Firmware crash while communicating on BLE when NRF_LOG_ENABLED set to 0

[Pratik Patel]

I am facing strange issue when I execute firmware with NRF_LOG_ENABLED set to 0.

During BLE communication, Firmware is crashing. 

If I enable NRF_LOG_ENABLED, all is working fine.

Has anyone faced such issue?

[Vidar Berg]

Hello,

Yes, it sounds a bit strange that the FW crashes when you turn off logging. Only explanation I can think of is that your issue must be timing related somehow. Could you try to enable the DEBUG (set automatically if you select the 'Debug' build configuration in Segger Embedded studio) and see if the program enters the application error handler (see Error module)?

[Pratik Patel]

I tried your suggestions but found that program is not entering in the application error hander. 

[Vidar Berg]

Ok thanks, but what happens when your FW crashes, does it get stuck somewhere, or does it reboot and make the device connectable again?

[Pratik Patel]

Yes It gets stuck to unknown address. I need to restart the device in order to make it connectable.

[Vidar Berg]

Please post a screenshot showing the CPU register and dissambly view in your IDE when the program is stuck at this unknown address.

[Pratik Patel]

[Vidar Berg]

I see log messages in the debug terminal, so I suppose you have NRF_LOG_ENABLED set to '1' now? Anyway. The CPU registers shows that hardfault exception has been raised in your program. You can try to use our HardFault handling library to help find out what's really causing it.