Hi.

I see that there is support for making a pico-probe from an additional RPi Pico, but is there a way to debug using the new Raspberry Pi Debug Probe?

https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html



Cheers

Nigel

Thanks for the information but I am unable to get this working with the probe that I linked you to earlier. Can you describe how to get this working with this specific probe please?

This is the issue that I'm getting when attempting to use the Raspberry Pi Debug Probe as suggested in the documentation/videos.

Compiling 'ScanNetworks' for 'Raspberry Pi Pico W (Picoprobe)                                                                                        (rp2040_rpipicowpicoprobe)'
Program size: 320052 bytes (used 15% of a 2093056 byte maximum) (3.40 secs)
Minimum Memory Usage: 59560 bytes (23% of a 262144 byte maximum)
 
Uploading 'ScanNetworks' to 'Raspberry Pi Pico W (Picoprobe)(rp2040_rpipicowpicoprobe)' using 'COM8'
Open On-Chip Debugger 0.11.0-g610f137 (2022-02-11-13:57)
The uploader process failed
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
Error: Failed to open or find the device
Error: Can't find a picoprobe device! Please check device connections and permissions.
Error: No Valid JTAG Interface Configured.

Here is a link to the build log
https://drive.google.com/file/d/1FPi4Yx-RcZn4jqo56fv-IgedgyyxRaFc/view?usp=share...

I am using the official board with the debug and uart connections attached. This is working and debugging/logging okay through a test project in Visual Studio Code - but I'd really like to get this working through Visual Micro on VS2022

So I renamed the file to "RASPBERRY_PI_PICO_W.Debug.debugger_launch.json"
Set Debug to Hardware with Manual/Custom set and with the Pico W selected as the correct COM port attempted to debug the app.

It uploaded the app to the device and it reset and started to run, but VisualStudio showed an error saying that it could not find the MatrixOrnamentV3.ino.bin file referenced from the JSON file on line 25. I edited the json file and specified the .elf file and after trying again, and waiting for the debugger to kick in, I could eventually start to debug the running program by adding a breakpoint.

Is the .bin generation missing? Was I correct changing this to the .elf file instead?

I am unable to put a breakpoint within the setup() function as the program seems to run on the Pico before the initial breakpoint is hit. I attempted to change the "stopAtEntry" value in the json to true, but this made no difference. Is there some other way to get the debugger to hold off from starting the program until everything is ready?

I also had trouble stopping the debugger and restarting it. The program would not upload again to the Pico. I had to manually reset the Pico and try again for it to work. Shouldn't the program be uploaded via the Debug Probe?

Sorry to be a pain, but I hope this is some useful info for you.

Thanks. I've updated to v3.0.0 and this is also working okay - although still with the ELF file. The BIN file is being generated, but setting that instead of the ELF give a missing or corrupt file warning when the debugger is attempting to start. Maybe this only works with v.3.1.0

The upload through the debug probe is also working - although it's fairly slow compared to the uf2 file method, but I think that is just the speed that the debug port runs at.

Thanks for all your help with this. How soon do you expect to have a working solution without the need for a custom json file? weeks? months?

I added the delay and this is working fine

Apologies for the delay on releasing this, please download the latest version (23.0424.0) from the board below to use the integrated menu option for this debugger;
https://www.visualmicro.com/forums/YaBB.pl?board=VS_ARDUINO_EXT_RELEASES