Odd error message

Software IDE 2.x
1

Started to get a very cryptic message

Waiting for gdb server to start...[2023-04-22T13:47:00.003Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session connected. You can switch to "DEBUG CONSOLE" to see GDB interactions.
"C:\\Users\\rtcno00225\\AppData\\Local\\Arduino15\\packages\\arduino\\tools\\openocd\\0.10.0-arduino7/bin/openocd" -c "gdb_port 50000" -c "tcl_port 50001" -c "telnet_port 50002" -s "d:\\Arduino sketches an libs\\GPSLocation" -f "C:/Program Files/Arduino IDE/resources/app/plugins/cortex-debug/extension/support/openocd-helpers.tcl" -f "C:\\Users\\rtcno00225\\AppData\\Local\\Arduino15\\packages\\arduino\\hardware\\samd\\1.8.13/variants/mkr1000/openocd_scripts/arduino_zero.cfg"
Open On-Chip Debugger 0.10.0+dev-gf0767a31 (2018-06-11-13:36)
Licensed under GNU GPL v2
For bug reports, read
        http://openocd.org/doc/doxygen/bugs.html
CDRTOSConfigure
Info : auto-selecting first available session transport "swd". To override use 'transport select <transport>'.
none separate
adapter speed: 400 kHz
cortex_m reset_config sysresetreq
Info : Listening on port 50001 for tcl connections
Info : Listening on port 50002 for telnet connections
Error: unable to find CMSIS-DAP device

[2023-04-22T13:47:00.383Z] SERVER CONSOLE DEBUG: onBackendConnect: gdb-server session closed
GDB server session ended. This terminal will be reused, waiting for next session to start...

Anyone ?

2

Hi @Ballscrewbob. What were you doing when you saw the error message?

This error would normally occur when the user clicks the "Start Debugging" button without a debug probe connected between the computer and the MKR1000 board:

image

1 Like
3

That was it !

Not 100% up to speed on 2.x
Though it may just parse the code.

4

OK, great. I'm glad we identified the cause. In case you haven't seen it already, I'll share the link to some more information about the Arduino IDE's integrated sketch debugger feature:

It is necessary to connect a CMSIS-DAP compliant or J-Link debug probe to the SWD header on the MKR1000 board in order to use the feature.

If you have an Arduino Zero board, that board has an on-board debug probe so is more convenient to use with the debugger.

1 Like
5

This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.