Assert Fault using Softdevice

RE: Assert Fault using Softdevice

Vidar Berg — Tue, 10 Nov 2020 12:38:04 GMT

[quote user="dth"]I could imagine that the application might take too long to reply to some BLE-Events or that the application somewhere uses a priority level that is reserved for the softdevice.[/quote]

I does not seem like you should be able to trigger this assertion by not responding SD events. However, using interrupt priorities reserved to the Softdevice might. Or, if you have critical regions in your code which temporarly disable interrupts globally.

RE: Assert Fault using Softdevice

dth — Mon, 09 Nov 2020 18:06:26 GMT

I'm not using the timeslot API and didn't use a debugger either.

I could imagine that the application might take too long to reply to some BLE-Events or that the application somewhere uses a priority level that is reserved for the softdevice. It would just be good to know, whether one of these could result in that assertion.

RE: Assert Fault using Softdevice

Vidar Berg — Mon, 09 Nov 2020 13:54:54 GMT

Hello,

Does you application use the timeslot feature of the Softdevice by any chance? I asked the Stack team about this assert, and they said it could be triggered if the application overstayed its allocated timeslots.

You may also get the same assert if you continue execution after halting the CPU with a debugger.

Best regards,

Vidar