Mesh SDK 3.0.0 timeslot_sd_event_handler

[luciom]

Hi,

I just completed the migration from mesh sdk 2.2.0 to 3.0.0.

After running the project it get stuck at line 422 of timeslot.c in function timeslot_sd_event_handler().

Can you help?

[Marjeris Romero]

Hi Lucio,

Sorry for the late reply. Could you check if you are registering SD event observer twice? This will happen if you call ble_stack_init() function from the ble_softdevice_support.c

If this is not the case, could you please give any other input in how to reproduce this issue?

Best Regards,

Marjeris

[luciom]

Marjeris,

as mentioned above the application stops on:

NRF_MESH_ASSERT(sd_radio_request(&m_radio_request_earliest) == NRF_SUCCESS);

For completeness I can add that the returned value of sd_radio_request() is NRF_ERROR_FORBIDDEN = 15

Lucio

[Marjeris Romero]

Hi Lucio,

I tried to migrated a project of my own to the new Mesh SDK v3.0.0 today as well.

The new SDK has added a file called ble_softdevice_support.c, which has replaced the initialization phase of the softdevice handler, the BLE stack, the gap module and the connection parameters negotiaton module. The documentation for the module is here https://www.nordicsemi.com/en/DocLib/Content/SDK_Doc/Mesh_SDK/v3-0-0/group__BLE__SOFTDEVICE__SUPPORT#details

The on_sd_evt handler function and observer are already called in ble_softdevice_support.c so I had to remove the following lines from my main.c:

static void on_sd_evt(uint32_t sd_evt, void * p_context)
{
    (void) nrf_mesh_on_sd_evt(sd_evt);
}

NRF_SDH_SOC_OBSERVER(mesh_observer, NRF_SDH_BLE_STACK_OBSERVER_PRIO, on_sd_evt, NULL);

So on_sd_evt don't get called twice. Could you search in your project and see if you are registering the observer twice? This fixed a timeslot assert for me. It was unclear to me if you still have problems with the assert on sd_radio_request assert, but I hope this was more detailed than my first answer.

Best Regards,

Marjeris

[luciom]

Hi Marjeris,

I confirm that the problem was there.

I removed the lines above and now the application works as expected.

I suggest to add this on the migration guide.

Thank you for your support.

Lucio