Hi Erik, FYI, pyocd is Zephyr-aware and Nordic’s J-Link OBs can be reflashed with pyocd-compatible firmware: https://www.nordicsemi.com/Software-and-tools/Development-Kits/nRF52-DK/Download#infotabs A

#debugging #gdb #nrf52480 #ztest #bluetoothmesh

Hi, We are looking for direction on how best to improve our (multi-threaded) debugging capability. Current setup: host ---NRF52_dev_board (onboard jLink) -- custom Nordic-SoC board where host is macOS

#debugging #gdb #nrf52480 #ztest #bluetoothmesh

All I did was to uncheck the "start pyOCD locally"

#debugging #eclipse #gdb

Hello, I am trying to setup Eclipse with GNU MCU Eclipse plugin as an IDE debugger for Zephyr under Ubuntu 19.04. That is mainly in hopes to be able to debug with multiple threads, since I can't seem

#debugging #eclipse #gdb

Merci Port 3333 was the missing detail :D A small add: Debugging with the "C/C++ Remote Application" have problems resolving symbols and code. You get errors like that: """ Using runner: openocd Open

#west #gdb #eclipse

Hi, Looks like eclipse is set up to use port 6666 for the GDB connection... But 3333 is what is open for incoming gdb connections. It seems openocd has opened 6666 for tcl, not gdb. If you can change

#west #gdb #eclipse

Hej, Currently I am trying to figure out how to setup the debugger by the use of west. I manage to start the west debug server but I failed to connect. Maybe I am missing something or anyone having th

#west #gdb #eclipse