Debugging against the Pico Board
Using the second core of the same Pico
Since the RP2040 features two cores, why not using one core to debug the other? This is the interesting approach to get a first look at debugging.
Alas, I couldn't manage to run the debugger and debug the application at the same time. I may have missed one step in the procedure. |
Using a second Pico board
As the Pico goes for USD4, why not using a second Pico as a programmer-debugger?
Called PicoProbe, this solution works very well. The first Pico is turned into a programmer-debugger after flashing an executable available as a UF2 file. Then it is connected to the second Pico, the target. The programmer-debugger also reroutes the serial port from pin 0 and 1 of the target. The Serial port of the target is no longer Serial on the USB port, by Serial1 on pins 0 and 1. |
Using a Raspberry Pi 4B
I haven't tested this solution.
|
Using a standard programmer-debugger
The standard tools include the openOCD server, the GDB client and a Segger J-Link programmer-debugger.
I faced various issues, but found fixes for all of them:
|
Links
|
Posted: 21 Apr 2022 Updated: |