cmsis-dap.cfg and rp2040.cfg

[approxdec]

g'day.

on windows 11 i am using

xpack-openocd-0.12.0-1-win32-x64.zip

for STM32 and there has never been a problem.

for the raspberry pi pico with cmsis-dap.cfg and rp2040.cfg
.\bin\openocd -f interface\cmsis-dap.cfg -f target\rp2040.cfg -s share

F:\openocd-v0.12.0-i686-w64-mingw32>.\bin\openocd -f interface\cmsis-dap.cfg -f target\rp2040.cfg -s share
Open On-Chip Debugger 0.12.0 (2023-01-14-23:37)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Warn : An adapter speed is not selected in the init scripts. OpenOCD will try to run the adapter at the low speed (100 kHz)
Warn : To remove this warnings and achieve reasonable communication speed with the target, set "adapter speed" or "jtag_rclk" in the init scripts.
Info : Using CMSIS-DAPv2 interface with VID:PID=0x2e8a:0x000c, serial=E6614103E76B342F
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 100 kHz
Info : SWD DPIDR 0x0bc12477, DLPIDR 0x00000001
Info : SWD DPIDR 0x0bc12477, DLPIDR 0x10000001
Info : [rp2040.core0] Cortex-M0+ r0p1 processor detected
Info : [rp2040.core0] target has 4 breakpoints, 2 watchpoints
Info : [rp2040.core1] Cortex-M0+ r0p1 processor detected
Info : [rp2040.core1] target has 4 breakpoints, 2 watchpoints
Info : starting gdb server for rp2040.core0 on 3333
Info : Listening on port 3333 for gdb connections
Info : starting gdb server for rp2040.core1 on 3334
Info : Listening on port 3334 for gdb connections
Error: error reading data: Pipe error
Polling target rp2040.core1 failed, trying to reexamine
Error: CMSIS-DAP command CMD_DISCONNECT failed.
Error: CMSIS-DAP command CMD_CONNECT failed.
Error: CMSIS-DAP command CMD_DISCONNECT failed.
Error: CMSIS-DAP command CMD_CONNECT failed.

which is not very helpful. well - it is helpful but not in a way one would like.

Raspberry Pi Debug Probe at https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html
about 3/8 down the page at 'MS Windows'
points to a particular build of openocd at https://github.com/raspberrypi/pico-setup-windows/releases/latest/download/openocd-x64-standalone.zip
and this works fine with the Debug Probe.

well, you likely know all this.
but why? why will the call to cmsis-dap.cfg and rp2040.cfg in
xpack-openocd-0.12.0-1-win32-x64.zip
not work?

[ilg-ul]

Unfortunately I do not have a Raspberry Debug Probe to test.

This project distributes the official OpenOCD, built from the upstream repository.

If Raspberry has a custom version of OpenOCD, with functionality not contributed back to the official project, the official OpenOCD cannot work with such custom devices. You should probably use the custom OpenOCD, as suggested by the Raspberry documentation.

BTW, the links in your message are broken.

[ilg-ul]

I got a Raspberry Debug Probe and did a first test on my mac, with the xPack OpenOCD, and it seems ok:

% /Users/ilg/Library/xPacks/@xpack-dev-tools/openocd/0.12.0-1.1/.content/bin/openocd  -f interface/cmsis-dap.cfg -f target/rp2040.cfg
xPack Open On-Chip Debugger 0.12.0-01004-g9ea7f3d64-dirty (2023-01-30-17:05)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Warn : An adapter speed is not selected in the init scripts. OpenOCD will try to run the adapter at the low speed (100 kHz)
Warn : To remove this warnings and achieve reasonable communication speed with the target, set "adapter speed" or "jtag_rclk" in the init scripts.
Info : Using CMSIS-DAPv2 interface with VID:PID=0x2e8a:0x000c, serial=E6616407E339502C
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 100 kHz
Info : SWD DPIDR 0x0bc12477, DLPIDR 0x00000001
Info : SWD DPIDR 0x0bc12477, DLPIDR 0x10000001
Info : [rp2040.core0] Cortex-M0+ r0p1 processor detected
Info : [rp2040.core0] target has 4 breakpoints, 2 watchpoints
Info : [rp2040.core1] Cortex-M0+ r0p1 processor detected
Info : [rp2040.core1] target has 4 breakpoints, 2 watchpoints
Info : starting gdb server for rp2040.core0 on 3333
Info : Listening on port 3333 for gdb connections
Info : starting gdb server for rp2040.core1 on 3334
Info : Listening on port 3334 for gdb connections
^Cshutdown command invoked

[ilg-ul]

Same result on Windows:

>C:\Users\ilg\AppData\Roaming\xPacks\@xpack-dev-tools\openocd\0.12.0-1.1\.content\bin\openocd -f interface\cmsis-dap.cfg -f target\rp2040.cfg
xPack Open On-Chip Debugger 0.12.0-01004-g9ea7f3d64-dirty (2023-01-30-15:04)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Warn : An adapter speed is not selected in the init scripts. OpenOCD will try to run the adapter at the low speed (100 kHz)
Warn : To remove this warnings and achieve reasonable communication speed with the target, set "adapter speed" or "jtag_rclk" in the init scripts.
Info : Using CMSIS-DAPv2 interface with VID:PID=0x2e8a:0x000c, serial=E6616407E339502C
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 100 kHz
Info : SWD DPIDR 0x0bc12477, DLPIDR 0x00000001
Info : SWD DPIDR 0x0bc12477, DLPIDR 0x10000001
Info : [rp2040.core0] Cortex-M0+ r0p1 processor detected
Info : [rp2040.core0] target has 4 breakpoints, 2 watchpoints
Info : [rp2040.core1] Cortex-M0+ r0p1 processor detected
Info : [rp2040.core1] target has 4 breakpoints, 2 watchpoints
Info : starting gdb server for rp2040.core0 on 3333
Info : Listening on port 3333 for gdb connections
Info : starting gdb server for rp2040.core1 on 3334
Info : Listening on port 3334 for gdb connections
...

