GDB + softdevice ?

RE: GDB + softdevice ?

Øyvind Karlsen — Mon, 08 Feb 2016 14:10:27 GMT

You can refer to this answer for more info.

RE: GDB + softdevice ?

ypearson — Mon, 08 Feb 2016 13:35:24 GMT

This is exactly the type of answer I was looking for. Thank you! There any documentation discussing this ?

RE: GDB + softdevice ?

Øyvind Karlsen — Mon, 08 Feb 2016 08:00:48 GMT

Hi,

Because of how the SoftDevice works you are not able to debug it by stepping the code. This is because it will report a fault upon failing timing checks. These timing checks are critical in order to be able to operate a BLE connection.

Best regards,

Øyvind

RE: GDB + softdevice ?

RK — Sun, 07 Feb 2016 23:57:23 GMT

In general you can't single-step through softdevice calls, or break while the softdevice is running, with any debugger because the softdevice has timing requirements which single stepping breaks.

Here's a recent blog about monitor mode debugging which attempts to work around this

devzone.nordicsemi.com/.../

but it's an advanced technique. This all has nothing to do with GDB.

RE: GDB + softdevice ?

ypearson — Sun, 07 Feb 2016 19:10:00 GMT

GDB seems to reset the chip on a SVCALL. I step through code, but resets up calling a SVCALL.

RE: GDB + softdevice ?

ypearson — Sun, 07 Feb 2016 19:08:03 GMT

Sorry, I wasn't clear.

I'm using GCC+GDB+OpenOCD to step through code, and it appears if GDB steps through a SVCALL the microcontroller resets but if I run the example code without using GDB the code works fine.

Were you successful in using GDB with softdevice ? If so how did you mange that?

To program the micro I would use nrfjprog.

thanks!

Hi, Because of how the SoftDevice works you are not able to debug it by stepping the code. This is because it will report a fault upon failing timing checks. These timing checks are critical in order to be able to operate a BLE connection. Best regards, Øyvind Øyvind Karlsen (5 hours ago)

RE: GDB + softdevice ?

RK — Sun, 07 Feb 2016 12:52:39 GMT

GDB doesn't read the hex file, it's only used for uploading the code to the chip, so if you have GDB issues, it has nothing to do with merged hex files.

RE: GDB + softdevice ?

Wojtek — Sun, 07 Feb 2016 12:27:08 GMT

If by GDB you mean compiling on GCC, it does not interfere with softdevice. You just separately flash app compiled in GCC and funcions calling to softdevice communicate with it by SVCALLs. Just keep memory layout as specified in softdevice specification.

RE: GDB + softdevice ?

ypearson — Fri, 05 Feb 2016 22:05:45 GMT

It appears GDB could interfere with the programmed softdevice.