RE: Issue with blocking wait using app_timer

alnordic — Fri, 20 Sep 2019 14:10:18 GMT

Hi RK, thank you for your answer.

It seems that there was indeed an issue with priority. The timer handler was not executed until my application code returned.

The "Application Timer" documentation also discusses priority.

Instead, I used an RTC directly, whose handler was not blocked.

RE: Issue with blocking wait using app_timer

RK — Thu, 19 Sep 2019 02:17:28 GMT

well you've given no context as to where you're calling this code from. If you're calling it from another timer handler or an IRQ handler with higher priority you're blocking your own interrupts and so you'll never get the callback. 99% that's what you're doing.

The recommended way to implement an accurate blocking wait is not to. Blocking waits waste power and, as you're finding out, can cause you to deadlock yourself or block other events which need processing. Make your code asynchronous, implement state machines and get away from blocking anything.