To reduce power consumption

Question

Hey all! 
 
 I have been working on DA14531 micro - controller, using keil uVision application software to develop a firmware and Dialog Smartbond Flash Programmer application software to load the same. 
 Details of the hardware/ software applications: 1. DA14531: Micro - controller that is being used. 2. Keil uVision5: Application to develop the firmware and generate a hex file to load the same. 3. Dialog Smartbond Flash Programmer v1.0.8: Application to load the firmware. 4. J - link (Segger JTAG): The interface used to load the firmware. 5. SDK_6.0.18: SDK that has basic in-built examples [the main SDK]. 
 The aim is to achieve the working of DA14531 as a beacon with necessary application. 
 The above involves the use of extended sleep mode as well where the advertising interval is set to 1.3sec so the device advertises, goes to sleep and wakes up to perform the same on loop, the current consumption when checked on power profiler application is observed to be as follows: 
 1. Overall average power: 19.57 uA 
 2. Peak power: 3.27 mA 
 3. Average power when in extended sleep mode: 11.91 uA 
 
 PFA a screenshot of the same.

Can the current consumed during sleep time be reduced any further? 
 
 Any help shall be appreciated. TIA! 
 
 Warm regards, 
 AXISCADES.

OV_Renesas · Answer

Hi AXISCADES, Thank you for posting your question online. 
 CADES said: The aim is to achieve the working of DA14531 as a beacon with necessary application. 
 The above involves the use of extended sleep mode as well where the advertising interval is set to 1.3sec so the device advertises, goes to sleep and wakes up to perform the same on loop, 
 I used our ibeacon project, and I only changed the Advertising intervals equal to 1.3sec. After that I could see on the Power Profiler: As you can see the Avg Current is 22uA. 
 CADES said: Can the current consumed during sleep time be reduced any further? 
 According to the screenshot you shared, I can see that the DA14531 is going successfully into Extended Sleep Mode between the advertising intervals. You could possibly drop the current consumption a bit more if you do not retain the RAM blocks while on Extended Sleep Mode. Please refer on the BLE Sleep Modes Tutoria l: You can check the RAM retained blocks on the da1458x_config_advanced.h file: /****************************************************************************************************************/
/* The Keil scatter file may be provided by the user. If the user provides his own scatter file, the system has */
/* to be aware which RAM blocks has to retain. The 4th RAM block is always retained, since it contains the ROM */
/* data. */
/* - CFG_RETAIN_RAM_1_BLOCK: if defined, the 1st RAM block must be retained. */
/* - CFG_RETAIN_RAM_2_BLOCK: if defined, the 2nd RAM block must be retained. */
/* - CFG_RETAIN_RAM_3_BLOCK: if defined, the 3rd RAM block must be retained. */
/* */
/* If the CFG_CUSTOM_SCATTER_FILE flag is undefined, the system knows which blocks to retain based on the */
/* default SDK scatter file. */
/****************************************************************************************************************/
#define CFG_RETAIN_RAM_1_BLOCK
#define CFG_RETAIN_RAM_2_BLOCK
#define CFG_RETAIN_RAM_3_BLOCK Generally, the Avg Current of 19.57uA for a beacon project is an expected value. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi AXISCADES, Thank you for the reply. Could you please clarify if you are using the DA14531 SoC or the DA14531MOD? Could you also please clarify if you are testing this on a custom board or one of our Dev Kits? The current consumption measurements I shared on my previous answer regarding the ibeacon project are INCORRECT. The reason is that I had not calibrated the Power Profiler. I worked on Dev Kit Pro and I tested it with both the DA14531MOD DB and the DA14531 SoC DB. I used SDK v6.0.18 and the ibeacon project from the GitRepo. Before measuring the current consumption, I followed the Calibration procedure as mentioned on the SmartSnippets Toolbox User Manual", on section 13.10 Calibration Procedure. In order to open the SmartSnippets Toolbox User Manual, go in the top right corner, on the Help tab and select User Guide (html) After that the measurements I got for TX power: 0dBm, Advertising interval: 1.3 seconds And according to the site you shared: 
 CADES said: Also, another observation made is to use the function spi_flash_power_down() to reduce the current consumption as discussed below: 
 community.renesas.com/.../current-consumption-due-to-spi-flash-on-da14531-module 
 Yet this resulted in failure, is there anything related to the above to be done? 
 What do you mean it resulted in failure? As you can see on the thread you shared, it highly depends on the SPI Flash you have selected for your board. If the SPI Flash fails to go into sleep, that will add up from 100 up to 400uA depending the SPI Flash. So I do not think that with a current consumption of 19uA the SPI Flash has failed to go into Sleep mode. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Cades, Thank you for the reply. Is there a reason you are working with SDK v6.0.16 and with the latest SDK v6.0.18? The Schematic you shared is OK, just make sure that you have the debugger de-attached when trying to measure the Avg Current Consumption so you can make sure that you have accurate measurements. 
 CADES said: But the same setup when used to measure current with our device application involving extended sleep mode resulted in consuming a s leep current of 11uA. 
 In SDK v6.0.18 with the DA14531MOD and the ibeacon project from the GitRepo (with TX power set at 0dBm and Advertising Interval at 1.3 seconds) I get 5.6uA Avg. Current Consumption. 
 CADES said: The datasheet of the DA14531MOD claims the current of 1.6uA to be consumed when in extended sleep mode , is there a way to achieve this? 
 The DA14531MOD Datasheet, claims a current of 1.8uA. In order to achieve that, I stopped advertising on all 3 available Channels and I selected only one. On user_config.h file: /*
 ****************************************************************************************
 *
 * Advertising configuration
 *
 ****************************************************************************************
 */
