General • debugprobe_on_pico (i.e. not the retail debug probe)

I've got a retail debug probe which works fine. Problem is I want to use the alternate probe you install on a pico (i.e. only one USB cable)

On page 18 of Getting Started With Pico - https://datasheets.raspberrypi.com/pico ... h-pico.pdf there's this image...
I've made this setup about half as dozen times so far. The left device MUST BE a plain pico (not a W or 2) while the right device can apparently be anything (only tried picos)

I've used the release version of debugprobe_on_pico.uf2 from https://github.com/raspberrypi/debugpro ... obe-v2.0.1 and also built many variants but there's a comment ...

src/probe_config.h:// TODO tie this up with PICO_BOARD defines in the main SDK

Hence the requirement that the probe itself be on a plain pico. So e.g. building for a pico_w appears to use the wrong LED pin for example (well, it didn't come on when I tried it)

I've got a collection of all picos so had no problem setting everything up but as soon as you start opencd (Windows) you get the following output...

Open On-Chip Debugger 0.12.0+dev-g75bc439-dirty (2024-08-08-15:04)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
CDLiveWatchSetup
Info : Hardware thread awareness created
Info : Hardware thread awareness created
adapter speed: 5000 kHz
Info : Listening on port 50001 for tcl connections
Info : Listening on port 50002 for telnet connections
Info : Using CMSIS-DAPv2 interface with VID:PID=0x2e8a:0x000c, serial=E66130100F373A28
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: Test domain timer supported
Info : CMSIS-DAP: FW Version = 2.0.0
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 0 SWDIO/TMS = 0 TDI = 0 TDO = 0 nTRST = 0 nRESET = 0
Info : CMSIS-DAP: Interface ready
Info : clock speed 5000 kHz
Warn : Too long SWD WAIT, issuing DAPABORT
Warn : Too long SWD WAIT, issuing DAPABORT
Warn : Too long SWD WAIT, issuing DAPABORT
Error: Failed to connect multidrop rp2040.dap0

Doing the same thing with the retail probe has correct responses - i.e. the Warn stuff etc is absent and it connects to the target

Statistics: Posted by Peardox — Thu Aug 22, 2024 5:48 pm

---