Softdevice assert with TWI

RE: Softdevice assert with TWI

tesc — Fri, 30 Oct 2020 16:29:36 GMT

Hi,

"However, if you use the nRF5 SDK's app_scheduler module to run the application from the main loop, the low priority parts of the mesh stack should also run from the main loop."

In other words, when using the app scheduler the irq_priority field must be NRF_MESH_IRQ_PRIORITY_THREAD (also stated in the same section of the setting interrupt priority levels documentation page.)

Regards,
Terje

RE: Softdevice assert with TWI

ftjandra — Fri, 30 Oct 2020 00:01:56 GMT

I changed the interrupt priority of the TWI to lowest and that seemed to help a little, but not completely.

So now I am trying to implement the scheduler. I followed the tutorial here: https://devzone.nordicsemi.com/nordic/short-range-guides/b/software-development-kit/posts/scheduler-tutorial

But now I get 'app_error_weak.c, 115, Mesh error 9 at 0x00000000 (:0)' on power up.

Does running mesh require additional changes?

Thanks.

RE: Softdevice assert with TWI

tesc — Tue, 27 Oct 2020 13:23:19 GMT

Hi,

Since it is a SoftDevice assert it sounds like wrong settings for interrupt priorities, or otherwise too much time used in high priority interrupt context blocking the mesh stack from releasing resources back to the SoftDevice.

Please double check Setting interrupt priority levels, and be careful with running interrupts at a higher priority than that of the mesh stack. The schedule handling library is an option for moving interrupt triggered code to main context.

Regards,
Terje