P33M

It's explicitly set low because otherwise and if plugged into a bus-powered hub, it will usually get ignored by the host OS. That's more irritating to debug for users.

rpi-6.12.y is in active development so will be regularly rebased, hence the massive diffstat. You will need to rebase your branch on top of a recent pull of our 6.12....

The latest version of the debugprobe firmware is not v2.0.0. Please ensure you are using the v2.2.3 release.

https://www.raspberrypi.com/documentation/microcontrollers/debug-probe.html#updating-the-firmware-on-the-debug-probe

That's the CMSIS DAP protocol version and not the probe firmware version. Unfortunate that they can collide. The probe version is reported in the bcdDevice field of the USB device...

I've replicated your setup with a Pico (in bootsel mode), Debugprobe and VScode but don't see your issue. However, I've spotted that the openocd build shipped with the extension is...

If it was previously working, and is no longer working, and you're sure the software environment hasn't changed, then hardware damage is more likely. Check the pins inside the JST...

It isn't, but it's immaterial - the error is the same in both cases. I can replicate the errors with a disconnected SWDIO line. You will also get this behaviour...

Are you using the debugprobe_on_pico.uf2 from https://github.com/raspberrypi/debugprobe/releases/tag/debugprobe-v2.2.3 ? Note that the default swd GPIO assignments on Pico are GPIO2 swclk and GPIO3 swdio and shown pictorially in https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf figure 9....

Example trace of openocd when idle. Pico debugging a Pico 2. Adapter speed is 200kHz due to the lackluster performance of this Saleae Logic 4, but works fine at 1MHz...