RE: Init/deinit openthread stack causes a failed assert

Marjeris Romero — Wed, 17 Nov 2021 09:30:37 GMT

Hi,

I am so sorry for not getting back to you on this one, it looks like I forgot to reply. I don't see anything it your code snippets that seem unormal to me. Are you still struggling with this? Could you give me an update on how it's going with your project?

Again I am so sorry I didn't see this ticket wasn't reply to before now...

Best regards,

Marjeris

RE: Init/deinit openthread stack causes a failed assert

MarcoLG — Mon, 31 May 2021 13:15:03 GMT

Hello,

sure, i'll try to share you the relevant parts. However, this is not my application code, but simply a modified Thread CLI example that i did in order to reproduce the problem.

The main function creates a timer, "connect_timer_id", used to decide when to connect. In the main loop, this is the code:

    while(true) 
    {
        if (connect_timer_expired)
        {
            connect_timer_expired = 0;
            if (thread_state == STATE_DISCONNECTED)
            {
                thread_state = STATE_CONNECTING;
                thread_network_up();
            }
            else if (thread_state == STATE_CONNECTED)
            {
                thread_state = STATE_DISCONNECTED;
                thread_network_down();
                err = app_timer_start(connect_timer_id, APP_TIMER_TICKS(7000), (uint32_t *)0x1);
                APP_ERROR_CHECK(err);
            }
        }
        
        if (thread_instance_initialized) {
            thread_process();
        }
        
        NRF_LOG_PROCESS();
    }

connect_timer_expired is set in interrupt context upon timer expiration.

The thread_network_up() function configures the thread network parameters and starts a radio scan using otLinkActiveScan. Once the scan finds the configured thread network, the system enables the remaining thread stack by calling thread_interface_enable(), defined as:

static void thread_interface_enable(bool enabled)
{
    otError error;
    /* Start the Thread network interface (CLI cmd > ifconfig up) */
    otInstance *instance = thread_ot_instance_get();

    error = otIp6SetEnabled(instance, enabled);
    APP_ERROR_CHECK(error);

    /* Start the Thread stack (CLI cmd > thread start) */
    error = otThreadSetEnabled(instance, enabled);
    APP_ERROR_CHECK(error);
    
    NRF_LOG_INFO("Thread interface %s", enabled ? "enabled" : "disabled");
}

Once the device is connected to the thread network, the timer is started again to schedule a disconnection. This is part of the thread_state_changed_callback function:

static void thread_state_changed_callback(uint32_t flags, void * p_context)
{
    otDeviceRole role = otThreadGetDeviceRole(p_context);
    NRF_LOG_INFO("State changed! Flags: 0x%08x Current role: %d\r\n",
                 flags, role);
    
    [...]
    if (role >= OT_DEVICE_ROLE_CHILD)
    {
        thread_state = STATE_CONNECTED;
        uint32_t err = app_timer_start(connect_timer_id, APP_TIMER_TICKS(1500), (uint32_t *)0x1);
        APP_ERROR_CHECK(err);    
    }
    
    [...]
}

Basically this is it.

RE: Init/deinit openthread stack causes a failed assert

Marjeris Romero — Mon, 31 May 2021 12:03:54 GMT

Hi,

Yes, it looks like something isn't finished from the previous operation. Could you perhaps share your code with us to review and see what you are doing?

Best regards,

Marjeris