Re: how to attach umodem0 to something cu can use

Mark Millard <[email protected]> Wed, 22 Apr 2026 23:04:32 -0700
Newsgroups gmane.os.freebsd.stable
Message-ID <[email protected]>
On 4/22/26 18:47, void wrote:
> On Wed, Apr 22, 2026 at 04:22:49PM -0700, Mark Millard wrote:
> 
>> Is this the standard Raspberry Pi Debug Probe?
> 
> yes
> 
>>
>> # dmesg -a | grep -i uart
>> uart0: <PrimeCell UART (PL011)> iomem 0x107d001000-0x107d0011ff irq 0 on
>> acpi0
>> uart0: console (115200,n,8,1)
>>
>> The Probe has 2 non-USB ports (and a USB port, not listed below):
>>
>> D (SWD)  for CMSIS-DAP
>> U (UART) for UART serial
>>
>> Both apparently can be in use but I only connect and use the U port (as
>> the serial console).
> 
> I'll need to look at it again wrt freebsd. I think
> the D port was being used on the probe. I couldnt see for sure which was
> which.
> 
> In mitigation, the cu command did respond with 'connected'
> 
>> In my context, the USB connection is to a old macOS laptop running a
>> Serial console (terminal) application.
> 
> 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

RPi5 (only logged in on the serial console):
login[1599]: ROOT LOGIN (root) ON ttyu0
# echo test > /dev/ttyu0
test
# echo test > /dev/console
test

> 
> 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.


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