I purchased Visual Micro on 8/3/2024 and running it on VS2022.  I was able to get it to work properly with an Arduino board but get an error when uploading to a Pico W board and Pico Probe Debugger.  The error is “No drive to deploy. The uploader returned an error.”  I am unable to resolve this issue and need assistance.   

VM Configuration:
•      Attached is my output with verbose logging and Show Build Properties enabled. 
•      The setup was performed according to instructions from your website, How to debug a Raspberry Pi Pico with an Arduino project and GDB? (visualmicro.com).  The only differences between the instructions and my installation is that my PicoProbe is a smaller square board than the one shown in the VM instructions, and also Zadig V2.9 does not display an option Picoprobe (Interface 2). The driver that becomes available to me when I plug in the Pico Probe USB is CMSIS-DAP v2 Interface (Interface 0). WINUSB v10.0.
•      I have included C:\Program Files\Git\mingw64\bin as a path in my environment variables.

IDE: Arduino 2
Installed Platform: Raspberry Pi Pico/rp2040 v3.9.4

How can I isolate the cause for the error and resolve it?

The build has been updated. Please redownload it from here

Add the properties shown in bold to the command line and then email the log out of the  "[vmbuild.exe path]\logs" folder.

-builder.project_path="[project path and name].vcxproj" -builder.build=true -builder.verbose=true -builder.log=true -builder.dump_props=true

Thanks

I apologize Tim, I used VMBuilder on the larger project file I had developed and tested on the Arduino. When I ran it on the simple Pico test program, VM Builder threw an exception message saying libdep.a is either not designed to run on Windows or contains an error. I had to hit OK multiple times with a reoccuring exception until the compilation completed. Attached is the log file. I can send a screen shot of the exception message if that would help you.

You are correct, I am using the Raspberry Pi Debug Probe hardware.  I thought they were functionally the same! 

Placing the board in boot select mode allowed the download to complete.  However, a second exception occurs when it attempts to start debugging.  Attached is a screenshot with two exceptions. I first is my original exception associated with the rp2040 library when I ran VMBuilder this morning.  The second is the most recent exception associated with the debugger.

UPDATE: I made some progress over the weekend and resolved the second error message.  The Hello World example code now flashes and the Debug Probe yellow and green UART LEDs are on. However, the serial monitor opens and then immediately closes when I start the program, and the break point I set on the printf statement has an exclamation warning. It says, "The breakpoint will not currently be hit. Module containing this breakpoint has not yet loaded or the breakpoint address could not be obtained." I tried reopening the monitor and it remains open but there is no activity.  I also tried manually attaching the debug to the OpenOCD process. No Luck.

I don't know if it's relevant, but I read a post that OpenOCD v 0.11 or 0.12 is required for the RPi Debug Probe to work properly. I notice that the Visual Mirco OpenOCD installed at C:\ProgramData\VMicro\tools\openocd-rpi-0.10.0.20210623\bin  is v0.10.   

What might be causing the breakpoint not to function? I've attached a VMBuilder log to this message in case that might be helpful in isolating the cause. Thank you!

It could be that we need to update our internal OpenOCD version which we will look at in the coming days.

Can you try selecting the "Debug: Arduino" option instead of "Debug: Hardware", and then try attaching the debugger again?

(This will use the same configuration as the Arduino2 IDE for debugging and will run the OpenOCD version packaged with the boards' tools)

Thanks for the update.

Are you running the Serial via the PicoProbe, or directly from the USB lead between the target RP2040 and the PC?

Are you calling the main() in your hello_serial.c from the INO or is it possible to share the code for your project (either here or via email)?

Simon,

Attached is the Test project as a Zip file.  Your reply asking about the ino file may be the problem. 

I am not well versed on the interactions between VM, VS and Arduino IDE; nor how the debug, UART and USB channels are applied for hardware debugging.  Therefore, I have not applied an INO file to my test. The C programming information I’ve read (Programming the Raspberry Pi Pico/W in C, second edition) all is pure C with a main(), no ino file.  So are you suggesting that I need to create a INO file, establish the Serial port in setup() and then call main in loop()?  If so, does it get deployed that way to the release version? If so, it would be helpful if you could point me to some educational resources that would help me come up to speed to fill in my blind spots. 

Thank you.

John