Setup a Debug environment on Segger Embedded Studio using ARM GCC tools

RE: Setup a Debug environment on Segger Embedded Studio using ARM GCC tools

ppillai — Wed, 24 Mar 2021 17:26:47 GMT

Thanks for the link. I'll check it out.

On your second point, the code is being built completely unoptimized and still shows the same issue while debugging.

RE: Setup a Debug environment on Segger Embedded Studio using ARM GCC tools

Edvin — Wed, 24 Mar 2021 12:31:46 GMT

Basically, awneil is correct.

Once the softdevice is enabled and started, you can't use normal breakpoints, because the softdevice will miss time critical events. It is possible to use Monitor Mode Debugging, but this is not something that I have tested myself. My typical advice is to use logging and reset the application after breakpoints. It takes a bit longer, but that is how it is working with embedded devices and (time sensitive) protocol stacks.

RE: Setup a Debug environment on Segger Embedded Studio using ARM GCC tools

awneil — Tue, 23 Mar 2021 17:52:37 GMT

[quote userid="87534" url="~/f/nordic-q-a/73152/setup-a-debug-environment-on-segger-embedded-studio-using-arm-gcc-tools"]In BLE-enabled projects, if breakpoints are hit, the session becomes unstable[/quote]

You need Monitor Mode Debug:

devzone.nordicsemi.com/.../193088

[quote userid="87534" url="~/f/nordic-q-a/73152/setup-a-debug-environment-on-segger-embedded-studio-using-arm-gcc-tools"]There are also issues where breakpoints are enabled on sections of code that are definitely being encountered, but breakpoints set there are never hit[/quote]

Optimisation?