From Newsgroup: muc.lists.freebsd.stable

Hi,

I'm trying to use the raspberry pi probe to access
(from desktop amd64 15-stable) a rpi5.

The device is recognised on the desktop:

Apr 22 18:11:54 [7254924] ugen0.11: <Raspberry Pi Debug Probe (CMSIS-DAP)> at usbus0
Apr 22 18:11:54 [7254924] umodem0 on uhub6
Apr 22 18:11:54 [7254924] umodem0: <Raspberry Pi Debug Probe (CMSIS-DAP), class 0/0, rev 2.10/1.01, addr 27> on usbus0
Apr 22 18:11:54 [7254924] umodem0: data interface 2, has no CM over data, has no break

How can I tell cu to use it?

A usb<>ttl cable is seen like this:

Apr 22 19:32:38 [7259768] ugen0.11: <Prolific Technology Inc. USB-Serial Controller D> at usbus0
Apr 22 19:32:38 [7259768] uplcom0 on uhub6
Apr 22 19:32:38 [7259768] uplcom0: <Prolific Technology Inc. USB-Serial Controller D, class 0/0, rev 1.10/4.00, addr 28> on usbus0

I can access it via cu like this:

% cu -l cuaU0 -s 115200
Connected

How to do the same with the probe? Is it seen on cuaU0? I'm not seeing any output.
--


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

On 4/22/26 11:46, void wrote:

Hi,

I'm trying to use the raspberry pi probe to access (from desktop amd64 15-stable) a rpi5.

The device is recognised on the desktop:

Apr 22 18:11:54 [7254924] ugen0.11: <Raspberry Pi Debug Probe (CMSIS-
DAP)> at usbus0
Apr 22 18:11:54 [7254924] umodem0 on uhub6
Apr 22 18:11:54 [7254924] umodem0: <Raspberry Pi Debug Probe (CMSIS-
DAP), class 0/0, rev 2.10/1.01, addr 27> on usbus0
Apr 22 18:11:54 [7254924] umodem0: data interface 2, has no CM over
data, has no break

I'm taking some guesses about context, so the below might well be off point.

Is this the standard Raspberry Pi Debug Probe? I use one on each RPi5 in
order to have a serial console for each. On the RPi5 I get just:

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

To see which of the 2 non-USB ports is which on the probe, view:

<https://www.raspberrypi.com/documentation/microcontrollers/images/labelled-wiring.jpg>

In my context, the USB connection is to a old macOS laptop running a
Serial console (terminal) application.


Notes:

The FreeBSD running on the RPi5 is via a partial/draft EDK2 and its ACPI selection. (There are more specifics involved.)

If I understand right, there is a devel/openocd FreeBSD port for use of CMSIS-DAP, not that I've ever done so.

How can I tell cu to use it?

A usb<>ttl cable is seen like this:

Apr 22 19:32:38 [7259768] ugen0.11: <Prolific Technology Inc. USB-Serial Controller D> at usbus0
Apr 22 19:32:38 [7259768] uplcom0 on uhub6
Apr 22 19:32:38 [7259768] uplcom0: <Prolific Technology Inc. USB-Serial Controller D, class 0/0, rev 1.10/4.00, addr 28> on usbus0

I can access it via cu like this:

% cu -l cuaU0 -s 115200
Connected

How to do the same with the probe? Is it seen on cuaU0? I'm not seeing any output.

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


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

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?

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


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

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 ?
Was that in dmesg on the mac?

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


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21f-Linux NewsLink 1.2

From Newsgroup: muc.lists.freebsd.stable

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


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-admin@muc.de
--- Synchronet 3.21f-Linux NewsLink 1.2