It looks like the problem you have happens after the GDB client connects to OpenOCD.

Could you share more details in order to reproduce the issue? What GDB client are you using, which version, and what is the exact command?

[approxdec]

g'day.
I am sorry but I have been called away 200 km on family things.
so this is written from memory but I am fairly certain this would have been my sequence.

https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads

arm-gnu-toolchain-12.2.rel1-mingw-w64-i686-arm-none-eabi.zip
at the top of the list

From there I used the gdb file [ file name ending in gdb]
calling from a project folder so it would have the path name before it.

in gdb I would have started with
target remote localhost:3333
but I don't think I could get to there.

I am sorry I can't do this on my windows 11 laptop at home and repeat the sequence there.
I hope this is useful. I will not be home until Saturday morning UTC + 11

[ilg-ul]

As a reference, on macOS:

% /Users/ilg/Library/xPacks/@xpack-dev-tools/openocd/0.12.0-1.1/.content/bin/openocd  -f interface/cmsis-dap.cfg -f target/rp2040.cfg
xPack Open On-Chip Debugger 0.12.0-01004-g9ea7f3d64-dirty (2023-01-30-17:05)
...
Info : starting gdb server for rp2040.core0 on 3333
Info : Listening on port 3333 for gdb connections
Info : starting gdb server for rp2040.core1 on 3334
Info : Listening on port 3334 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
[rp2040.core0] halted due to debug-request, current mode: Thread 
xPSR: 0x01000000 pc: 0x100001f0 msp: 0x2003ffe8
Info : Found flash device 'win w25q16jv' (ID 0x001540ef)
Info : RP2040 B0 Flash Probe: 2097152 bytes @0x10000000, in 32 sectors

Info : New GDB Connection: 1, Target rp2040.core0, state: halted
Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (1122 ms). Workaround: increase "set remotetimeout" in GDB
Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
Info : dropped 'gdb' connection

and the client was:

% /Users/ilg/Library/xPacks/@xpack-dev-tools/arm-none-eabi-gcc/12.2.1-1.2.1/.content/bin/arm-none-eabi-gdb
GNU gdb (xPack GNU Arm Embedded GCC x86_64) 12.1.90.20221210-git
...
(gdb) target remote localhost:3333
Remote debugging using localhost:3333
warning: No executable has been specified and target does not support
determining executable automatically.  Try using the "file" command.
0x100001f0 in ?? ()
(gdb) exit
A debugging session is active.

	Inferior 1 [Remote target] will be detached.

Quit anyway? (y or n) y
Detaching from pid Remote target
Ending remote debugging.
[Inferior 1 (Remote target) detached]
%

[ilg-ul]

Same on Windows 11:

>C:\Users\ilg\AppData\Roaming\xPacks\@xpack-dev-tools\openocd\0.12.0-1.1\.content\bin\openocd -f interface\cmsis-dap.cfg -f target\rp2040.cfg
xPack Open On-Chip Debugger 0.12.0-01004-g9ea7f3d64-dirty (2023-01-30-15:04)
...
Info : starting gdb server for rp2040.core0 on 3333
Info : Listening on port 3333 for gdb connections
Info : starting gdb server for rp2040.core1 on 3334
Info : Listening on port 3334 for gdb connections
Info : accepting 'gdb' connection on tcp/3333
Info : Found flash device 'win w25q16jv' (ID 0x001540ef)
Info : RP2040 B0 Flash Probe: 2097152 bytes @0x10000000, in 32 sectors

Info : New GDB Connection: 1, Target rp2040.core0, state: halted
Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (2036 ms). Workaround: increase "set remotetimeout" in GDB
Warn : Prefer GDB command "target extended-remote :3333" instead of "target remote :3333"
Info : dropped 'gdb' connection
...

With the client session:

>C:\Users\ilg\AppData\Roaming\xPacks\@xpack-dev-tools\arm-none-eabi-gcc\12.2.1-1.2.1\.content\bin\arm-none-eabi-gdb.exe
GNU gdb (xPack GNU Arm Embedded GCC x86_64) 12.1.90.20221210-git
...
(gdb) target remote localhost:3333
Remote debugging using localhost:3333
warning: No executable has been specified and target does not support
determining executable automatically.  Try using the "file" command.
0x0000018a in ?? ()
(gdb) exit
A debugging session is active.

        Inferior 1 [Remote target] will be detached.

Quit anyway? (y or n) y
Detaching from pid Remote target
Ending remote debugging.
[Inferior 1 (Remote target) detached]
>

[ilg-ul]

We'll probably wait for you to return to your computer for more details.

[approxdec]

hello again.

dodgy USB ports - that is the main problem.

your proof that the standard openocd and gdb work for raspberry pi pico
assured me that the command line was not a problem.

my original question as to why the standard openocd would not work
was confounded by dodgy usb ports.

i have spent some hours last night with standard openocd + gdb and
have had the commands work and then fail. usb ports are the problem
for me. since i was assured by your testing that both openocd and gdb
worked as expected i had eliminated the command line as a problem.

changing/removing usb connections mainly solved the issue. i can be
wary of the usb issue in future.

thanks for you help and apologies for the time gap in our interaction.

regards
joe

[ilg-ul]

Thank you for confirming that xPack OpenOCD behaves as expected.

Good luck with your projects!