Hi Dialog,
I am using the DA14580 with the DA14580_DialogBeacon_3.40.6 SDK.
I found that DA14580 chip comsumes about 700μA for about 5 seconds,
when a 3V DC voltage starts to supply to the chip.
我想700μ是当前使用initialization.
So the 5 seconds is the necessary time for initializing the processor, oscillators and ect.
Is that correct? Is there anyway to reduce the initialization time or the current it consumes?
Keywords:
Hi Ambient,
the start-up time of the DA14580 to first advertising running a proximity application can be seen below : it takes about 150mS to get to advertising from a cold boot - that is the complete start-up time. Thats the physical limiation of the device. I'm not sure why there is a delay been programmed into the beacon application (I just checked and can verify i also see it).
Let me check why it has been set-up that way. the device is capable to wake and advertise in 150mS, so i need to understand why we have programmed this extra beacon delay.. BR JE_Dialog
Hi Ambient, I just learnt this 5 sec delay has been implemented on purpose for debugging purposes. in case the spi memory is defined, requires some time to attach the debugger. So, it could be removed. JE_Dialog
HI, Quick update ;
By default, we have in the da14580_config.h: #define CFG_SPI_FLASH
This means that the DA14580 keeps reading the beacon parameters from the flash. If there is no flash connected, you will see such delay.
In case you want to get ride of this delay, you should undef this CFG_SPI_FLASH.
BR JE_Dialog