SOFTDEVICE: ASSERTION FAILED id = 0X00000001, pc=0X00002F96

RE: SOFTDEVICE: ASSERTION FAILED id = 0X00000001, pc=0X00002F96

YangYu — Sun, 19 Dec 2021 23:30:57 GMT

I see. It is pretty odd. It happened that I fixed the bug late last Friday. QP which is a real-time embedded frameworks (RTEFs) is used in my project. Softdevice was initialized before the firmware went into the QP loop. I got the assertion after the firmware got interrupted by app_timer2. The assertion have never happened after I put all softdevice init functions into the QP loop. I haven't got chance to dig deep in. But I highly suspect that QP may influence how sw interrupt works. Anyway thank you of being helpful and nice.

RE: SOFTDEVICE: ASSERTION FAILED id = 0X00000001, pc=0X00002F96

Einar Thorsrud — Fri, 17 Dec 2021 11:28:31 GMT

Hi,

It should not be a problem with the default configuration. Have you by any chance modified APP_TIMER_CONFIG_SWI_NUMBER in sdk_config.h? (This is only relevant if using app_timer.c, as app_timer2.c does not use SWI.)

RE: SOFTDEVICE: ASSERTION FAILED id = 0X00000001, pc=0X00002F96

YangYu — Thu, 16 Dec 2021 21:58:16 GMT

Hi Einar,

Thank you for your reply.

I check in sdk_config.h. All software interrupts are not excluded by the driver. Could it be the conflict between an app timer and softdevice? Maybe the app timer uses SW15?

RE: SOFTDEVICE: ASSERTION FAILED id = 0X00000001, pc=0X00002F96

Einar Thorsrud — Thu, 16 Dec 2021 12:06:04 GMT

Hi,

This assert is because an interrupt does not have the expected interrupt priority (specifically SWI5). Have you made any changes to that in you firmware?