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.

CCS/CCSTUDIO: EnergyTrace: How to Synchronise Current Graph with Reference

Part Number: CCSTUDIO
Other Parts Discussed in Thread: ENERGYTRACE, TMDSEMU110-U

Tool/software: Code Composer Studio

I'm using EnergyTrace to optimise the pwoer consumption.

I performed a first measure I saved earlier and I'm using it as reference.

I've modified the code and I'm running a new measure.

The first pane provides comparison between current and reference measures.

The second pane displays a graph with current in green and reference in yellow. How can I synchronise both series to compare the peaks of power consumption?

Reference starts at 8 s while current starts later on at 50 s. I would like to have both series at start one on top of the other, by moving either reference by +42 s or current by -42 s.

Thank you!

  • Olivier,

    Unfortunately there is no way to change the reference directly on the EnergyTrace GUI - you will have to manually change it on the data to properly display it.

    The data can be saved also in CSV format for easier post-processing.

    That said, I recall there were some discussions to improve the display features of EnergyTrace view - perhaps have them closer to what the Single Time Graph has. I will try to follow up and see if there is any progress in this regard. This may not happen until the next major version of CCS, though.

    I apologize for the inconvenience,
    Rafael
  • Using Excel is doable, but rather slow as CSV files are very large.

    One possible solution would consist on implementing a very basic trigger, either resetting the board at the start of the record or flashing a LED to show a surge in power consumption.

    On the example below, I combined two different EnergyTrace CSV files into an Excel file. The result is, RTOS for the MSP432 MCU saves 3 mA.

  • Hi,

    By setting the trigger to "custom" you can frame the data capture on your system to known values. However, this works asynchronously from the main processor - i.e., it is completely dictated by the host PC and its somewhat imprecise data timekeeping.

    Would that help get closer to what you need?

    Regards,

    Rafael 

  • Thanks, I'll give a try.
  • Olivier,

    Did this work well for your purposes?

    Regards,
    Rafael
  • Yes, I managed to get the traces synchronised by using a LED as trigger. 

    Toggling a LED on then off for 10 ms starts the recording, as a LED requires 41 mW.

    Time difference is minimal and allows good comparison. The LED are toggled every 500 ms.

    I posted more details on the section Setting a Trigger for Better Synchronisation at Ultra-Low Power with EnergyTrace.

    Thank you for your help in solving this question!

  • The Auxiliary Breakout Board of the XDS110 JTAG Debug Probe (TMDSEMU110-U) features 4 GPIOs, 2 inputs and 2 outputs.

    As per the XDS110 Debug Probe User's Guide (SPRUI94),

    How to use the XDS110 GPIO pins:

    The XDS110 includes 4 GPIO pins on the AUX connector that can be controlled by the user. dbgjtag includes a command to configure, write, and read these GPIO pins:

    dbgjtag -f @xds110 -Y gpiopins, config=number, write=number, read=boolean, mask=number

    The GPIO pins are accessed by reading and writing the lower four bits of the number value. GPIO 3 and GPIO 2 are inputs into the XDS110. GPIO 1 and GPIO 0 are outputs from the XDS110. GPIO 1 and GPIO 0 are initially configured as inputs (hiZ). The user must configure these as outputs to enable these pins.

     Wouldn't be nice to use one of those GPIO to trigger the start of EnergyTrace?

  • Olivier,

    Although interesting, this feature is not yet available. Sorry.

    I submitted the enhancement request DBGTRC-4276. In a few hours you can check its status in the link SDOWP in my signature below.

    Regards,
    Rafael

    P.S. to avoid your replied being missed, please open a new thread instead of replying to an older one.