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-CC1352R1: gpiostandby example and EnergyTrace

Part Number: LAUNCHXL-CC1352R1
Other Parts Discussed in Thread: ENERGYTRACE, , CC1352R, SYSCONFIG


I'm measuring the current consumption to test the SDK power policy.

First I use command line stune for capturing EnergyTrace data, then I merge all CSV files and I plot current vs time.

I've tested current consumption using gpiostandby example with a LAUNCHXL-CC1352R1. I've removed all jumpers on the LaunchPad between the XDS debugger and the device except for the XDS110 Power, the 3V3 and RXD jumpers. I've removed LED jumpers too.

I got this:

The device woke up every 5s and took around 10mA, then it went again to stand by mode. But in the capturing data, what are other 10.5mA peaks? I don't understand, my device doesn't do anything.

Thanks in advance.


  • Hi Andrés

    What you observe here is the VDDR Recharge pulse. Standby mode consists of a recharge period used to charge up the VDDR capacitor and the period between recharging.

    See for more details.


  • Hi Siri.

    OK perfect, now I understand those peaks.

    I've flashed the same example in a custom board with a CC1352R without any modification. The device doesn't go to standby mode.

     I need to check the constraints of power policy? How can I check it? with Power_getConstraintMask() ?


  • My 32-kHz crystal oscillator is working correctly:

    I've used to check it this:


  • If you are using the unmodified gpiostandby example from the SDK there is no need to do any changes to the standby policy (you have already confirmed that it works on the LP)

    If the exact same code is not working on your custom HW, I will assume that is because your custom HW is not identical to the LP.

    Without knowing how your HW differs, it is hard to tell what the problem is.

    I assume that you are not running the application via the debugger when measuring current (as the debugger prevents the device from entering Standby.

    Are your application running as it is supposed to when it comes to functionality (only the current consumption is the problem?)

    Does it not enter Standby at all, or does it enter standby (you see the recharge pulses), but the standby current is too high?

    Have you done any modifications at all to the default example?


  • Hi Siri,

    My custom HW has a sensor Hall, an eprint display, a ambient light sensor and time-to-digital converter. I've used the SDK sensor example like reference and it works perfectly with all peripherals.
    Then I've wanted test the current consumption of my custom HW, so I've started with the gpiostandby example. I haven't done any modifications at all to the default example. (the same that i've tested on the LP).
    The device doesn't enter Standby at all like we can see in the image on previous post. Those peaks are when the device wakes up (every 5s).


  • Before calling BIOS_start() in main, I call Power_getConstraintMask and I get 4

  • The power driver will put a constraint on standby until the system is running on the selected LF clock.

    This takes some time, so if you check the constrainMask right after you call Board_init();, it will return 4

    I did the following test where I checked the contrainMask in the mainThread: 

    Running the code without any breakspoints would lead me to enter the if statement starting at line 64

    If I set a breakpoint at for example line 55, and then started again, the code would run enter the while loop at line 72.

    Please try to do the same exercise. 

    To check if your problems are related to your 32 kHz crystal, you could try to select LF RCOSC as the LF Clock source in sysConfig instead. This will give us an indications as to where the problem can be.