• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 332 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LAUNCHXL-CC26X2R1: Unknown power spikes in Idle thread

Eyal Rosenthal
Prodigy 140 points

Part Number: LAUNCHXL-CC26X2R1
Other Parts Discussed in Thread: ENERGYTRACE

Hello,

I'm testing multi_role example using CC13x2_26x2 SDK 5.10.00.48. I wanted to check the device's idle current consumption using EnergyTrace. In the Main() I've commented out all tasks:

So that the device will stay in Idle mode. However, when testing with EnergyTrace (and following the guide SWRA478D - Measuring CC13xx and CC26xx current consumption) I get power spikes about every 800ms:

This is obviously the RTOS scheduler waking up to do something but I don't know what or how to control it. I can't imagine this is simply to advance the system clock since the current jumps to about 10mA.

I've set up the Power module with syscfg to use PowerCC26XX_standbyPolicy and disabled RCOSC calibration. I'd appreciate if you could tell what causes this wake up, and if there's a way to disable or control the time interval in which it is performed.

Eyal

  • +1
    TI__Mastermind 44330 points

    Hi Eyal,

    This seems to be the VDDR recharge that occurs when the device is in standby. This behavior is discussed in the SWRA478D app note in chapter 2 Standby. I have pinged the HW team for their thoughts on this.

    Best Regards,

    Jan

  • 0 in reply to Jan
    Prodigy 140 points

    Hi,

    Yes it was the VDDR recharge. My confusion came because our power consumption profiler(not EnergyTrace) showed an idle current substantially higher than the data sheet, which made me think that maybe something other than the VDDR recharge is causing this current spike and my power policy has an issue.

    It seems that our current profiler had a problem that corrupted our measurement, but it has been fixed and the device is working as intended now.

    Thanks