Dear Sir,
In my project, device was using very short time, maybe 2min per day. But I need keep RTC counter, to record the time user use device but no turn on BLE. It current SDK, I need set device to work in ext sleep mode, and setup app_easy_timer, the current is about 3uA, it's too high. If I set device to work in deep sleep, can I use timer to period wakeup? If yes, because wakeup from deep sleep will cause system reset, how to know the reset reason? How to keep counter variable?
Thanks!
Best regards,
Brent Zheng
Device:
Hi,
You can use a timer to wake up from deep sleep (it is not called deep sleep for the 585, it is called Extended sleep with OTP copy). You will still be able to store data in the retained part of memory and thereby retaining the time counter variable.
/MHv
Dear MHv_Dialog,
So in Extended sleep with OTP copy, only 32KB(block 4) of system RAM was retained, right? If yes, the current should be around 1.4uA right? In 14585 data sheet page 26 wrote: Typical buck-application in extended-sleep mode with 32 kB RAM retained, running from XTAL32K oscillator, 1.4uA.
Please help to confirm it, thanks.
Best regards,
Brent Zheng
Hi,
Using the SDK504 in its current form actually leads to a typical extended_sleep_with_OTP_copy current of about 1.9uA (as it utilizes the entire 32kByte of retention block 4).
/MHv
Dear MHv_Dialog,
But which condition can exceed spec data 1.4uA?
The leak current of uninitialized data in the retention block is lower than initialized data. If you were to have the 32kbyte retention block (4) powered, but only initialized a small fraction of it, the consumption would approximate the 1.4uA. The current SDK 6.0.4 does not provide the handles to acheieve this, however.
/MHv
Ok, noted. Hope Dialog can improve the SDK to make battery life more longer.
I can assure you that our SDK team is working day and night on that :-)