sdk 12.3.0
nrf52832
problem:
when I multiple call app_timer_stop.it will return NRF_ERROR_NO_MEM.how to result it?
thx everybod!
sdk 12.3.0
nrf52832
problem:
when I multiple call app_timer_stop.it will return NRF_ERROR_NO_MEM.how to result it?
thx everybod!
Hey King,
Calls to the app timer library are queued. If you receive a NRF_ERROR_NO_MEM it means that you have exceeded the queue size.
You need to increase the queue size parameter when calling APP_TIMER_INIT().
I also recommend you to migrate to SDK14.2 or SDK15.0.
Cheers,
Håkon.
Hey King,
Calls to the app timer library are queued. If you receive a NRF_ERROR_NO_MEM it means that you have exceeded the queue size.
You need to increase the queue size parameter when calling APP_TIMER_INIT().
I also recommend you to migrate to SDK14.2 or SDK15.0.
Cheers,
Håkon.
thx,when I add queue size from 2 to 4 or more
it happens again.
I dont know if I have not app_timer_start
then call app_timer_stop more than once.
what happened if have not start app_timer_start then always call app_timer_stop
Try increasing the queue size to 10 or more.
I do not understand what you are trying to say. I suggest that you read the definition of app_timer_stop in app_timer.c found in SDK12.3\components\libraries\timer\
thx haakonsh
I want to say like this case
app_timer_stop(id);
app_timer_start(id);
app_timer_stop(id);
app_timer_stop(id);
app_timer_stop(id);
it can work normal?
thx for you answer.
What is it that you want to achieve? Why do you want to start and stop the timer in such manner, it makes no sense to me.
haakonsh Makes no sense. But this may happen due to async (event driven) programming. The question was, what happens if someone tries to stop a stopped timer.