Mesh stack does not work correctly when using the scheduler

[Dmitro Balo]

Mesh SDK 5.0, SoftDevice S140 v7.2.0, NRF52840, SEGGER
------------------------------------------------------------------------------------
Hi,
I'm using the mesh with the scheduler. The main loop looks like this:

for(;;){
    app_sched_execute();
    if (nrf_mesh_process()){
        sd_app_evt_wait();
    }
}

Also, following the recommendations, I added the following configuration:

#define APP_TIMER_ENABLED 1
#define APP_SCHEDULER_ENABLED 1
#define APP_TIMER_CONFIG_USE_SCHEDULER 1

I have a simple model that takes a message and responds with a status message. The problem is that status messages often don't reach the sender, causing the sender to retransmit, and the whole process slows down a lot. I have found that status messages reach the sender of the request just fine when there is any loop timer with a short timeout (allowing the main loop to wake up more often) or if sd_app_evt_wait() is not called at all. It looks like going to sleep is preventing the stack from working properly, maybe nrf is not waking up on some events, or going to sleep is preventing the status packet from being sent.
Let me know if you have any ideas, thanks!

[Dmitro Balo]

When I don't call the sd_app_evt_wait() function it looks like the incoming events can execute quickly which doesn't cause a lot of m_flag_count flags to accumulate in the bearer_event and the bearer_event_handler always returns done=true. However, after waking up from sleep, when bearer_event_handler calls event callbacks, the program enters this branch:

[tesc]

Hi,

Just to be clear, have you been following the Setting interrupt priority levels section of the documentation, including the section Running application and Bluetooth mesh event handling in main loop? Also, the irq_priority field of the nrf_mesh_init_params_t (used by nrf_mesh_init()) was set to NRF_MESH_IRQ_PRIORITY_THREAD, as per the Interrupt priority level list and configuration section?

Regards,
Terje

[Dmitro Balo]

Hello,
I took into account all the recommendations, including the section "Running application and Bluetooth mesh event handling in main loop". I set the priority in nrf_mesh_init_params_t as NRF_MESH_IRQ_PRIORITY_THREAD.

[tesc]

Hi,

Can you provide a minimal example, with instructions for how to reproduce the behavior? That way we can look into it locally.

Regards,
Terje