This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2642R: The problem of high sleep current

Part Number: CC2642R
Other Parts Discussed in Thread: ENERGYTRACE

     I have encountered a problem where when CC2642R is in sleep mode, its power consumption is much higher than described in the chip manual. The current is about 100 μA. 

The system clock I set is 48MHz and my power configuration is as follows:

extern void PowerCC26XX_standbyPolicy(void);
extern bool PowerCC26XX_calibrate(unsigned int);

const PowerCC26X2_Config PowerCC26X2_config = {
.enablePolicy = true,
.policyInitFxn = NULL,
.policyFxn = PowerCC26XX_standbyPolicy,
.calibrateFxn = PowerCC26XX_calibrate,
.calibrateRCOSC_LF = true,
.calibrateRCOSC_HF = true,
.enableTCXOFxn = NULL

Besides, I added POWER_ SAVING, the predefined macro. Is there anything worth noting in reducing sleep power consumption? Any suggestions are very welcome.

  • Hi,

    Which example are you using? (example name, SDK version, CCS version)


  • Sorry for the delayed reply. simplelink_cc13x2_26x2_sdk_4_20_01_04\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\simple_peripheral, CCS 12.4.0. In addition, I added some application services to the demo and controlled its sleep wake-up through a pin.

  • simplelink_cc13x2_26x2_sdk_4_20_01_04\examples\rtos\CC26X2R1_LAUNCHXL\ble5stack\simple_peripheral

    Thanks for confirming. I will notify the BLE team.

    Can you try with a newer SDK?
    The most recent version is, and there have been many improvements compared to the 4.20 SDK.


  • Thanks for reply. Now I am working with simplelink_cc13xx_cc26xx_sdk_7_10_01_24. There are still the same issues. I think this version of the SDK should have very little difference from the latest SDK?

     I used UART serial communication, but it was closed when going to sleep. In addition, I have configured a pin with both-edges interrupts to control wake-up. During sleep, the broadcast period is 500ms. Will these matter?

  • Hello Lishuang,

    Thanks for the information. To further assist you, could you please help me with the following questions:

    1. How are you measuring the power consumption (power analyzer, energytrace, etc)?
    2. Between what events are you measuring the standby current? If you have a "current draw vs time" graph showing where are you measuring this, it can be helpful.
    3. You mean that the only thing that is happening during "sleep" is broadcasting (with a 500 ms advertising interval)? Are you measuring the power consumption between advertisement events?
    4. What peripherals (other than UART and the interrupt pin) are you using?
    5. Are you running the power measurements under debug mode?



  • Thank you very much for your attention.

    I measured the current again using the measurement method suggested by TI and found that the broadcast period was not 500ms.

    After checking simple_ peripheral.syscfg, it was found that the configuration of Primary PHY Interval Maximum (ms) was set to a value below 500ms, which may have caused the broadcast interval to be unable to be changed to 500ms. After modifying the value to 500ms, the static current decreased to an ideal value. Your reply has been very helpful to me, thank you!