hello.

with rpi pico debugging using hardware/picoprobe
i get 'unable to start debugging' after build and load

Thanks for the report.

Can you enable the vMicro > Uploader > Verbose, and try attaching the debugger again from Debug > Attach to Process, and attach the additional output shown in the Output > Micro Build Window, and anything shown in the Output > Debug window.

Please also attach the below log file from the build folder:
Blink_DebugOpenOCD.log

Thanks for the logs, the OpenOCD Log should be in the location shown in the attached file.

Can you confirm you have installed the WinUSB Driver using Zadig, for the PicoProbe > Interface 2?

Are all wires connected between the PicoProbe and the target rp2040 as shown on this page?
https://www.visualmicro.com/page/RasPiPico-Debugging.aspx

Thanks for the detail.

The WinUSB Driver needs to be installed on (Interface 2) of the PicoProbe, as shown in the below image:


https://www.visualmicro.com/page/Zadig-Driver-Installation-Guide.aspx

We will be reviewing the newer version of OpenOCD in the near future, however this is not required to use the PicoProbe in Visual Micro, its supported on the current versions integrated.

Thanks for clarifying.

Can you send over the commands you are using to debug your project via cmd (for both OpenOCD and GDB) ?

We should be able to show how to get this running in Visual Micro without changing the driver in theory.

Thanks for the information, from what I understand the only change required is to use the cmsis-dap.cfg file instead of the picoprobe.cfg.

If you add a Local board.txt file to your project (vMicro > Add Code > Add Local Board.txt), and paste in the contents from the attached file.

Then rebuild the project, and try attaching the debugger again with the vMicro > Debugger > Hardware Debugger set to "PicoProbe".

We can add further overrides for the OpenOCD version if required, however I don't believe these will be needed.

board.txt 

# Blink build property overrides
#
params.verbose=-d2
path=C:\ProgramData\VMicro\tools\openocd-rpi-0.10.0.20210623
openocdscript=target/rp2040.cfg
initCmd=-c "init" 
#
# Override the picoprobe.cfg with the cmsis-dap.cfg
# Ensure vMicro > Debugger > Hardware Debugger is set to "PicoProbe"
tools.vmpicoprobe.vmserver.build.openocddebugger=cmsis-dap.cfg


Blink.ino_DebugOpenOCD.log

Error: The specified debug interface was not found (cmsis-dap)
The following debug adapters are available:
1: ftdi
2: usb_blaster
3: ft232r
4: jlink
5: vsllink
6: ulink
7: hla
8: osbdm
9: opendous
10: aice
11: picoprobe
12: xds110
13: st-link


Output [Visual Micro -> Output]

Starting: "C:\\ProgramData\\vmicro\\tools\\openocd-rpi-0.10.0.20210623\bin/openocd.exe" -d2 -l DebugOpenOCD.log}" -s "C:\ProgramData\vmicro\tools\openocd-rpi-0.10.0.20210623/scripts/" -f -dap.cfg" -f fg" -c "init"
Starting: b52\bin\arm-none-eabi-gdb.exe" --interpreter=mi
"C:\\ProgramData\\vmicro\\tools\\openocd-rpi-0.10.0.20210623\bin/openocd.exe" exited with code 1 (0x1).

=====================
the board override has not entirley worked.
Blink.ino_DebugOpenOCD.log shows that openocd cannot find
cmsis-dap
now, that is understandable because it was not in openocd until the new version of OpenOCD 0.12.0

i have looked for a way to change paths for openocd and gdb
in Visual Micro but have not found it

so i am stuck again

thanks

joe

thank youfor your help.

i will wait for the probe to be available in the drop down list.

in the meantime i can use the command line to openocd
and run arm-none-eabi-gdb from the VSMicro output folder.

regards

joe

i have tried the first board override file and
then the second file received just a while ago.

i am using the official Raspberry Pi Debug Probe.

i look forward to the changes.

CMSIS-DAP v2 Interface (Interface 0)

WINUSB (v6.1.7600.16385)