[ISSUE] Debugging BSom (B404) using VSCode

Using VSCode on Windows 11. Had no problem doing local debug using Particle Debugger with Boron module.
Switched to B404 module and can’t start debugging session. This window pops up:
image
and debug console reports:
Reading symbols from C:/Users/chida/.particle/toolchains/gcc-arm/10.2.1/bin/arm-none-eabi-objdump.exe --syms -C -h -w c:/MyData/EQR/Particle/B40x/alertv2_3/target/5.3.0/bsom/alertv2_3.elf
Reading symbols from c:/users/chida/.particle/toolchains/gcc-arm/10.2.1/bin/arm-none-eabi-nm.exe --defined-only -S -l -C -p c:/MyData/EQR/Particle/B40x/alertv2_3/target/5.3.0/bsom/alertv2_3.elf
Launching GDB: “C:\Users\chida\.particle\toolchains\gcc-arm\10.2.1\bin\arm-none-eabi-gdb.exe” -q --interpreter=mi2
IMPORTANT: Set “showDevDebugOutput”: “raw” in “launch.json” to see verbose GDB transactions here. Very helpful to debug issues or report problems
Launching gdb-server: “C:\Users\chida\.particle\toolchains\openocd\0.11.0-particle.4\bin\openocd.exe” -c “gdb_port 50000” -c “tcl_port 50001” -c “telnet_port 50002” -s “C:\Users\chida\.particle\toolchains\openocd\0.11.0-particle.4\share\openocd\scripts” -f “c:/Users/chida/.vscode/extensions/marus25.cortex-debug-1.10.0/support/openocd-helpers.tcl” -f “interface\cmsis-dap.cfg” -f “target\nrf52-particle.cfg”
Please check TERMINAL tab (gdb-server) for output from C:\Users\chida.particle\toolchains\openocd\0.11.0-particle.4\bin\openocd.exe
Finished reading symbols from objdump: Time: 53 ms
Finished reading symbols from nm: Time: 76 ms
OpenOCD: GDB Server Quit Unexpectedly. See gdb-server output in TERMINAL tab for more details.

Terminal tab shows:
Waiting for gdb server to start…[2023-04-04T19:17:21.688Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session connected. You can switch to “DEBUG CONSOLE” to see GDB interactions.
“C:\Users\chida\.particle\toolchains\openocd\0.11.0-particle.4\bin\openocd.exe” -c “gdb_port 50000” -c “tcl_port 50001” -c “telnet_port 50002” -s “C:\Users\chida\.particle\toolchains\openocd\0.11.0-particle.4\share\openocd\scripts” -f “c:/Users/chida/.vscode/extensions/marus25.cortex-debug-1.10.0/support/openocd-helpers.tcl” -f “interface\cmsis-dap.cfg” -f “target\nrf52-particle.cfg”
xPack OpenOCD x86_64 Open On-Chip Debugger 0.11.0+dev (2022-03-25-17:32)
Licensed under GNU GPL v2
For bug reports, read
OpenOCD: Bug Reporting
CDRTOSConfigure
Info : auto-selecting first available session transport “swd”. To override use ‘transport select ’.
DEPRECATED! use ‘adapter speed’ not ‘adapter_khz’
Info : Listening on port 50001 for tcl connections
Info : Listening on port 50002 for telnet connections
Error: unable to find a matching CMSIS-DAP device
[2023-04-04T19:17:21.815Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session closed
GDB server session ended. This terminal will be reused, waiting for next session to start…

Is there any tutorial on how to debug a B40x module? The only one I’ve found is for a Boron, and that was very old…