S112 crash at address 0x18808

[Gaétan]

Hi,

On a dice projet based on NRF52810. Sometime when I plug the battery charger the firmware crash at address 0x18808 and the call stack is empty !

This address is in softdevice , and I can't determine the cause !

SDK 16.0

Softdevice version: s112_nrf52_7.0.1_softdevice.hex

Please can you explain what is the function at 0x18808 address ?

Regards,

Gaétan

[Hung Bui]

Hi Gaetan,

I have just tested your BL+Settings+App+SD.hex file on my nRF52810 dev kit and it worked fine. 
You can see the screen recording here: 

This is quite strange. Do you have any other hardware board to test ? 
Could you record the screen when you test ? What exactly you meant by "connecting to NUS" 
If you test with the buttonless example (no NUS) do you have any trouble ? 

[Gaétan]

Hi, 
I'm back from holiday...

I have make some tests with 

Gaétan said:

Firmware: BL+Settings+App+SD.zip

and the crash occur only if SES is in debug mode !

Thanks for confirmation:

Hung Bui said:

The error at 0x18808 and 0x188D4 pointing us to the hardfault handler in the softdevices. 

Please can you explain why softdevice don't fire the function app_error_fault_handler() when hard fault is catched ?

Thanks

[Hung Bui]

Hi Gaetan, 
When you are running in debug mode did you stop at any breakpoint and then continue ? 

Have you built your application so that it's friendly for debugging ? (build with no optimization )
The app_error_fault_handler() only handle assertion that thrown by the softdevice or the SDK, not the hardfault. It's not possible to return to the application from the softdevice when you have a hardfault. 

Please try to narrow down the issue by comparing to our DFU Buttonless example. Please try to test if you can reproduce the issue with the example. 

[Gaétan]

Hung Bui said:

When you are running in debug mode did you stop at any breakpoint and then continue ? 

Never. But I download firmware in flash memory. and after I use "attach to debbuger" menu for connect Jlink RTT to debug terminal in SES.

I continue to investigate... and send feedback.

[Hung Bui]

You can use the RTT Viewer application to see the log without having to "attach to debugger" in SES.