How to knew, what cause event after sd_app_evt_wait()?

RE: How to knew, what cause event after sd_app_evt_wait()?

Hung Bui — Thu, 18 Oct 2018 08:42:38 GMT

When you put the CPU to sleep do you have any radio activity ? Like advertising, in a connection ?

When you call sd_evt_get(&evt_id) please make sure that it's return NRF_SUCCESS. You can be waken up not because of softdevice's event. Please make sure it's not from one of your peripheral, like SPI, RTC, TIMER.

My suggestion for you is to disable the functionality of the code, like disable SPI, RTC, softdevice (don't initialize them) until you can enter sleep mode. Note that if you run the chip in debug mode it won't be able to enter sleep mode.

RE: How to knew, what cause event after sd_app_evt_wait()?

Ars Morozov — Wed, 17 Oct 2018 12:02:07 GMT

Sorry for so long delay, I skipped notification about update in this thread. You can see in the first post that I use SDK 15.2 , softdevice s132 6.1.0.

My application is based on ble_app_template. I try to go to sleep in advertising event handler in case of BLE_ADV_EVT_IDLE event. In my application I use 1 TIMER, SPI0, SPI1 through PPI from timer event, RTC and SPI2 for sd card and also GPIOTE. Before going to sleep I disable RTC, PPI and TIMER.

RE: How to knew, what cause event after sd_app_evt_wait()?

Hung Bui — Thu, 27 Sep 2018 12:12:54 GMT

Hi Arsenii,

Could you tell more about your application ? Which softdevice do you use ? which SDK ?

When testing that were you in any connection ?

Do you have any other peripheral running ?

Have you tried to test with a dummy program (ble_app_template for example) to see if CPU can enter sleep mode ?