anyone having problem with the APP_TIMER in SDK14

RE: anyone having problem with the APP_TIMER in SDK14

yacine — Mon, 05 Feb 2018 15:11:29 GMT

question continues here

RE: anyone having problem with the APP_TIMER in SDK14

yacine — Mon, 05 Feb 2018 11:29:44 GMT

Hello Sigurd,

Thanks for your reply. I verified: app_timer_create is called, the timer _id is not 0, the callback is not NULL.

I discovered the following with more tests:

1) this code works only if the temporary variable timer_data is declared static (just like in APP_TIMER_DEF macro. is not static app-timer_create returns SUCCESS, but app_timer_start will return NRF_ERROR_INVALID_STATE. see below ths code:

ret_code_t err_code;
static app_timer_t timer_data = { {0} };
m_timer_id = &timer_data;
err_code = app_timer_create(&m_timer_id, APP_TIMER_MODE_REPEATED, cbk_measure);

(...)
ret_code_t err_code;
err_code = app_timer_start(m_timer_id, APP_TIMER_TICKS(m_probing_interval_ms), (void *) this);

2) now the problem is that m_timer_id is a member of my c++ class and my code breaks when I create a second instance of this class and try to call app_timer_create. it seems like app_timer_create returns NRF_ERROR_INVALID_STATE when the timer_id is already used by another app_timer. Actually the timed_id generated in the second instance constructor has the same value of the previous instance and this leads to app_timer create returning

see below the logs:

// first instance
<debug> FIXME: m_timer_id (before app_timer_create)= 536884956
<debug> FIXME: app_timer_create returns 0
<debug> FIXME: m_timer_id (before app_timer_start) = 536884956
<debug> FIXME: app_timer_start returns 0

// second instance
<debug> FIXME: m_timer_id (before app_timer_create)= 536884956
<debug> FIXME: app_timer_create returns 8

I need to geenerate a different m_timer_id for each class instance. how can I do ?!?!

RE: anyone having problem with the APP_TIMER in SDK14

Sigurd — Mon, 05 Feb 2018 09:39:24 GMT

Hi yacine,

Error code 8 is NRF_ERROR_INVALID_STATE. You will get this error code if have not initialized the timer module(app_timer_init()). You could also get this error code if your timer_id is 0, or if the timeout_handler function is NULL.

RE: anyone having problem with the APP_TIMER in SDK14

yacine — Thu, 01 Feb 2018 20:18:11 GMT

hello

yes I have problems with my app_timers in SDK14.2 (migration from 12),

I well noticed that the prototypes of the functions create and start changed from sdk12.

	// create timer
	static app_timer_t timer_data = { {0} };
	m_timer_id = &timer_data;
	err_code = app_timer_create(&m_timer_id, APP_TIMER_MODE_REPEATED, cbk_measure);
	APP_ERROR_CHECK(err_code);

this works well

ret_code_t err_code;

	err_code = app_timer_start(m_timer_id, APP_TIMER_TICKS(m_probing_interval_ms), (void *) this);

	NRF_LOG_DEBUG("FIXME: app_timer_start returns %d", err_code);
	//	APP_ERROR_CHECK(err_code);

but the start returns error code 8 (invalid param if i remember correctly) and I dotn understand why.

BTW my timer_ids are C++ class members. I cannot simply use the APP-TIMER_DEF macro. but it was already the case ion SDK12 and worked AFAIK

thx,

yacine

RE: anyone having problem with the APP_TIMER in SDK14

Sigurd — Thu, 16 Nov 2017 16:13:42 GMT

Hi,

There was no changes in the app timer library between SDK 13 and SDK 14. So it could be something else that is causing the application to stop.

So if you are having trouble with the application stopping, you should debug and see if you maybe are running in the error-handler? See this post.