About sleep release in "sd_app_evt_wait"

[takashina hiroki]

I am now facing the following issues:
https://devzone.nordicsemi.com/f/nordic-q-a/55975/about-reset-during-advertising

I call "sd_app_evt_wait" and go to sleep.
Even when the sleep is released at the SoftDevice level, the sleep may not be released at the application level.
In the link above, I'm giving an example of advertising.

Is there any possibility that the same phenomenon occurs outside of this example?
If so, please tell us about the case.

Also, please tell me if there is a way to wake up at the application level when the sleep is waked up at the SoftDevice level.

[Susheel Nuguru]

Hi Takashina-san,

I do not think that you can call nrf_drv_wdt_init with wdt_event_handler set to NULL. That is how I see you set it in your code from the previous thread.

I see that when you use WDT you see increase in power consumption.

1. How much increase do you see it? And how much did you expect?
2. What are the wakeup sources in your application?
3. When exactly do you feed the WDT by calling nrfx_wdt_channel_feed()?

[takashina hiroki]

I wanted to talk about WDT in the thread at the link above.
This thread wanted to talk about wake up, not WDT.

>> I see that when you use WDT you see increase in power consumption.
The cause is "__WFE ()" and "__SEV ()" instead of WDT.

>> 1. How much increase do you see it? And how much did you expect?
The current consumption increased from 5.5μA to 200μA.
I was expecting the same current consumption as before the change.

>> 2. What are the wakeup sources in your application?
Below are the wake-up sources.
"nrf_sdh_soc_evt_handler_t", "nrf_ble_gatt_evt_handler_t", "pm_evt_handler_t"

>> 3. When exactly do you feed the WDT by calling nrfx_wdt_channel_feed ()?
It is the timing to return from "sd_app_evt_wait".