NRF9160 Segger and building for Debug (Debug is missing)

[GJSea]

I'm trying to debug my NRF9160 Zephyr app in Segger Studio but finding Step Over/Into is behaving like a Release build and jumping all over the place as would be expected for optimized code... when I looked to change my build configuration only 'Common' is available to be selected vs the typical Debug/Release options. Any idea as how to build and deploy true Debug instrumented code, or am I missing something obvious?

Thanks!

[Simon]

You can add another build configuration by clicking "Edit Build Configurations" and then add a configuration called Debug by clicking the +button.

[GJSea]

Thanks... I added a debug configuration under Public Configurations and it appeared in the dropdown, but where do I specify to the compiler to build with debug symbols, turn of optimzations etc? Thx!

[Simon]

I just tested this myself using the Nordic Edition of SEGGER Embedded Studio (arm_segger_embedded_studio_v414_win_x64_nordic) and the asset tracker, and debugging worked fine. I tested "step over", "step into" and "step out".

Did you use the same version of SES? Did you follow the Getting started guide for nRF Connect SDK?

Best regards,

Simon

[GJSea]

Hi Simon

I have 4.14 of the Nordic Segger, but the debugger is still behaving as though it is release optimized code. Where in the Segger  IDE does one specify whether to build Release or Debug code? Where does one control the compiler optimizations. If I select Project..Options in the various parts within the Project Items tree I don't see any compiler/linker options.

Thx!

[Simon]

Take a look at this thread, where Håkon explains how to turn off the optimization. 

Best regards,

Simon