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/LAUNCHXL2-TMS57012: LAUNCHXL2-TMS57012

Part Number: LAUNCHXL2-TMS57012
Other Parts Discussed in Thread: ENERGYTRACE, TMS570LS1224, TMDSEMU110-U, TM4C129ENCPDT, INA210

Tool/software: Code Composer Studio

Hello.

Good Day!

I've got a LaunchXL2-TMS57012 with XDS110 debug interface. When I start the EnergyTrace function within the CCS Studio 10.0, I always get the following error message:

"\ti\ccs1000\ccs\ccs_base\dvt_4.1.0.202001311011\AnalysisLibrary\DataProviders\EnergyTrace\EnergyTrace_MSP432_XDS110.ccxml is not compatible with the current target configuration C:\TI\Launchpad\Examples\PWM\targetConfigs\TMS570LS1224.ccx".

In the CCS menu "Windows->Preferences->Code Composer Studio->Advanced Tools->Energy Trace Technology" the default Device type MSP432/RF432/CC13xx/CC26xx couldn't be changed.

The menu is gray shaded. What's the problem? What has to be done that the EnergyTrace function is available?

Thanks and Regards,

Heinz 

  • Heinz,

    user6208246 said:
    I've got a LaunchXL2-TMS57012 with XDS110 debug interface.

    Do you have a standalone XDS110 (TMDSEMU110-U) plus the HDR accessory (TMDSEMU110-ETH)? The XDS110 Debug Probe built into the Hercules Launchpads do not usually feature the EnergyTrace functionality. 

    user6208246 said:
    What has to be done that the EnergyTrace function is available?

    Since the only EnergyTrace mode that can be used with Hercules devices is the standalone mode, it can be enabled outside of a Debug Session. 

    This becomes a bit cumbersome given this becomes a two step process, but it does not detract from the EnergyTrace functionality itself: flash the device, close the debug session and then start EnergyTrace from the Edit Perspective. 

    The reason why EnergyTrace cannot be enabled from inside a Debug session is because the tool queries the target to seek for the extra functionality of the device, thus failing when Hercules is used.

    (edit) I just filed the enhancement request EXT_EP-9918 to improve the handling of this scenario. 

    Hope this helps,

    Rafael

  • Rafael,

    Good Day!

    Thank You very much for your very fast response.

    I use the inboard XDS110 emulation via the TM4C129ENCPDT. In the schematics of the LaunchPADXL2-TMS57012 I saw a shunt resistor with OPamp in the core supply of the TMS570LS1224 MCU which is connect to the TM4C129ENCPDT. Therefore I think in principle it should be possible to get the value of the core current out of the board.

    Your proposal to launch the EnergyTrace function out of a debug session unfortunately doesn't workes. There still only a MSP432... is shown in the preference menu of the EnergyTrace program.

    Perhaps you have another Idee what I can try out?

    Thanks and Regards,

    Heinz

  • Heinz,

    user6208246 said:
    I use the inboard XDS110 emulation via the TM4C129ENCPDT. In the schematics of the LaunchPADXL2-TMS57012 I saw a shunt resistor with OPamp in the core supply of the TMS570LS1224 MCU which is connect to the TM4C129ENCPDT. Therefore I think in principle it should be possible to get the value of the core current out of the board.

    As I mentioned before, the XDS110 Debug Probe that comes with the launchpad does not have EnergyTrace support, thus the current/energy monitoring cannot be done directly from CCS.

    I am not entirely sure which OpAmp + shunt you are referring but, if it is U6, you would be able to measure the current proportional to the INA210 output voltage in the AD input 3 of the TMS570 using custom code. 

    Regards,

    Rafael 

  • Rafael,

    Thank You for your answer.

    You're right, I meant the U6 OpAmp INA210 output. But because it seems that the output of the INA210 is connected to U7 TM4C129ENCPDT AD input 3 and not to a TMS570 AD input I've no idea how to write code for this. Nevertheless, for the first step, I simple measure the output voltage of U6 directly and then calculate the supply current of the TMS570 out of the voltage. One last question, is it possible, and when yes, how, get access to the TM4C129ENCPDT AD converter input anyhow?

    Regards,

    Heinz

  • Hi,

    user6208246 said:
    But because it seems that the output of the INA210 is connected to U7 TM4C129ENCPDT AD input 3 and not to a TMS570 AD input

    Yes, you are right; I overlooked that it was connected to the TM4C129.

    In this case, there is no provision on the XDS110 support to read this pin. Sorry.

    Regards,

    Rafael

  • Hi,

    although there is no solution to my problem, thank you very much for your support and help!

    Regards,

    Heinz