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.

ENERGYTRACE: CC2642R EnergyTrace problems

Other Parts Discussed in Thread: CC2642R, LAUNCHXL-CC26X2R1


I encountered a lot of problems using EnergyTrace in CCS ( with a XDS110 debugging a CC2642R.

1) When using "probe supplied power", I start a debug session, then open EnergyTrace, then run the code.

EnergyTrace gets stuck on the first value of the timer and no value changes nor trace appear on the graphs.

Target configuration used :

EnergyTrace :

2) When using "Target supplied power", I start a debug session, then open EnergyTrace, then run the code.

The "EnergyTrace Technology" tab displays "Stream closed"

Target configuration :

EnergyTrace :

3) When stopping a debug session, the "EnergyTrace Technology" tab closes, and the "Energy" and "Current" graph tabs stay.

4) I often get the "Failed to create the part's controls" error, which requires to restart CCS.

Please help me use EnergyTrace.


Victor Tolosana

  • Hello Victor,

    Are you aware of SWRA478 and the EnergyTrace Overview page?  I do not recommend altering the .ccxml target configuration file for this purpose.  You can view certain settings from Window -> Preferences -> Code Composer Studio -> Advanced Tools -> EnergyTrace Technology but once again nothing should need to be changed.  Below are the results of running a default timerled example on a LAUNCHXL-CC26X2R1:

    If you are experiencing any difficulties with Code Composer Studio performance then you can make a specific post to the relevant forum.


  • Hello Ryan, 

    I modify the .ccxml file because my goal is to be able to use EnergyTrace with probe supplied power and with target supplied power, depending on whether the target has a battery or not.

    I also need to use SWO overlaid on JTAG TDO.

    What I want to do is to be able to measure the current consumed by the target (Rload). Battery can be present or not (switch S1). If battery is present, use target supplied power, if battery is not present, use probe supplied power. It would be better if it can be automatic (maybe with a script ?), but it is ok if we have to change the ccxml to adjust for battery/no battery.

    The schematic :

    I continued experiments, and the problem I have is that in order for EnergyTrace to work with probe supplied power, TGTVDD(SENSE) should not be connected. It prevents from using the probe supplied power mode if the battery is in.

    Either I didn't find it or XDS110 documentation is very incomplete, especially about TGTSUPPLYIN and TGTVDD(SENSE). Can you explain what does TGTVDD(SENSE) do please (in both probe and target supplied power modes) ?

    Thank you.

  • Here is the XDS110 Debug Probe User's Guide and Product Page.

    From the LaunchPad User's Guide: "To use EnergyTrace the Power Jumper must be in the XDS110 Power position and the 3V3 jumper on the XDS header must be mounted to provide current to the target. The other jumpers on the XDS header are optional. EnergyTrace does only support 3.3 V supply voltage. Chapter 7 in the Measuring Current Consumption Application Report describes how to run EnergyTrace from CCS."

    In summary, you may need to consider a different power consumption monitoring solution.