S132 sd_app_evt_wait() blocks for seconds during connection

RE: S132 sd_app_evt_wait() blocks for seconds during connection

Ole Bauck — Fri, 09 Dec 2016 12:43:08 GMT

Forgot to refresh the page...

Feel free to close the case if it can be solved in the other thread.

RE: S132 sd_app_evt_wait() blocks for seconds during connection

Ole Bauck — Fri, 09 Dec 2016 12:39:21 GMT

sd_app_evt_wait() does not block. It does the same as __WFE() and in addition checks whether the interrupt that woke up the CPU is SoftDevice specific (like RADIO, TIMER0 or RTC0) or application specific, in which case it will jump to the application/return from the function.

My guess is that you are running code from interrupt context all the time, therefore never executing the app_timer calls or never going to sleep. You can check if this is the case by measuring the current consumption. If the current consumption never goes to 2-3uA (or a couple of 100s uA if you are running timers or similar), then you know that the application is not returning to sleep, i.e. never calling sd_app_evt_wait().

RE: S132 sd_app_evt_wait() blocks for seconds during connection

Jarmo — Fri, 09 Dec 2016 10:32:23 GMT

That question should be reopened, since I am hitting it again.

RE: S132 sd_app_evt_wait() blocks for seconds during connection

Jarmo — Fri, 09 Dec 2016 10:31:55 GMT

This seems to converge into this problem: devzone.nordicsemi.com/.../