DA14531- Power profile issue

Question

Hi sir, 
 i am working on DA14531, after flashing the code into DA14531 then i started checking for power profile using smart snippets toolbar v5.0.24 
 it detects the device and J-tag, but it won't show the power profile. 
 what can be the issue behind this problem?

how can solve this issue??

OV_Renesas · Accepted Answer

Hi Stanly, Thank you for the reply. Which is the SDK version you are trying to use? If you are using SDK v6.0.20 or v6.0.22, please make sure you do the following to integrate Git Repo examples: 1) Make sure you add the system_library_531.c on the sdk_arch folder: 2) You can do that by right-clicking on the sdk_arch folder: 
 3)Navigate on the SDK files on the following path ...\6.0.20.1338\sdk\platform\system_library\src\DA14531 PS: For different kind of issues, please create new threads. This way when a new user searches for an answer on the communities, they will find it easier. Best Regards, OV_Renesas

PM_Renesas · Answer

Hi Stanly, 
 
 Thanks for your inquiry. You will have to connect via UART to enable PowerProfiler functionalities. . 
 
 BR, 
 PM_Renesas

JH_Renesas · Answer

Hi Stanly, 
 The DA14531 SmartBond TINY USB Development Kit does not support power profile. 
 Please use Development Kit Pro, or you can measure the power consumption by following this tutorial: 
 UM-B-125 User Manual DA14531 USB Development Kit Hardware (renesas.com) chapter 5.18 
 BR, 
 JH_Renesas

OV_Renesas · Answer

Hi Stanly, Thank you for the reply. 
 stanly said: I have DA14531 as a peripheral device and it should keep on scanning for the central device 
 once the central device is found it should connect with it (one peripheral device for one central device) 
 This is not possible. The Peripheral devices can only Advertise. The Central devices can Scan for the Advertisement packets. The Central devices can send a connection request (CONNECT_IND packet) to the Peripheral devices. The Central device should scan, find your Peripheral device and initiate the connection. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Stanly, Thank you for the reply. Please refer on our Git Repo : 1) Central Example 2) Central with Security Example Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Stanly, Thank you for the reply. I tested your firmware with the DA14531MOD Daughterboard and the Development Kit Pro. I was not able to wake-up the DA14531 unless I used the HW Reset button (P0_0). I am not sure if that is supposed to be the expected behavior. I could see that you are advertising for 1 second and then go back into sleep mode without advertising. For the Battery Life Estimation, I would need you to provide me the necessary information in order to test this: It highly depends on the configuration you have set on your project. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Stanly, Thank you for the reply. Indeed I was able to wake up the device via P0_7. During advertising I get the following current consumption: During Sleep mode I get the following current consumption: Have you configured your device to perform non connectable Advertising? Have you considered using Deep Sleep when you do not want to advertise? I still do not have enough information regarding the Battery Lifetime Estimator. Please share the exact application code size, how often are you going to press the button to advertise etc. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Stanly, Thank you for the reply. For Deep Sleep, please refer on the prox_reporter example and on the following tutorials: 1) DA1453x & DA1458x Sleep Modes Tutorial &mdash; DA1453x & DA1458x Tutorial Sleep Modes (renesas.com) 2) 3. BLE Development Environment and First Application &mdash; DA14585/DA14531 SW Platform Reference Manual (renesas.com) You can follow the implementation shown on prox_reporter to enable Deep Sleep on ble_app_sleepmode example as well. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Stanly, Thank you for the reply. On your Options for Target settings please check C/C++ tab and make sure that Link-Time Optimization is enabled: Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Stanly, Thank you for the reply. Go again on Options for Target, on Utilities tab and select the Use External Tool for Flash Programming option: The J-Link debugger should be able to connect now. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Stanly, Thank you for the reply. From the screenshots you have shared, is that you are trying to debug the project directly from the BLE-SDK examples folder of the GitRepo. You should copy/paste the example you are interested in inside your SDK with the rest of the SDK examples included. Then use the python script included to fix the paths to your SDK. The rest of the settings seems OK to me. Keil is trying to locate the jlink_DA14531.ini which is part of the SDK folders and not from the GitRepo folder. This is why you cannot debug. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Stanly, Thank you for the reply. I tried to apply your configuration on the Battery Lifetime Estimator: You can test this on your side with SmartSnippets Toolbox as well. For the Battery Lifetime Estimator you will not need to use any of the Dev Kits. I only put 5% of Lifetime spent in Advertising since you are going to advertise for a few seconds 20 times a day. Best Regards, OV_Renesas

OV_Renesas · Answer

Hi Stanly, Thank you for the reply. Please refer on the mp4 video below: I used Development Kit Pro with the DA14531MOD Daughterboard and I used P0_7 to wake-up the device. The final current consumption will depend on how many times the DA14531 will wake-up to advertise. Best Regards, OV_Renesas