How to view the raw data of power and energy graphs of energy trace module for msp430fr5969?..how to view the .profxml file?
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.
How to view the raw data of power and energy graphs of energy trace module for msp430fr5969?..how to view the .profxml file?
Krishna,
The RTS (Run Time System Library) source code is part of your CCS installation. Please look in:
C:\ti\ccsv6\tools\compiler\msp430_4.3.x\lib
- rtssrc.zip
RTS_4_3_x_Manifest.pdf
Regards,
David
David,
I would like to the power numbers of my CPU components like ADC when my code is running in free run mode. Energy trace ++ runs in debug mode and gives me the percentages of energy consumed of my components .Can I use the power numbers of my code in free run mode and use the percentages of the components in debug mode to get the power consumed of individual components.
In summary my question is how to correlate between the power data shown by energy trace++ and energy trace in debug and power modes respectively.
Regards,
Krishna
Krishna Balaji said:In summary my question is how to correlate between the power data shown by energy trace++ and energy trace in debug and power modes respectively.
AFAIK, EnergyTrace gives you the power consumed by your system.
EnergyTrace+ gives you a timeline with the information which component was active at a given time.
However, you won’t get the information how much energy any component uses. You may calculate it when you have two states that differ only in one component being active or not, and all other components taking exactly the same power. Then the difference in energy consumed is the consumption of this component during its active period. However, these are too many prerequisites to make an automatic analysis meaningful.
Also, debug mode may change the timing compared to free run mode. So it is likely misleading to correlate data from two different runs.