RE: Conflicts when accessing peripherals from mesh-callback

Mttrinh — Fri, 21 Feb 2020 13:19:02 GMT

Hi,

The "Run application and mesh event handling in main loop" section, should actually help. Did you set IRQ priority to NRF_MESH_IRQ_PRIORITY_THREAD when initializing the mesh stack: https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v3.2.0/structnrf__mesh__init__params__t.html#ad41f7d35516c895ec84ac9b2cd9e77af?

Could you post how the mesh stack is initialized and which call you use for replying on a message?

What could also cause the issue is that the mesh API is not called at the correct IRQ priority. 2 ways how this can be fixed:

1. Use app_scheduler and run the mesh stack at NRF_MESH_IRQ_PRIORITY_THREAD as described on https://infocenter.nordicsemi.com/topic/com.nordic.infocenter.meshsdk.v3.2.0/md_doc_introduction_mesh_interrupt_priorities.html#irq_levels_changes_main_loop page and use the same workaround as provided for `simple_hal` on that page. Use `app_sched_event_put` to put an event to the app scheduler and then call the mesh API from the callback provided to `app_sched_event_put` call.

2. Use Bearer Event API to schedule a callback at the mesh stack IRQ priority level. To do that, register the callback using `bearer_event_flag_add` function (see bearer_event.h). Whenever the callback needs to be scheduled, run `bearer_event_flag_set` function with the event returned by `bearer_event_flag_add`.

RE: Conflicts when accessing peripherals from mesh-callback

Mttrinh — Thu, 20 Feb 2020 16:00:18 GMT

Hi,

I have forwarded this to our Mesh team, I will update you when I get a response from them.