Current consumption at startup

⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at//www.xmece.com/support. We’ll be fixing bugs / optimising the searching and tagging over the coming days.
2 posts / 0 new
Last post
Jun-ichi Tobe
Offline
Last seen:1 year 5 months ago
加入:2016-04-01 10:39
Current consumption at startup

Hi support team!

I created the evaluation board using DA14585.
When I tested using this board, I have a long time consumption current for about 2 seconds.

I think this is a very long time.
The actual measurement results are as follows.
 1.2 mA about 1.8 v
 0.8 mA about 3.0 v
(Refer to the attached measurement result, when using 1.8 V.)
Current measurement waveform for 5 seconds from power on. )

I am considering operation using a small rechargeable battery(7.7mAh, 2.3V).
Since the battery capacity is small, it will not be possible to use this battery if the current consumption time is long.

About setting condition:
· Operation mode: BUCK mode

· Sample program:
ble_app_barebone (SDK 6.0.4.326 included)
The interval is about 400 ms
I write its project to OTP and test it.

Also with Dialog ProKit, the results were the same.

Questions:
What is DA 14585 doing about 2 seconds after turning on the power?
Are there any ways to shorten this long time?
I am thinking that DA 14585 is scanning the boot device in the boot sequence.

Regards.

Jun-ichi

附件:
Device:
MT_dialog
Offline
Last seen:1 year 1 month ago
工作人员
加入:2015-06-08 11:34
Hi Jun-ichi Tobe,

Hi Jun-ichi Tobe,

That 2 seconds that you observe isn't the scan booting time, since that device has allready booted and the fw runs on the 585. As on the 580 SDK the SDK of the 585 will keep the device for 2 seconds without going to sleep in order for the XTAL32 to settle, which is crucial for the LP clock. The value that keeps that device awake (in the default case for 2 seconds) depends on the crystal characteristics used on the board and if you would like change that into a smaller value you will have to test this over quite enough samples and over different temperatures and voltages in order to be on the safe side. The 2 seconds that the SDK keeps the device awake is a more of a generic safe value and can be reduced either via the STARTUP_SLEEP_DELAY_DEFAULT definition or by using the arch_startup_sleep_delay_set() (but again how much it can be reduced depends on the crystal). If the XTAL has not settled properly will result in instabilities of the system, wrong sleep and wake up times.

Thanks MT_dialog