SOFTDEVICE: ASSERTION FAILED

RE: SOFTDEVICE: ASSERTION FAILED

jimihuard — Wed, 30 Oct 2019 22:28:10 GMT

I can see the bluetooth device now, after some debugging. It looks like this was indeed the issue.

RE: SOFTDEVICE: ASSERTION FAILED

jimihuard — Wed, 30 Oct 2019 22:00:55 GMT

The device does a lot more than act as a keyboard. This is only one piece of it's functionality-- removing the RTOS is not an option unfortunately. I also cannot replace the RTOS with the features provided via softdevice. In short, I have a large back end that is heavily integrated with this RTOS that I am trying to port to the nordic chip, while leveraging softdevice's BLE support.

I think I may have a root cause though-- I only see the assert if I have a breakpoint. I wasn't aware of the major limitation softdevice has, namely that it doesn't play nicely with an attached debugger (problem discussed here https://devzone.nordicsemi.com/f/nordic-q-a/30981/softdevice/122445#122445)

I haven't hit any more asserts after removing breakpoints/other debug hooks.

RE: SOFTDEVICE: ASSERTION FAILED

Turbo J — Wed, 30 Oct 2019 21:53:06 GMT

[quote userid="84624" url="~/f/nordic-q-a/53848/softdevice-assertion-failed"] I am using a proprietary RTOS[/quote]

RTOSes like to run internal housekeeping with interrupts turned off - which is not allowed when using softdevice.

Some interrupt prioroties - especially the default zero one - are only allowed for the softdevice itself.

Why do you need an RTOS for a keyboard anyway? Seems very much overkill here.