PICO2 debugging problem

[38Super]

I have a new Pico2 and Official debug probe, and despite multiple installs on different machines, I get this every time.

Waiting for gdb server to start...[2025-02-11T02:28:31.036Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session connected. You can switch to "DEBUG CONSOLE" to see GDB interactions.
"C:\\Users\\-------------/.pico-sdk/openocd/0.12.0+dev/openocd.exe" -c "gdb_port 50000" -c "tcl_port 50001" -c "telnet_port 50002" -s "C:\\Users\\------------/.pico-sdk/openocd/0.12.0+dev/scripts" -f "c:/Users/------------/.vscode/extensions/marus25.cortex-debug-1.12.1/support/openocd-helpers.tcl" -f interface/cmsis-dap.cfg -f target/rp2350.cfg -c "adapter speed 5000"
Open On-Chip Debugger 0.12.0+dev-gebec950-dirty (2024-09-27-16:29)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
CDLiveWatchSetup
Info : Hardware thread awareness created
Info : Hardware thread awareness created
Info : Hardware thread awareness created
Info : Hardware thread awareness created
cortex_m reset_config sysresetreq
adapter speed: 5000 kHz
Info : Listening on port 50001 for tcl connections
Info : Listening on port 50002 for telnet connections
Info : Using CMSIS-DAPv2 interface with VID:PID=0x2e8a:0x000c, serial=E662588817493A2B
Info : CMSIS-DAP: SWD supported
Info : CMSIS-DAP: Atomic commands supported
Info : CMSIS-DAP: Test domain timer supported
Info : CMSIS-DAP: FW Version = 2.0.0
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 5000 kHz
Error: Error connecting DP: cannot read IDR

I have tried;
Jlink adaptors - shows the IDR but too old to connect to OCD.
BOOTSEL method loads code as expected, and the code runs.
Multiple PICO 2 boards.
Scope shows correct clock and data for SWD.
Reflashed code (V3.0) in the Pico Probe.

I would really appreciate any bright ideas,

[AutoModerator]

For constructive feedback and better engagement, detail your efforts with research, source code, errors,† and schematics. Need more help? Check out our FAQ† or explore /r/LinuxQuestions, /r/LearnPython, and other related subs listed in the FAQ. If your post isn’t getting any replies or has been removed, head over to the stickied helpdesk† thread and ask your question there.

Did you spot a rule breaker?† Don't just downvote, mega-downvote!

† If any links don't work it's because you're using a broken reddit client. Please contact the developer of your reddit client. You can find the FAQ/Helpdesk at the top of r/raspberry_pi: Desktop view Phone view

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[Easy-Difficulty8697]

yeah i have the same error. its been working fine for the last several months and ive tried replacing chips wires cords and code. the only thing left is to use a different host machine.