CC2652R: Implement BLE sleep wakeup strategy in cc2652r launchpad simple peripheral example project.

Also when we are using simple peripheral example code without any modification we can achieve up to 386 micro amps.

How can we reduce the current consumption for above configuration.

Hi chaitali,

Please review SWRA478 and the POWER_SAVINGS definition as mentioned in the BLE5-Stack User's Guide.  It is possible that the XDS110 debugger on the LAUNCHXL-CC26X2R1 has not been fully removed during power consumption measurements.

Regards,
Ryan

The XDS110 debugger on the LAUNCHXL-CC26X2R1 has been fully removed during power consumption measurements.

how we can implement standby mode in ble cc2652R side.

Depending on your SDK and BLE project settings, PowerCC26XX_standbyPolicy should already be enabled in the simple_peripheral SysConfig -> TI Drivers -> Power module.  This means that standby will be entered whenever the device is Idle (i.e. no stack or application activity).  If you are measuring 386 uA then then is less than active or idle power consumption, meaning your device is going into standby for some time (see Section 8.5 of the Datasheet).  You could disable the two-button menu UART display for greater current savings.

Regards,
Ryan

after disabling uart display also we are getting 1.6mA current consumption. Actually I have modified the simple peripheral example code as per my application need I have changed the ble UUID to 128 bit  and i have added one UART and one timer of 100ms.During ble sleep condition the timer and uart are not needed they are required in application after ble wakeup so is there any way we can reduce ble sleep current less than 1mA.

Hello,

We are able to achieve sleep current up to 1mA in our simple peripheral modified code using the following API's in simple_peripheral.c file,

  Power_releaseConstraint(PowerCC26XX_ENTERING_STANDBY);
  Power_releaseConstraint(PowerCC26XX_ENTERING_SHUTDOWN);

Can you suggest what is the sequence we have to follow to wakeup from the ble standby mode.

Which SIMPLELINK-CC13XX-CC26XX-SDK version are you using?  What equipment are you using to measure current?  Pleaser validate your hardware setup by recording the power measurement of default gpiostandby and simple_peripheral examples.  Here also is the TI Drivers Power Managment User's Guide.

Regards,
Ryan

We are using simplelink_cc13x2_26x2_sdk_5_10_00_48 sdk. For measuring current we are using power analyzer.

I have tried to find the gpiostandby code in my sdk but it is not available there.

Currently we have acheived the sleep current upto 1mA using the API Power_releaseConstraint(PowerCC26XX_ENTERING_STANDBY);
  Power_releaseConstraint(PowerCC26XX_ENTERING_SHUTDOWN);

but after ble wakeup we are facing issue with uart driver working. so is there any specific sequence we have to follow after using these power API to wakeup ble and get the uart working properly.

The pinstandby code is an option for your SDK version.  Have you removed all XDS110 and LED jumpers along with moving the jumper for "Extern Pwr"?

Additional API should not be necessary to enter standby mode for the BLE simple_peripheral example.  There could be an issue with the custom code if measurements are improved with the default examples.

Regards,
Ryan

We have removed all the jumpers and checked but still same issue we are facing we are not able to achieve sleep current less than 1mA.

Can you please go through the shared modified simple peripheral example code and suggest how we can reduce sleep current consumption.

https://sparkmindaashokmindagroup-my.sharepoint.com/:f:/g/personal/chaitali_gosavi_mindacorporation_com/EjiFcZc7DcZAsF1mp-uE-PUB20ArTHs0TWMYLtSXzWFM7Q?e=3Mzryk

chaitali gosavi said:

Currently we have acheived the sleep current upto 1mA using the API Power_releaseConstraint(PowerCC26XX_ENTERING_STANDBY);
  Power_releaseConstraint(PowerCC26XX_ENTERING_SHUTDOWN);

Try use the original simple peripheral without modifications. Remove any code that opens UART. Remove jumpers and power the launchpad from battery.

Remove the menu codes, button codes, led on code. It's a lot of work.

The device will automatically go to standby mode when there is no event.

-kel

I do not think it would be an efficient use of time to review your custom code.  As kel stated, you should first verify low-power operation using the default simple_peripheral example.  Then remove excess on-board peripherals such as UART and GPIOs for LEDs/pushbuttons.  Once the power is measured at a sufficient level, incrementally add in your code and further test to determine if any specific changes create a larger power consumption.  Then you can further debug and post code excerpts if necessary.

Regards,
Ryan