static const struct advertise_configuration user_adv_conf = {

 .addr_src = APP_CFG_ADDR_SRC(USER_CFG_ADDRESS_MODE),

 /// Minimum interval for advertising - set in user_app.c
 .intv_min = MS_TO_BLESLOTS(0), 

 /// Maximum interval for advertising - set in user_app.c
 .intv_max = MS_TO_BLESLOTS(0), 

 /**
 * Advertising channels map:
 * - ADV_CHNL_37_EN: Advertising channel map for channel 37.
 * - ADV_CHNL_38_EN: Advertising channel map for channel 38.
 * - ADV_CHNL_39_EN: Advertising channel map for channel 39.
 * - ADV_ALL_CHNLS_EN: Advertising channel map for channel 37, 38 and 39.
 */
 .channel_map = ADV_CHNL_38_EN, And on the user_app.c file I set the Advertising Interval into 5seconds. Then with the Power Profiler (calibrated) I was able to see this Avg Power Consumption: And I was able to see the DA14531MOD advertising with the SmartBond App on my SmartPhone (Android v13). Then I changed the Advertising Interval into 1.3 seconds and kept only the Advertising Channel 37 active. On the Power Profiler I could see Avg Power Consumption of 3.9uA My Central (SmartBond App) was able to scan for the DA14531MOD while advertising. In order to achieve the 1.8uA Current Consumption you are going to need to increase the Advertising Interval (how much, it depends on your central configuration, scan interval, scan window etc.) and to try advertising only in one Advertising Channel and not on all 3 simultaneously. Is there a specific reason you are working with the ble_app_peripheral example and not with the ibeacon project? Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Cades, Thank you for the reply. 
 CADES said: Average current has been reduced to 15 uA (TX power: 0dBm, Advertising interval: 1.3 seconds) but the sleep current is still 11.91uA (Extended sleep mode). 
 It is weird that even after you changed the Advertising Channel map the sleep current remained the same. You should be able to see a difference in the current consumption. 
 CADES said: The reason for not using the iBeacon project is I couldn't link the SDKs. I had raised a query for the same and PFA the forum link: 
 https://community.renesas.com/wireles-connectivity/f/bluetooth-low-energy/31461/unable-to-link-ble_sdk6_examples-to-the-main-sdk 
 
 Is there a way I can solve either of the issues? 
 As mentioned on the mentioned ticket: The SDK v6.0.16 uses ARM Compiler v5 and the SDK v6.0.18 ARM Compiler v6. All the GItRepo examples, and the python script, has been ported into SDK v6.0.18. beacon_v6.0.16.zip Please find the attached beacon_v6.0.16.zip file. It contains the old ibeacon example for SDK v6.0.16 with ARM Compiler v5. I have also attached the old python script to fix your paths. 1) Unzip the file and place the beacon folder inside the ble_examples folder (inside the SDK). 2) Open the ibeacon folder: 3) Type 'cmd' on the Windows path bar and press enter: 4) On CMD type the following: python dlg_make_keil5_env_v2.000.py -sdkpath clean
 When the script has finished, you should see this kind of log: 5) Then type: python dlg_make_keil5_env_v2.000.py -sdkpath "INSERT_YOURPATH_TO_THE_SDK" When the script has finished, you should see this kind of log: 6) Open the ibeacon project in Keil IDE and you should be able to compile the project with ARM Compiler v5. The other approach would be to migrate into SDK v6.0.18 and then use the ibeacon project from the GitRepo. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Cades, Thank you for the reply. 
 CADES said: Now that I tried linking the above given iBeacon project with the SDK v6.0.16, it worked. I could compile the same without any errors. 
 Glad you were able to port the ibeacon project in your SDK. 
 CADES said: I want the extended sleep mode to be retained and the device needs to wakeup by a GPIO to just give a blink every time the GPIO goes high, other than it's regular wake up for advertising. As the wkupct_quadec.c file wasn't used, I did add the same under the sdk_driver folder (as in the ble_peripheral example I was using prior) via the keil application and the wakeup functionality doesn't seem to work when called the same. 
 I initially had used interrupts for the same but because the device is set to extended sleep mode, I had to use GPIO wakeup. 
 Can you kindly suggest a way to solve the same? 
 Please find the attached beacon_v6.0.16_wkcpt.zip file, it contains the ibeacon project for SDK v6.0.16. I have implemented an app_easy_timer that starts inside the user_app_adv_start function and after 20seconds it stops advertising and shuts down the BLE core. Then I configure the P0_11 as a Button and I initialize the Wake-up Controller. I have also configured P0_9 as my LED pin because it is already connected into a LED on the DA14531MOD Daughterboard board. When I press the Button (P0_11) the DA14531 wakes up the BLE core and restarts advertising. The LED turns on when the Interrupt is triggered and turned off just before we start advertising (less than 1 second). This ends up on a loop, 20 seconds advertising, then BLE core is off, push the Button to wake-up the BLE core and restart advertising for 20 seconds. beacon_v6.0.16_wkcpt.zip Note: You will need to use the python script to fix the paths of the SDK. Please share any feedback! 
 CADES said: Also, where can I find references for the above given iBeacon project? 
 What exactly are you looking for? The ibeacon project is part of the SDK6 so the same APIs and functionalities are available. Please refer on the UM-B-119 . It has all the necessary documentation for the SDK6. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Cades,

