Thanks for the report, have you set more than 2 breakpoints in the sketch?

Can you also attach the XA0376B.ino_DebugOpenOCD.log logfile from the build folder for us to review?

Tried one and two breakpoints, no more.

option 1: WORKS.
Launching Debugger...
Program Running 'XA0376B'
User Experience: The serial debugger was delayed waiting for an incoming line of data. tips: Use WhenHit>=millis to limit the packet data rate. Dont overload the serial by sending your own serial from a fast loop. If the Serial.print() command is used between breakpoints, then ensure that a line termnator is sent using .println() or .print("\r\n"). Optionally, use #if defined(VM_DEBUG) to add code that is only active when debugging. (if this is expected then switch this user experience message off in tools>options>visual micro>micro debug)
14:43:53.719    XA0376B.ino, line 15      loop()
XA0376B is paused at XA0376B.ino, line 15, loop()
XA0376B Running
14:44:00.435 [up:17s:741ms perf:0ms]   XA0376B.ino, line 17      loop()
XA0376B is paused at XA0376B.ino, line 17, loop()
XA0376B Running
14:44:04.698 [up:21s:999ms perf:100ms]   XA0376B.ino, line 15      loop()
XA0376B is paused at XA0376B.ino, line 15, loop()

Set port to disabled and level to none.
Serial debug still works.
Changing back to debug probe it worked first time, 2 breakpoints set and stopped at both. Closed VS, reopened, didn't work back to pause only no breaking.
tried swapping between serial and debug-probe ant debug-probe 'occasionally' works ?

Info : RP2040 Flash Probe: 33554432 bytes @0x10000000, in 8192 sectors
Info : Padding image section 1 at 0x10012cc8 with 56 bytes (bank write end alignment)
Warn : Adding extra erase range, 0x10012d00 .. 0x10012fff
** Programming Finished **
** Verify Started **
** Verified OK **
     The upload process has finished.
# Copy build result to 'Project>Property Pages>Intermediate Directory'
# Destination: "file:///C:/Users/fmc/OneDrive/Projects/vMicro/DBGTST/XA0376B/obj/ARM/Debug/"

 
// MI Debugger Properties
{
  "serverLaunchTimeout": 5000,
  "filterStdout": false,
  "filterStderr": true,
  "targetArchitecture": "arm",
  "stopAtEntry": false,
  "externalConsole": false,
  "MIMode": "gdb",
  "MIDebuggerServerAddress": "localhost:3333",
  "cwd": "C:\Users\fmc\AppData\Local\Temp\VMBuilds\XA0376B\rp2040_rpipico\Debug",
  "MIDebuggerPath": f\bin\arm-none-eabi-gdb.exe",
  "MIDebuggerArgs": "",
  "debugServerPath": "C:\\ProgramData\\vmicro\\tools\\openocd-rpi-0.12.0.20240923\bin/openocd.exe",
  "debugServerArgs": "-d2 -l .ino_DebugOpenOCD.log}\" -s \"C:\ProgramData\vmicro\tools\openocd-rpi-0.12.0.20240923/scripts/\" -f s-dap.cfg\" -c \"adapter speed 5000\" -f cfg\" -c \"adapter speed 5000; init; reset halt\"",
  "setupCommands": [],
  "program": no.elf",
  "logging": {
    "moduleLoad": false,
    "trace": false,
    "engineLogging": false,
    "programOutput": false,
    "exceptions": false,
    "traceResponse": false
  },
  "showDisplayString": true
}

Not sue if it helps, a screenshot from when it works.

I didn't change any settings between serial / hardware.
Both times port disabled and level none.

"C:\Users\fmc\Pictures\Screenshots\Screenshot2025-04-29164013.png"

No, it's not fixed it occasionally will stop at breakpoints, it seems only to happen if I run the serial debugger and then the debug-probe.

tool\4.0.1-8ec9d6f\picotool.exe info -a
Program Information
none

Fixed Pin Information
none

Build Information
none

Device Information
type:        RP2040
revision:    B2
flash size:  2048K
flash id:    0xE660C0D1C77A172F

Hi, no difference, clean and rebuild, tried running and program attach, no change.

Hi, that didn't work so tried some others ... 4.0.1 is the last version that WORKS 

Deleted all breakpints and restarted, it at-least connects but seems to 'lock up':

Type "apropos word" to search for commands related to "word".
=cmd-param-changed,param="pagination",value="off"
Note: automatically using hardware breakpoints for read-only addresses.
0x000000ea in ?? ()

Thread 1 "rp2040.core0" hit Breakpoint 1, main () at \rp2040\main.cpp:83
83          set_sys_clock_khz(F_CPU / 1000, true);
Failed to select multidrop rp2040.dap0

I can't exit debug, have to use taskmgr to kill openocd and sometimes arm0-none.....

Dropped adapter speed to 250k [I'm still using the same pico and debugprobe as in test-project] ?
It seems to get further and WILL stop at a breakpoint in setup but fails to hit the second breakpoint.


Note: automatically using hardware breakpoints for read-only addresses.
0x000000ea in ?? ()

Thread 1 "rp2040.core0" hit Breakpoint 1, main () at \rp2040\main.cpp:83
83          set_sys_clock_khz(F_CPU / 1000, true);

Thread 1 "rp2040.core0" hit Breakpoint 2, setup () at C:\Users\fmc\OneDrive\Projects\vMicro\XA0476B/XA0476B.ino:119
119            Init_NVM();                                                                                                      // Check validity
Failed to select multidrop rp2040.dap0