Debug configurations in SES

[perf]

How can I add debug and release configurations to the "mqtt_simple" project?

Video tutorial "SEGGER Embedded Studio - Build configurations" does not show this important step.

In the video, debug and release exists and can be further configured but how the rebug and release became defined in the first place is not mentioned.

Please show how.

[Simon]

Be aware that the SEGGER Embedded Studio video series uses the original version of SES, and in order to build with NCS the Nordic Edition has to be used. These editions are not the same, and they will vary slightly.

In order to add your own Build Configurations in SES Nordic Editions, follow these steps:

Best regards,

Simon

[perf]

I think the way you point me will be too demanding. I do not have the knowledge required to go that way.

I believe the best way is to create a new project in SES with File->New Project, then select an Nordic C executable template and specify all options needed (difficult for a newcomer). Then - copy the required files from mqtt_simple. 

Btw: Why are the samples provided stripped in such a way that they are difficult to use as a template?

I have tried to make my own project and succeeded in some way, but the result in SES is unstable as the J-link download works just once - for example. 

It would be nice to get some help to do what I asked for - or beeing pointed to a good example project that can be a template that have Debug/Release settings and J-link that works.

Regards

Per.

[Simon]

I will look into this, in the meanwhile, you could take a look at the NCS tutorial, which helps you get started with the nRF9160 and NCS.

Best regards,

Simon

[Simon]

The way this works in NCS/Zephyr is through configurations. Take a look at the configurations under menu "Debugging Options" in the file ncs/Zephyr/subsys/debug/Kconfig, which can be selected to enable various debugging features. Also, take a look at the configurations under menu "compiler options" in the file ncs/Zephyr/Kconfig.zephyr.

E.g. if you would like to disable optimizations you set  CONFIG_DEBUG=y, or if you would like to get more information about the stack usage you set CONFIG_STACK_USAGE=y.

The only thing I do before debugging is to set CONFIG_DEBUG_OPTIMIZATION=y.

Best regards,

Simon