have you debugged a Pico2 RISC program with a PICOPROBE / DEBUGPROBE?

Exactly the same project, but I ask the extension to build it for ARM:. That works.

[2025-06-19T22:59:23.283Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session connected. You can switch to "DEBUG CONSOLE" to see GDB interactions.
"C:\\Users\\jancu/.pico-sdk/openocd/0.12.0+dev/openocd.exe" -c "gdb_port 50000" -c "tcl_port 50001" -c "telnet_port 50002" -s "C:\\Users\\jancu/.pico-sdk/openocd/0.12.0+dev/scripts" -f "c:/Users/jancu/.vscode/extensions/marus25.cortex-debug-1.12.1/support/openocd-helpers.tcl" -f interface/cmsis-dap.cfg -f target/rp2350.cfg -c "adapter speed 5000"
Open On-Chip Debugger 0.12.0+dev-g75bc439-dirty (2024-08-08-15:04)
Licensed under GNU GPL v2
For bug reports, read
openocd.org/.../bugs.html
CDLiveWatchSetup
Info : Hardware thread awareness created
Info : Hardware thread awareness created
Info : Hardware thread awareness created
Info : Hardware thread awareness created
cortex_m reset_config sysresetreq
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=4150323038323713
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
Info : SWD DPIDR 0x4c013477
Info : [rp2350.dap.core0] Cortex-M33 r1p0 processor detected
Info : [rp2350.dap.core0] target has 8 breakpoints, 4 watchpoints
Info : [rp2350.dap.core0] Examination succeed
Info : [rp2350.dap.core1] Cortex-M33 r1p0 processor detected
Info : [rp2350.dap.core1] target has 8 breakpoints, 4 watchpoints
Info : [rp2350.dap.core1] Examination succeed
Info : starting gdb server for rp2350.dap.core0 on 50000
Info : Listening on port 50000 for gdb connections
Info : accepting 'gdb' connection on tcp/50000
Info : RP2040 Flash Probe: 33554432 bytes @0x10000000, in 8192 sectors

Info : New GDB Connection: 1, Target rp2350.dap.core0, state: halted
undefined debug reason 8 (UNDEFINED) - target needs reset
Warn : [rp2350.dap.core1] VECTRESET is not supported on this Cortex-M core, using SYSRESETREQ instead.
Warn : [rp2350.dap.core1] Set 'cortex_m reset_config sysresetreq'.
[rp2350.dap.core0] halted due to breakpoint, current mode: Thread
xPSR: 0xf9000000 pc: 0x00000088 msp: 0xf0000000
[rp2350.dap.core1] halted due to debug-request, current mode: Thread
xPSR: 0xf9000000 pc: 0x00000088 msp: 0xf0000000
Warn : [rp2350.dap.core1] VECTRESET is not supported on this Cortex-M core, using SYSRESETREQ instead.
Warn : [rp2350.dap.core1] Set 'cortex_m reset_config sysresetreq'.
[rp2350.dap.core0] halted due to breakpoint, current mode: Thread
xPSR: 0xf9000000 pc: 0x00000088 msp: 0xf0000000
[rp2350.dap.core1] halted due to debug-request, current mode: Thread
xPSR: 0xf9000000 pc: 0x00000088 msp: 0xf0000000
Info : Padding image section 0 at 0x100017a4 with 92 bytes (bank write end alignment)
Warn : [rp2350.dap.core1] VECTRESET is not supported on this Cortex-M core, using SYSRESETREQ instead.
Warn : [rp2350.dap.core1] Set 'cortex_m reset_config sysresetreq'.
[rp2350.dap.core0] halted due to breakpoint, current mode: Thread
xPSR: 0xf9000000 pc: 0x00000088 msp: 0xf0000000
[rp2350.dap.core1] halted due to debug-request, current mode: Thread
xPSR: 0xf9000000 pc: 0x00000088 msp: 0xf0000000
[rp2350.dap.core1] halted due to debug-request, current mode: Thread
xPSR: 0x09000000 pc: 0x000000ec msp: 0xf0000000

Tried Claude 3.7 for insight:

https://claude.ai/share/5c40ee71-5752-451a-a4bd-4a0c04cd7ba1

This got me a step further!

It's not breaking or stopping yet, but finds the cores.

The part that got me to this:

Fixed!

I needed to adapt the launch.json, based on these instructions:

not 100% exact, but close enough to put me on track.

Here's the actual script I added:

        {
            "name": "Pico Debug RISC (Debug Probe)",
            "cwd": "${userHome}/.pico-sdk/openocd/0.12.0+dev/scripts",
            "type": "cortex-debug",
            "request": "launch",
            "executable": "${command:raspberry-pi-pico.launchTargetPath}",
            "servertype": "openocd",
            "serverpath": "${userHome}/.pico-sdk/openocd/0.12.0+dev/openocd.exe",
            "gdbPath": "${command:raspberry-pi-pico.getGDBPath}",
            "configFiles": [
                "interface/cmsis-dap.cfg",
                "target/rp2350-riscv.cfg"
            ],
            "openOCDPreConfigLaunchCommands": [
                "set ENABLE_RESCUE 0",
                "set PICO_CORE riscv"
            ],
            "serverArgs": [
                "-c", "adapter speed 1000"
            ],
            "runToEntryPoint": "main",
            "showDevDebugOutput": "raw"
        }

gdb server log:

strange thing: now that picotool has set it to riscv, it also works with the standard launch.json profile Pico Debug (Cortex-Debug)

I suppose like most things, these sort of niggles still have to worked out through future probe firmware mods. At least you have it working. That's so cool. Well done.

repeatable solution to get a new RP2350 debug-able in riscv mode:

1 time:

• build a program
• start pico2 up in BOOTSEL mode (push bootsel and connect to computer with USB)
• from project folder, execute (I use VSCode PowerShell terminal): picotool reboot -c riscv -u
• drop the riscv uf2 firmware on the disc (only needed 1 time)
• disconnect

from then on:

• connect a debugger, and now you can flash and debug with the default Pico Debug (Cortex-Debug) profile.