Thank you for the reply.
Glad you were able to get the current consumption you were looking for.

Regarding your scenario:
I am a bit confused on what the exact scenario is.
From my understanding, you want to do the following:
1)Non connectable advertising, with 1.3sec advertising interval
2) When the user presses a button, the device stops advertising and a LED blinks momentarily (do you want a specific time for the LED to be turned on?).
3) The DA14531 will stay in Extended Sleep mode (with BLE core OFF) until user presses the same button again.
4) The DA14531 should wake-up and restart advertising (with 1.3 advertising interval) and the LED should be turned on momentarily.
Have I misunderstood something?

P.S.
If you found any answer helpful, you can verify them. That will help the rest of the community members that face the same issue.

Best Regards,
OV_Renesas

OV_Renesas · Answer

Hi Cades, Thank you for the reply. 
 CADES said: 1. As the device is powered on, it shall advertise (n on connectable) with an interval of 1.3second with extended sleep mode . 
 2. The above should continuously be taking place. 
 3. When the user clicks the button, the led should just blink once (just an on and go off, blink once; I need not want it to be turned on for a while). 
 4. While the above takes place, it should not hinder/ alter the regular functionality ie, the advertisement in an interval of 1.3second with the extended sleep mode . 
 5. The device should stop advertisement only when the power is not given . 
 I modified the previously shared project in order to fit inside these requirements. Please find attached the beacon_v6.0.16_wkcpt_v2.zip file which contains the project. I compiled the project, and I downloaded the firmware into the SPI Flash. On the Power Profiler I could see: The spikes are from the LED being turned on. For the LED I have added an app_easy_timer that will turn off the LED after 500ms If you want to change the time that the LED will be turned ON, you can change that: beacon_v6.0.16_wkcpt_v2.zip As mentioned before, I am working with DA14531MOD Daughterboard, SDK v6.0.16 and Dev Kit Pro. Whenever I press SW2 (P0_11) I can see the LED (P0_9) on the DA14531MOD Daughterboard turn ON and after 500ms it turns OFF. Best Regards, OV_Renesas