• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Answers 1 answer
  • Subscribers 78 subscribers
  • Views 165 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: CCS Energy Trace Automatically Closing

Anthony Sanseverino
Prodigy 10 points
Part Number: ENERGYTRACE

Hello!

I am trying to utilize Energy Trace on CCS 10 and 11 with a MSP-432P410R and am experiencing issues with the Energy Trace window. Whenever I try to open the window outside of debugging, it automatically closes  right after opening. I tried to work around this by enabling "auto launch." However, I am trying to get a .csv copy of the data collection and the window automatically closes after debugging and I am unable to save the data. Does anyone have a solution, or any forum redirects for this? 

Thank you.

  • 0
    TI__Guru 56685 points

    Hello,

    EnergyTrace is only available in the Debug view of CCS. You can always switch to that view, even w/o debugging with the icons on the top right of the CCS Window. Alternatively, you can also just pause the debug session to collect data.

    For power numbers closer to application use cases, it is recommended to run the debugger in "Free Run" mode. 

  • 0 in reply to Jace H
    Prodigy 10 points

    Hi Jace, thank you for promptly responding to my initial reply and am sorry for the delay in responding/ thanking you for the help. Earlier when I would pause within debug mode it would display an error, however i had tried again and i was able to export the data. (not sure what was causing the initial error) However, the error was not due to being in CCS debug view. Even when I click debug view, and try to open EnergyTrace it still closes automatically. Using a workaround I was able to collect the data but am not sure why this issue is still occurring. Issue semi resolved. Thanks! 

**Attention** This is a public forum