app_timer will be high consumption when repeated mode and config WDT with pause at CPU sleep

RE: app_timer will be high consumption when repeated mode and config WDT with pause at CPU sleep

jacksong — Fri, 11 Jan 2019 10:30:51 GMT

ok,thanks for your reply

RE: app_timer will be high consumption when repeated mode and config WDT with pause at CPU sleep

Stian Røed Hafskjold — Wed, 09 Jan 2019 15:17:05 GMT

Hi, when you add nrf_delay_us(128) the CPU is running for 128us. The CPU consumes current and it will add to the average idle current. If your application goes to sleep often I think it's better to use the RUN_SLEEP mode.

RE: app_timer will be high consumption when repeated mode and config WDT with pause at CPU sleep

jacksong — Fri, 28 Dec 2018 09:14:52 GMT

Hello,

thanks a kind friend remind me ,this is a nrf52832 own bug，this mentioned in nRF52832 Rev 2 Errata ---at anomalies[88].

refer to the workaround :Do not enter System ON IDLE within 125 µs after reloading the watchdog, modify my code like this:

	nrf_drv_wdt_channel_feed(m_wdt_channel_id);
        
    nrf_delay_us(128);

It fixed bug , but the consumption is 15uA more than 8uA( fixed by: config WDT with NRF_WDT_BEHAVIOUR_RUN_SLEEP ).

I'm confused to choose which way.

Could anybody let me know why the offical workaround is add a delay other than change the WDT mode?