Hi all,
Here's my setup.
My development machine is an AMD Radeon based MiniPC running SuSE Tumbleweed Linux. I'm using vscode (well vscodium), as an IDE with the relevant pico sdk and arm compiler installed. This works fine and I can compile code and copy the .uf2 file to a pico and it works as expected.
Up until recently I was also able to program/debug my code via a picoprobe connected to another (Ubuntu linux) machine on my LAN using an appropriate launch.json. Though I have to manually ssh to the ubuntu machine and start openocd, so that it would listen for the incoming GDB connection.
This has recently stopped working, now when I start openocd it seems to lose sync with gdb :
I also don't seem to be able to terminate openocd using CTRL-C
The debugging control bar (the one with stop, go, step in, step out etc) never appears.
I have tried :
Updating OS on Suse and Ubuntu machines.
Grabbed the latest OpenOCD from the RaspberyPi github and re-build and installed it.
Grabbed the latest Picoprobe firmware from RaspberyPi github and re-build and installed it.
Updated vscodium.
Checked that the ports used by openocd can be opened remotely (they can).
The debug probe is a Pico2 on a carrier board that just breaks out the required lines to a header, I know the design is good as I have been using it for over a year now without problems. I followed the instructions to build the firmware for the pico2.
Does anyone have any clue as to what might be the problem here? Or how I might go about solving it.
Cheers.
Phill.
OpenOCD
Here's my setup.
My development machine is an AMD Radeon based MiniPC running SuSE Tumbleweed Linux. I'm using vscode (well vscodium), as an IDE with the relevant pico sdk and arm compiler installed. This works fine and I can compile code and copy the .uf2 file to a pico and it works as expected.
Up until recently I was also able to program/debug my code via a picoprobe connected to another (Ubuntu linux) machine on my LAN using an appropriate launch.json. Though I have to manually ssh to the ubuntu machine and start openocd, so that it would listen for the incoming GDB connection.
This has recently stopped working, now when I start openocd it seems to lose sync with gdb :
Code:
phill@trion:~$ ./db rp2350Open On-Chip Debugger 0.12.0+dev-00002-gcd4873400 (2026-01-15-18:06)Licensed under GNU GPL v2For bug reports, readhttp://openocd.org/doc/doxygen/bugs.htmlInfo : [rp2350.cm0] Hardware thread awareness createdInfo : [rp2350.cm1] Hardware thread awareness createdocd_process_reset_innerDEPRECATED! use 'adapter speed' not 'adapter_khz'adapter speed: 5000 kHzInfo : Listening on port 6666 for tcl connectionsInfo : Listening on port 4444 for telnet connectionsInfo : Using CMSIS-DAPv2 interface with VID:PID=0x2e8a:0x000c, serial=E9D12391744D8D7AInfo : CMSIS-DAP: SWD supportedInfo : CMSIS-DAP: Atomic commands supportedInfo : CMSIS-DAP: Test domain timer supportedInfo : CMSIS-DAP: FW Version = 2.0.0Info : CMSIS-DAP: Interface Initialised (SWD)Info : SWCLK/TCK = 0 SWDIO/TMS = 0 TDI = 0 TDO = 0 nTRST = 0 nRESET = 1Info : CMSIS-DAP: Interface readyInfo : clock speed 5000 kHzInfo : SWD DPIDR 0x4c013477 DPv3Info : [rp2350.cm0] Cortex-M33 r1p0 processor detectedInfo : [rp2350.cm0] target has 8 breakpoints, 4 watchpointsInfo : [rp2350.cm0] Examination succeedInfo : [rp2350.cm1] Cortex-M33 r1p0 processor detectedInfo : [rp2350.cm1] target has 8 breakpoints, 4 watchpointsInfo : [rp2350.cm1] Examination succeedInfo : [rp2350.cm0] starting gdb server on 3333Info : Listening on port 3333 for gdb connectionsInfo : accepting 'gdb' connection on tcp/3333Info : RP2350 rev 2, QSPI Flash win w25q32fv/jv id = 0x1640ef size = 4096 KiB in 1024 sectorsInfo : New GDB Connection: 1, Target rp2350.cm0, state: halted[rp2350.cm0] halted due to debug-request, current mode: Thread xPSR: 0xf9000000 pc: 0x00000088 msp: 0xf0000000[rp2350.cm1] halted due to debug-request, current mode: Thread xPSR: 0xf9000000 pc: 0x00000088 msp: 0xf0000000[rp2350.cm0] halted due to debug-request, current mode: Thread xPSR: 0xf9000000 pc: 0x00000088 msp: 0xf0000000[rp2350.cm1] halted due to debug-request, current mode: Thread xPSR: 0xf9000000 pc: 0x00000088 msp: 0xf0000000Info : RP2xxx ROM API function FC @ 3711Info : Padding image section 0 at 0x10014d98 with 104 bytes (bank write end alignment)Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (18237 ms). Workaround: increase "set remotetimeout" in GDBWarn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (18003 ms). Workaround: increase "set remotetimeout" in GDBWarn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (12002 ms). Workaround: increase "set remotetimeout" in GDB^CError: error handling USB events: System call interrupted (perhaps due to signal)^CError: error handling USB events: System call interrupted (perhaps due to signal)Warn : keep_alive() was not invoked in the 1000 ms timelimit. GDB alive packet not sent! (8906 ms). Workaround: increase "set remotetimeout" in GDB^CError: error handling USB events: System call interrupted (perhaps due to signal)^CError: error handling USB events: System call interrupted (perhaps due to signal)^CError: error handling USB events: System call interrupted (perhaps due to signal)^CError: error handling USB events: System call interrupted (perhaps due to signal)^CError: error handling USB events: System call interrupted (perhaps due to signal)The debugging control bar (the one with stop, go, step in, step out etc) never appears.
I have tried :
Updating OS on Suse and Ubuntu machines.
Grabbed the latest OpenOCD from the RaspberyPi github and re-build and installed it.
Grabbed the latest Picoprobe firmware from RaspberyPi github and re-build and installed it.
Updated vscodium.
Checked that the ports used by openocd can be opened remotely (they can).
The debug probe is a Pico2 on a carrier board that just breaks out the required lines to a header, I know the design is good as I have been using it for over a year now without problems. I followed the instructions to build the firmware for the pico2.
Does anyone have any clue as to what might be the problem here? Or how I might go about solving it.
Cheers.
Phill.
OpenOCD
Statistics: Posted by PhillHS — Thu Jan 15, 2026 6:31 pm