Debugger stops after some wakeups only in debug mode.

[Abhijith.Desai]

Hi,

Using windows 10 OS, and SES v5.40.

I am using nRF52833 device in my project along with nRF5_SDK_for_Thread_and Zigbee_v4.1.0_32ce5f8 SDK.

I am running an application where it has to wakeup every 60 seconds and then goes to sleep.

I have I am trying to run the code in debug mode and printing some stuff for every wakeup as mentioned below.

So it i start my application and leave it for some time i have to see this pringting several times.

Problem : recently the debugger somehow goes to some part of code and it stops debuggiing and even debug reset doesnt work later.

When it gets stuck i cannot see rather the call stack and it stops the cursor pointing to some location in disassembly as below.

 

And the strange thing is it doesnt happend with release mode.

And i started facing this problem recently once i added some lines to my code and seems that if i comment any small part of code(anywhere) it works fine without problems.

Questions : 1. Is this some issue with the debugger settings?

                   2. Something related to the memory constraint? As i can see that memory is not really full and it can still accommodate RAM and Flash.

                   3. Is there any place where we have to set RAM space while we execute in debug mode?

Best regards

Abhijith Desai

[Jørgen Holmefjord]

Hi,

Do your application include BLE/softdevice, or is it Thread-only?

Can you upload the full application, for us to reproduce/debug the issue? Usually, the only difference between debug and release mode is the DEBUG/DEBUG_NRF symbols, and the optimization level of the compiler. Have you made any other modifications to the project configurations?

Best regards,
Jørgen

[Jørgen Holmefjord]

Hi,

Abhijith.Desai said:

we have problems with thread to join the network it halts at some point and doesnt proceed further.

Can you post the log from the application and a sniffer trace showing the on-air communications when this issue occurs?

Abhijith.Desai said:

Also we see different flash size when it is built in debug mode and release mode. 

This is expected if one configuration have the DEBUG/DEBUG_NRF symbols defined and the other does not. These symbols will include additional error handling/assert functions, along with debug strings, which will increase flash usage.

Best regards,
Jørgen