Hello,

I am attempting to debug an Arduino Nano RP2040 Connect with the PicoProbe. I've never done any hardware debugging like this, so bear with me.

I've followed the instructions in the following post to configure my Raspberry Pi Pico as a PicoProbe.

Creating a PicoProbe Debug Probe
https://www.visualmicro.com/page/Creating-a-PicoProbe-Debug-Probe.aspx

I then followed the directions in the following page

How to debug a Raspberry Pi Pico with an Arduino project and GDB?
https://www.visualmicro.com/page/RasPiPico-Debugging.aspx

I am currently stuck at the "Software Setup" section.

I've installed Visual Studio 2022 (free version), and added the Visual Micro extension. I've pointed the IDE to my installation of Arduino 2.0. vMicro seems to detect everything appropriately.

I have "Arduino IDE for Visual Studio 2022" version 2022.905.2201 installed (using the trial version at the moment). I also have the latest boards installed for the Mbed OS Nano boards (both the Nano RP2040 Connect and the Raspberry Pi Pico).

The problem I'm having is that the PicoProbe option is not showing up in the list of Hardware Debuggers with selecting the "Debug: Hardware" option. (See image attached)

Any help would be appreciated.

Sincerely,
Marcus G

Simon,

Thank you for the clarification! When I originally choose that package, I was thrown off by the Option 1...Option 10 selections, and totally missed the Debugger menu option below that, which does indeed have the Hardware Debugger selection and PicoProbe choices. Thanks!

Now on to the next step where I am stuck...

So far I am successfully able to upload the code, and the serial debugging seems to be working...through the PicoProbe.

I'm stuck at the actually debugging part. I've set a breakpoint, but it doesn't look like we are ever getting to the actual debug mode. After the program is uploaded, Visual Studio just returns to the "Ready" state. See the Micro Build log below.

Program BlinkWithoutDelay size: 55,476 bytes (used 0% of a 16,773,120 byte maximum) (3.29 secs)
Minimum Memory Usage: 7624 bytes (3% of a 262144 byte maximum)


TRIAL Version of Visual Micro (Expires On 25 October 2022)
(Existing customer? CTRL+click Or go to this link (https://visualmicro.com/page/Trial-Mode-VS2022.aspx)
Uploading 'BlinkWithoutDelay' to 'Arduino Nano RP2040 Connect (Picoprobe)                                                                      (rp2040_arduino_nano_connectpicoprobe)' using 'COM6'
Uploader started for board Arduino Nano RP2040 Connect (Picoprobe)                                                                      (rp2040_arduino_nano_connectpicoprobe)
Upload method will be: bootloader
Uploading via Bootloader
C:\Users\Marcus c06\bin\openocd -f "interface/picoprobe.cfg" -f "target/rp2040.cfg" -s .0-C/share/openocd/scripts -c "program outDelay.ino.elf} verify reset exit"
Open On-Chip Debugger 0.11.0-g610f137 (2022-02-11-13:57)
Licensed under GNU GPL v2
For bug reports, read
	http://openocd.org/doc/doxygen/bugs.html
Info : only one transport option; autoselect 'swd'
adapter speed: 5000 kHz
Info : Hardware thread awareness created
Info : Hardware thread awareness created
Info : RP2040 Flash Bank Command
Info : clock speed 5000 kHz
Info : SWD DPIDR 0x0bc12477
Info : SWD DLPIDR 0x00000001
Info : SWD DPIDR 0x0bc12477
Info : SWD DLPIDR 0x10000001
Info : rp2040.core0: hardware has 4 breakpoints, 2 watchpoints
Info : rp2040.core1: hardware has 4 breakpoints, 2 watchpoints
Info : starting gdb server for rp2040.core0 on 3333
Info : Listening on port 3333 for gdb connections
target halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x000000ee msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0xf1000000 pc: 0x000000ee msp: 0x20041f00
** Programming Started **
Info : RP2040 B0 Flash Probe: 2097152 bytes @10000000, in 512 sectors
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
Info : Writing 73728 bytes starting at 0x0
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
** Programming Finished **
** Verify Started **
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x00000178 msp: 0x20041f00
** Verified OK **
** Resetting Target **
shutdown command invoked
	The upload process has finished.
 

When I choose the "Attach to Process" option, I receive an error (see attached). That error suggests looking at the Project Configuration -> Debugging options, which don't look very promising. 

Any suggestions?

Sincerely,
Marcus G