NRF_FAULT_ID_SD_ASSERT thrown from PC 0xBBDC

[Elkana]

Hi,

I am using nRF52840, SDK 15.0, softdevice 6.0.0 (toolchain IAR 7 on windows).

My application runs on FreeRTOS 9.0.0 tickless (NRF_SDH_DISPATCH_MODEL 2).

I have a specific scenariothat throws error of type 0x0001=NRF_FAULT_ID_SD_ASSERT, PC = 0xBBDC and info = NULL.
The scenario doesn't include any BLE usage.

Do you have any clue on what could go wrong?

Is there a way to debug those SD asserts?

Thanks,

Elkana

[Susheel Nuguru]

The PC address is something new to me, so most likely this is something new you are seeing. 

can you help me reproduce this issue by attaching a minimalistic project to reproduce this?

[Elkana]

Not in the near future (stripping it may take a few days and I can't afford it right now).
I can tell you that it happens when the device is initially reset on external power + batteries, than when power is removed the assert occurs.
It is probably related to the way the module is initialized, because when initial reset is on batteries only - it is not reproduced even if you turn off and on the external power many times.

[Susheel Nuguru]

Elkana said:

If this is related to LF Clock configuration - could it be that temporary glitch in the oscillator (due to electrical behavior when power source switches) cause this SD_ASSERT ?

That is possible, Try to change the LF clock source to something else (like internal RC) and see if you still see it.

[Elkana]

MCU clock configuration is not a light thing to change.

sd_softdevice_enable fails with NRF_SDH_CLOCK_LF_SRC = 0, so I can't even start testing it 

[Susheel Nuguru]

I am out of theories then, I need to test this on my side to be able to reproduce and step into the softdevice code. We can change this to private case if you want. Please talk to your RSM if you worry about NDA 

[Elkana]

As I am working on a custom board (the image will fail very fast on Evalution Board)- I don't see how this can be done.

[Susheel Nuguru]

You need to send me the custom board and the software for me to be able to reproduce it and debug it RTOS part to see how it behaving with your application.