DAP init failed with OpenOCD and arduino-pico about pico-debug HOT 3 CLOSED

Alas, I don't have a good answer for you. I lack a Windows 11 platform to test with, and I'm loath to "upgrade" the one Windows 10 PC that I have which meets the Windows 11 system requirements.

In an earlier issue #18, a user was able to use Windows 11 after upgrading to the then latest pico-debug release (v10.04).

I would ask that you double-check the pico-debug release that you are using, and verify that (after loading the pico-debug .uf2) it appears in Device Manager without any warnings or errors.

from pico-debug.

after upgrading to the then latest pico-debug release (v10.04).

just checked, and i've been using 10.05!

verify that (after loading the pico-debug .uf2) it appears in Device Manager without any warnings or errors.

no errors! something to note is that pio is unable to upload with the above error yet if i use openocd manually:

PS C:\Users\aria\Downloads\xpack-openocd-0.11.0-5\bin> .\openocd.exe -f board/pico-debug.cfg
xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2022-09-01-17:58)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
cortex_m reset_config sysresetreq

Info : Listening on port 6666 for tcl connections
Info : Listening on port 4444 for telnet connections
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: FW Version = 2.0.0
Info : CMSIS-DAP: Serial# = E661640843675228
Info : CMSIS-DAP: Interface Initialised (SWD)
Info : SWCLK/TCK = 0 SWDIO/TMS = 0 TDI = 0 TDO = 0 nTRST = 0 nRESET = 0
Info : CMSIS-DAP: Interface ready
Info : clock speed 4000 kHz
Info : SWD DPIDR 0x0bc12477
Info : [rp2040.cpu] Cortex-M0+ r0p1 processor detected
Info : [rp2040.cpu] target has 4 breakpoints, 2 watchpoints
Info : starting gdb server for rp2040.cpu on 3333
Info : Listening on port 3333 for gdb connections

it works just fine!

from pico-debug.

Sorry, I just do not have the time to replicate the myriad of different environments of pico-debug users, and then investigate why that software doesn't play nice with pico-debug.

from pico-debug.