Re: how to attach umodem0 to something cu can use

On 4/24/26 04:14, void wrote:
> On Wed, Apr 22, 2026 at 11:04:32PM -0700, Mark Millard wrote:
>> On 4/22/26 18:47, void wrote:
>>>
>>> what device name does it use?
>>
>> macOS:
>> Path: /dev/cu.usbmodemFD132
>> It identifies it with the text: Debug Probe (CMSIS-DAP) #2
>> Driver ID: com.apple.driver.usb.cdc.acm
> 
> How were you able to tell it was associated with /dev/cu.usbmodemFD132 ?

The Serial program shows information under the Terminal  > Settings >
Device Info tab (where one can give a personally assigned to identify
the usage context).

> Was that in dmesg on the mac?

no.

> 
> On my (stable/15) desktop it was associated with umodem0 in dmesg.
> But I could not find a way to tell 'cu' about it. At the time,
> I looked for /dev/umodem0 in /dev and couldn't find it. So
> cu -l umodem0 -s 115200 errored.
> 
> I also don't know if it gets automatically linked with /dev/cuaU0
> 
>>> Eventually I tried from a debian laptop and changed port on the probe,
>>> then used
>>> i think it was procomm with the device name that was emitted when the
>>> probe
>>> was plugged in, booted the pi5 and output was produced.
> 
> I've worked around the issue for the time being by using Debian, but i'd
> really like this to work on FreeBSD as that is my main desktop.


-- 
===
Mark Millard
marklmi at yahoo.com