app_timer_start causes a hard fault

RE: app_timer_start causes a hard fault

Sawada — Mon, 26 Aug 2019 06:59:58 GMT

ret_code_t app_timer_start(app_timer_id_t timer_id, uint32_t timeout_ticks, void * p_context)

It seems that LOCAL_ERROR (0x4) was displayed on Keil because the reference destination of the null pointer was passed to the id of the first argument.
It was solved by taking measures so as not to pass null.
Thank you.

RE: app_timer_start causes a hard fault

Jørgen Holmefjord — Thu, 08 Aug 2019 09:13:46 GMT

user_op_alloc() should only return NULL if the queue is full. Did you try to increase the size of the operation queue config?

RE: app_timer_start causes a hard fault

Sawada — Thu, 08 Aug 2019 09:10:56 GMT

This error occurs when the timer operations queue is not full.

The device connected to a Keil and looked at the queue value of the timer when an error occurred.
m_op_queue.first == m_op_queue.last
If first and last are equal, it means that the timer has not accumulated.
Also, timer start and end are called alternately.

RE: app_timer_start causes a hard fault

Jørgen Holmefjord — Thu, 08 Aug 2019 08:56:48 GMT

Hi,

The API reference for app_timer_start() indicates what will cause this issue:

NRF_ERROR_NO_MEM

If the timer operations queue was full.

There is a sdk_config.h parameter for the library that allows you to change the operations queue size: APP_TIMER_CONFIG_OP_QUEUE_SIZE

Best regards,
Jørgen