DA14531 sleep mode exit

Hi Gowtham,

If you've not already done so, I'd recommend reviewing the following document:

http://lpccs-docs.dialog-semiconductor.com/Tutorial_SDK6/index.html

The first couple of chapters provide a high level explaination of the operation of the SDK and the associated callbacks, and give some details of sleep modes.

I'd also recommend the empty_peripheral_template as a starting point for any code you are going to write yourself (and this is the basis of the tutorial i mentioned above).

Best regards
IM_Dialog

Hi tsgowtham,

I assume that, when you are using the Power Profiler, you are running code on the DA14531 under the control of the debugger. This is OK, however once you start the code running you need to disconnect the debugger by pressing "Ctrl+F5", otherwise the debugger remains active and draws current.

Best regards
IM_Dialog

Hi tsgowtham,

Please refer to my answer to your questions below：

• From the tutorial link you have given, I understood that for waking from Extended sleep, the code performs a periph_init and continues execution. But what is done for the other sleep modes?? This has not been mentioned.
• [ycai]其他睡眠模式,而延长leep mode, there will be one more reboot process. Reboot process will re-copy the firmware data from external storage into RAM. The above process has been implemented by the SDK. The above process has been implemented by the SDK. From the perspective of the user, no matter which sleep mode is woken up from, the program will first run to a callback function in the user layer. The callback function may be called by RTC, GPIO, TIMER1 and so on.
• My application is to read a sensor value using I2C every 20ms and transmit the data to a connected phone. I would like the DA14531 to be in sleep for the rest of the time. Would it be possible to use Hibernation mode or deep sleep in this scenario?
• [ycai] The answer is yes. However, I suggest to use extend sleep mode, because another sleep mode requires an additional reboot process, which will also consume some power.
  When the sleep interval is long enough (such as 2s), the two external sleep modes are meaningful

Br, Yibin

I am having the same problem. I started with DA14531-DA14585-586_Service_Data_Beacon which sets
app_default_sleep_mode = ARCH_EXT_SLEEP_ON;
but the current between advertisements in the unmodified example is about 1.7mA. Changing to ARCH_SLEEP_OFF increases the current to 1.9mA.

This is with using the SmartBond Flash Programmer and cycling power to the Dev Kit before making the measurements.

I downloaded prox_reporter (both built from SDK source and the pre-built "Download online firmware" version from the SmartBond Flash Programmer) and the both the peak and average current measured as requested is 0.00000 mA. The graph is a straight line at the bottom (see attached pdf).

I verifed with BLE Scanner that the DLG-PROXR device was advertizing every 689ms.

I also tried the pre-built ble_app_barebone_531.out.bin from the online resources. The current looked more normal with an average of 0.16758 mA and peak of 3.181 mA.

Please let me know if I should move this discussion to a different thread. It appears to be the same problem, but I do not want to hijack the thread.

Jon

Hi Jon,

So w/o the SPI flash issue you are facing one problem of the "zero current consumption" with prox_reporter? Can you confirm the steps suggested by Yibin?

0. Unplug all jumpers on J19 on 531 dev-kit

1. Download the firmware of prox_reporter project in SDK into FLASH on 531 dev-kit

2. Unplug and reinsert the USB cable

3. Open SS toolbox -> select UART/SPI interface -> open power-profile tool

Br,

PW_Dialog

Hi tsgowtham,

Could you please take a look at the Sleep mode tutorial from our support website? Link is provided below.

http://lpccs-docs.dialog-semiconductor.com/DA14531_Sleep_Mode+/index.html

Thanks, PM_Dialog

Hi tsgowtham,

In the Sleep mode tutorial, the tables with extended sleep mode currents are for the DA14531. In your initial post, the DA14531 module is tagged. Please refer to the module’s datasheet and see Table 4: DC Characteristics.

You mentioned that the average current consumption is 0.02 mA. What is the advertising interval that you are using? Here, the device is advertising and goes into extended sleep mode between advertising intervals and it will automatically wakes up via the BLE timer.

If you follow that sleep mode tutorial, you will see that the after the advertising period, the chip will stop advertising and is going into permanent sleep mode (without BLE activity). How mush is the current consumption in permanent sleep mode?

Additionally, can you please indicate the project that you are using? If you could share it with me it would be helpful in order to run it in my side too.

Thanks, PM_Dialog

Hi tsgowtham,

The empty_peripheral_template does not stop advertising, so the device sleep between advertising or connection intervals. The prox_reporter is using advertising with time-out, so the system is going into sleep mode not only between advertising or connection intervals, bus once the advertising is stopped and it goes into permanent sleep mode. However, the prox_reporter is using the SPI flash, so to reduce the power consumption, you need to power it down and release it once the device wakes up.

Thanks, PM_Dialog

Hi tsgowtham,

Glad that you are able to reduce the power consumption and thanks for accepting my answer. Thanks for your feedback too!

Regards, PM_Dialog