Segger Release Build not working

[fgeldenh]

I have two projects exhibiting the same problem.

I have custom board using the nRF52832 and another using the nRF52840. In both cases I am using nRF5 SDK latest version and Segger Embedded Studio 8.32.

If I build the application using a Debug build it works fine. However, if I do a Release build the application does not work properly. It is as if the memory is being overwritten.

In the case of the nRF52832, I am not even using the Bluetooth stack, so it is a very simple application. The nRF52840 application is more complex and does use the Bluetooth stack.

I know this sounds strange, but I can reproduce at will.

Can you give me any hint as to where to start looking. I can make the project and source code available.

[Jørgen Holmefjord]

Hi,

Typically, the difference between Release and Debug build in SES is that optimization is enabled for Release but not for Debug, and some additional symbols (DEBUG, DEBUG_NRF) is defined in Debug build.

The optimization could cause some issues, but it is not possible to say anything about this without seeing your code and getting some more details about what is failing/not working.

Best regards,
Jørgen

[fgeldenh]

Jurgen - You hit the nail on the head. Pretty dumb of me not to spot it. Setting the optimization to None fixed both issues.

Please close this ticket and thanks for your help.

[awneil]

fgeldenh said:

Setting the optimization to None fixed both issues

That probably means that there are issues in your code which should be addressed - you have probably just masked the symptoms.

eg, see: https://community.arm.com/developer/tools-software/tools/f/keil-forum/48052/beginner-simple-question/169408#169408

fgeldenh said:

Please close this ticket

You do that by verifying the answer: