app_error_fault_handler at 0x00024a44

[ConcourseOscar]

Good Day

We have an issue where our device will run normally in a full load condition for about 2 hours without issues but will suddenly go into the app_error_fault_handler. We had an infinite loop there allowing us to inspect it and we saw the handler is called from 0x00024a44 which is a Soft Device address. We tested this 3 times and it always failed at that exact address.

This is Soft Device version s140_nrf52_6.1.1_softdevice

We don't know how to debug this issue, any pointers for the nature of this error would be greatly appreciated. 

OP

[tesc]

Hi,

0x24a44 is the fault handler. The assert itself happened at the pc value of 96184, or in hexadecimal 0x177b8.

Are you by any chance using timeslots, or using interrupts conflicting with those reserved by the SoftDevice?

Regards,
Terje

[ConcourseOscar]

Hi  Terje, thank you for your reply.

We are using these interrupt priority levels:

As for timeslots we aren't intentionally adding any timeslot function. We are using 1mb mode, then switching to coded phy when connected to the other device. I'm not sure if that is related. 

We left the devices connected over the weekend and logged 8 disconnections happening at seemingly random intervals.

Thank you.

OP