SoftDevice hard fault while porting to mesh

[mdh]

Using S132 v7.2, I'm getting a hard fault at PC 0x00015810 (I see the flag set in SEGGER, and the console outputs a SOFTDEVICE ASSERT FAILED error) that I'm working on manually tracing. I'm borrowing some code from another project of ours to get this one set up, and so the problem is likely something to do with initial mesh setup and initialization that is then causing the later hard fault. I'm hoping I can get the actual assert error information to better pinpoint the problem, because it's been a bit of a wild goose chase up to now.

[tesc]

Hi,

This assert is most likely the mesh stack failing to give the radio back to the SoftDevice in time (i.e. overstaying the timeslot.)

First thing to check would be interrupt priorities: Have you configured the mesh stack correctly? Are you calling any of the mesh stack API from the wrong context? Also, are you by any chance using timeslots yourself, or disabling interrupts anywhere?

Regards,
Terje

[mdh]

Tusen takk Terje. I'll look into those and make sure they're all set up correctly.

[tesc]

Hi,

Did you find anything related to interrupts, or are there still issues to be solved?

Regards,
Terje

[mdh]

Still hunting around - I'm somewhat new on this project and still learning the ropes of both FreeRTOS and the SDKs.

[tesc]

Hi,

Right. Is this a project mixing nRF5 SDK and nRF5 SDK for Mesh? If so, i recommend having a look at Integrating Bluetooth mesh into nRF5 SDK examples.

If FreeRTOS is also part of the mix, then I am afraid things might get a bit more complicated and take some more time for me to answer. Feel free to ask anyway, if something is unclear.

Regards,
Terje