Attaching gdb to running nRF51822

RE: Attaching gdb to running nRF51822

Wed, 04 Mar 2015 20:43:40 GMT

I have just found a solution by Eliot Stock. This is a partial solution for me, since I have several boards running at the same time and only one of them can be connected and debugged at a time. Here is a link to Eliot Stock's solution for reference:

devzone.nordicsemi.com/.../

RE: Attaching gdb to running nRF51822

Fri, 20 Feb 2015 18:47:14 GMT

Thanks for pointing that out, but, yes, unfortunately, that does not work. I imagine there ought to be a way to attach gdb and some Nordic engineers must have done this before.

In case attaching gdb to a running board does not work, the documentation for ble_debug_assert_handler() says that it writes the error code, line number, and filename to flash. I am thinking another way is to hook up the board after the error occurred and read the flash for those values. But I am not sure at the moment where in flash those values are stored at. developer.nordicsemi.com/.../a00111.html

RE: Attaching gdb to running nRF51822

Marius Heil — Fri, 20 Feb 2015 09:16:53 GMT

Hi,

I am using the Eclipse GDB Segger J-Link Debugging Plugin which allows me to check the "Connect to running target" option in the Debugger-Tab. Unfortunately, the accompanying info tip tells me, that this is currently not supported by SEGGER. I hope that this is just my setup and I could get this to run because it would be helpful for errors that only occur on a random basis.