How do you like the debug probe? I got one, but haven’t figured out an adapter for the pins yet to fit my BP5. I have 3P milled pins that I solder to a little PCB breakout I use for debugging with a PICO.
The DuPont crimps on their cable are probably the cheapest stuff I’ve ever seen. My jaw dropped a little.
The first time I run this, setting breakpoints in VSCode does not appear to do anything. I can break in after the fact, but … that’s not much use when I want to trace what’s happening within a function.
Except for the first time (even after restarting openOCD), attempts to debug just complains with:
ERROR: Unable to start debugging. Unexpected GDB output from command "-exec-run". During startup program exited with code 126.
The program './bp5/build/bus_pirate5_rev10.elf' has exited with code 0 (0x00000000).
Anyone else using this type of setup? If so, any ideas why the breakpoints are not being set?
Just a guess, is the PICO probe firmware up to date? They made some changes at one point and when I upgraded the VSCODE side I had to update the probe firmware too.
At the moment I have a zombie setup where I have to manually change stuff in the config because the vscode pico extension kind of messed up my whole toolchain.
I’ve also been using the wrong term… I’m using the official debugprobe hardware (not a pico setup as a debug probe), because the debugprobe kit was the cheapest way (at the time) to get the RP2040 debug cables.
Bummer. Still going to try to find a way to get this working.
OpenOCD server is working, and cmd-line I can break in, but doesn’t seem to have initial breakpoints working.
If I can’t figure this out, my ability to put together the more complex improvements will be severely impaired.