low power delay implementation

RE: low power delay implementation

endnode — Tue, 31 Oct 2017 16:44:09 GMT

Then I can only say that this construction is perfectly working for me, hard to say what detail broke it in your project. Hopefully the GPIO debug and logical analyzer will hint something...

RE: low power delay implementation

erltot — Tue, 31 Oct 2017 15:29:00 GMT

see comment right under uint32_t err code; in main

RE: low power delay implementation

endnode — Tue, 31 Oct 2017 15:25:07 GMT

If your app is based on any BLE example then it seems to be heavily customized because in your main function there seems to be no Soft Device init. If that is true then it's logical that sd_app_wait call in your power_manage doesn't do anything (or returns error status which should cause hard fault and reset).

RE: low power delay implementation

erltot — Tue, 31 Oct 2017 13:27:54 GMT

I built my app on the ble_app_uart peripheral example, power_manage is unchanged:

/**@brief Function for placing the application in low power state while waiting for events.
 */
static void power_manage(void){
    uint32_t err_code = sd_app_evt_wait();
    APP_ERROR_CHECK(err_code);
}

I'll attach a probe to a pin to check the actual delay time and get back to you about that

RE: low power delay implementation

endnode — Tue, 31 Oct 2017 11:12:11 GMT

Sorry, your code looks good. What do you mean by it doesn't work? Can you measure with some precise tool (like logical anayzer) what is actual delay on UART or RTT between start of "waiting" and "timer_ledelay" debug strings? This construction works in many apps I use... If you don't use SD can you make sure what is actually running in your power_manage function? It should be something like examples\multiprotocol\ble_app_gzll\main.c SDK example.