When call the app_timer_start(),return error_code = 0x08,NRF_ERROR_INVALID_STATE?

RE: When call the app_timer_start(),return error_code = 0x08,NRF_ERROR_INVALID_STATE?

Tanasis! — Thu, 26 Oct 2017 21:55:54 GMT

So what was the issue in the end?

RE: When call the app_timer_start(),return error_code = 0x08,NRF_ERROR_INVALID_STATE?

FormerMember — Fri, 04 Nov 2016 13:57:51 GMT

When the timer is being created, it's added to mp_nodes with the state "STATE_ALLOCATED". When starting the timer, app_timer checks mp_nodes, to check if the given timer has state "STATE_ALLOCATED". When you call app_timer_start(..), does timer_id matches the id given in app_timer_create(..)?

RE: When call the app_timer_start(),return error_code = 0x08,NRF_ERROR_INVALID_STATE?

Milk — Wed, 02 Nov 2016 08:51:04 GMT

Thank you for your reply,I used SDK9.0.The function app_timer_start() as follows:

1、uint32_t app_timer_start(app_timer_id_t timer_id, uint32_t timeout_ticks, void * p_context)

2、{

3、uint32_t timeout_periodic;

4、if (mp_nodes == NULL)

5、{

6、 return NRF_ERROR_INVALID_STATE;

7、}

8、if( (timer_id >= m_node_array_size) || (timeout_ticks < APP_TIMER_MIN_TIMEOUT_TICKS))

9、{

10、 return NRF_ERROR_INVALID_PARAM;

11、}

12、if (mp_nodes[timer_id].state != STATE_ALLOCATED)

13、{

14、 return NRF_ERROR_INVALID_STATE;

15、}

// Schedule timer start operation timeout_periodic = (mp_nodes[timer_id].mode == APP_TIMER_MODE_REPEATED) ? timeout_ticks : 0;

return timer_start_op_schedule(user_id_get(), timer_id, timeout_ticks, timeout_periodic, p_context); }

When I run the chip in debug mode,the programm stop at the line 14 as the above shows.I cannot understand why the state of m_sec_req_timer_id is not STATE_ALLOCATED.

RE: When call the app_timer_start(),return error_code = 0x08,NRF_ERROR_INVALID_STATE?

FormerMember — Tue, 01 Nov 2016 08:15:34 GMT

From the code in app_timer_start(..), it will return NRF_ERROR_INVALID_STATE if the timer_id is not properly initialized or if there is no timeout handler:

uint32_t app_timer_start(app_timer_id_t timer_id, uint32_t timeout_ticks, void * p_context)
{
uint32_t timeout_periodic;
timer_node_t * p_node = (timer_node_t*)timer_id;

// Check state and parameters
VERIFY_MODULE_INITIALIZED();

if (timer_id == 0)
{
    return NRF_ERROR_INVALID_STATE;
}
if (timeout_ticks < APP_TIMER_MIN_TIMEOUT_TICKS)
{
    return NRF_ERROR_INVALID_PARAM;
}
if (p_node->p_timeout_handler == NULL)
{
    return NRF_ERROR_INVALID_STATE;
}

// Schedule timer start operation
timeout_periodic = (p_node->mode == APP_TIMER_MODE_REPEATED) ? timeout_ticks : 0;

return timer_start_op_schedule(p_node,
                               timeout_ticks,
                               timeout_periodic,
                               p_context);
}

Could you run the chip in debug mode and set a breakpoint in app_timer_start(..) when your device is about to re-connect to the iPhone? When the program hits app_timer_start(..), you can see why it fails.