Bluetooth 5 BLE mesh: assert 0x0002DC36

Question

Hi all,s 
 
 I have a couple of nrf52840 boards and i was testing the ble mesh light application. The application works fine, but i changed it so it will periodically set the LED on the server side. After a few transmissions (usually around 100 or 200 packets). Then i get the following assert in the light client application: (app_error_weak.c, 95, mesh assert at 0x0002DC36). I did a stack trace wich showed me that it is going wrong in the core_tx.c in line 105: 
 NRF_MESH_ASSERT(m_packet.bearer_bitmap == 0) 
 it should be zero but it is obviously not. zero.., i have no clue why it is happening. It happens when i use a reliable transfer and an unreliable transfer. 
 Has anybody an idea about what is going wrong? 
 Thanks fot the help!

Bjørn Kvaale · Answer

Sorry for the delayed response. This is most likely an IRQ priority settings issue which can be read about more here . 
 When you run mesh_init() in mesh sdk v2.01, the IRQ priority is set to NRF_MESH_IRQ_PRIORITY_LOWEST, which is defined at level 7. However, when a Mesh API function is called in the main loop, the IRQ priority is set to NRF_MESH_IRQ_PRIORITY_THREAD, which is defined at level 15. Level 15 is a less critical interrupt priority level than level 7. This can lead to some mesh events interrupting other mesh events. Since we want the mesh stack to run at the same priority, we need to make sure that IRQ priority is decreased from level 7 to level 15 when running the mesh API in the main loop. This can be done by changing this line in the mesh_init function from: 
 .core.irq_priority = NRF_MESH_IRQ_PRIORITY_LOWEST, 
 to: 
 .core.irq_priority = NRF_MESH_IRQ_PRIORITY_THREAD 
 & updating the main loop to include: 
 while (true)
{
 app_sched_execute();
 bool done = nrf_mesh_process();
 if (done)
 {
 sd_app_evt_wait();
 }
}

Bluetooth 5 BLE mesh: assert 0x0002DC36

Top Replies

core_v2_widget.Hide()