Hello,
I have bought two units of the new Raspberri Pi debug probes. The documentation is not great. What the specs says is:
While designed for use with Raspberry Pi products, the Debug Probe provides standard UART and CMSIS-DAP interfaces over USB, so it can also be used with other processors, or even just as a USB-to-UART cable. It works with OpenOCD and other tools that support CMSIS-DAP.
The docs on Github are not for the newcomer.
https://www.raspberrypi.com/documentati ... probe.html
The fact it shows the debug probe as part of the Microcontroller, rather than as used as part of ran RPI5 adds a lot of noise to the pedagogical process of learning how the probe works.
So when I go about plugging the USB port in Linux, it shows up as a TTY port, named /dev/TTYACM0, and it binds to the U port on the port. It would actually be great for the documentation to stipulate U is for UART and D is for DEBUG (it's in the video, but not in the written text).
I expect that /dev/TTYACM0 is bound to the U port without any other drivers.
Then I expect the CMSIS-DAP interface to be a logical device other than /dev/TTYACM0 which can work with OpenOCD
I further purport the documentation at https://www.raspberrypi.com/documentati ... probe.html to be erroneous for swapping the debug leds for U and D... it does not make sense that the GPIO 15 & 16 leds which are attached to the U port to be on the D side if the leds on the right side are meant to depict serial activity on the Debug port... Finally it isn' clear what are the references to GPIO 7&8 for.
Do I understand that there is no way to configure the port as two separate UARTS over the same USB interface ?
In my illustrious discovery process, I ended up wiring two probes ... good thing I bought two, one on the U interface for the RPI debug header to use it as a serial port for console and another debug probe to have the U interface interface with the GPIO 15 & 16... and it was working nicely. See my other post to this effect.
Francois
I have bought two units of the new Raspberri Pi debug probes. The documentation is not great. What the specs says is:
While designed for use with Raspberry Pi products, the Debug Probe provides standard UART and CMSIS-DAP interfaces over USB, so it can also be used with other processors, or even just as a USB-to-UART cable. It works with OpenOCD and other tools that support CMSIS-DAP.
The docs on Github are not for the newcomer.
https://www.raspberrypi.com/documentati ... probe.html
The fact it shows the debug probe as part of the Microcontroller, rather than as used as part of ran RPI5 adds a lot of noise to the pedagogical process of learning how the probe works.
So when I go about plugging the USB port in Linux, it shows up as a TTY port, named /dev/TTYACM0, and it binds to the U port on the port. It would actually be great for the documentation to stipulate U is for UART and D is for DEBUG (it's in the video, but not in the written text).
I expect that /dev/TTYACM0 is bound to the U port without any other drivers.
Then I expect the CMSIS-DAP interface to be a logical device other than /dev/TTYACM0 which can work with OpenOCD
I further purport the documentation at https://www.raspberrypi.com/documentati ... probe.html to be erroneous for swapping the debug leds for U and D... it does not make sense that the GPIO 15 & 16 leds which are attached to the U port to be on the D side if the leds on the right side are meant to depict serial activity on the Debug port... Finally it isn' clear what are the references to GPIO 7&8 for.
In my illustrious discovery process, I ended up wiring two probes ... good thing I bought two, one on the U interface for the RPI debug header to use it as a serial port for console and another debug probe to have the U interface interface with the GPIO 15 & 16... and it was working nicely. See my other post to this effect.
Francois
Statistics: Posted by fmenard1234 — Sun Jan 12, 2025 10:16 pm