RE: Application crash at higher optimization levels

tesc — Thu, 21 Jun 2018 12:00:01 GMT

Hi,

Does it also happen on those other log levels when the optimization level is kept at 0?

We have not experienced any such behavior with the SDK or any examples within it, so it is most likely something that you do in your particular application.

Errors that arises when you enable optimization usually means that some crucial code is optimized away because to the compiler it looks like it is unnecessary.

A common mistake that can give behavior similar to this is that you have a loop structure waiting for a variable to change in an interrupt routine. In such cases you should declare the variable volatile, in order to tell the compiler that the variable may change at any time. Otherwise the check may be optimized away entirely, or the variable is kept in a register and not written to or read from memory every time it is used. That way, when the interrupt routine fires and changes the variable, it will not be detected from the other piece of code. In your case it may of course be something completely different, but that is a good first thing to check.

If the above tips does not lead to any discoveries then I am afraid you must share the code for us to give any pointers to what might be wrong.

Regards,
Terje