• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 53 subscribers
  • Views 1750 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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 stand-alone-mode doesn't launch EnergyTrace window in my CCS Version: 10.0.0.00010

YiKai Chen
Guru 735685 points
Part Number: CCSTUDIO
Other Parts Discussed in Thread: ENERGYTRACE

Tool/software: Code Composer Studio

When I test EnergyTrace stand-alone-mode in my CCS  Version: 10.0.0.00010, CCS doesn't launch EnergyTrace window after I click the EnergyTrace Ico on Tool bar. How can I know what is going wrong in my CCS?

  • 0
    TI__Guru**** 171004 points

    Yikai,

    This used to be a bug in one of the earlier releases of CCS, but I can't reproduce this in CCSv10.0.0. 

    That said, I wonder if two things may be going on:

    - The autodetect probe is not working properly. You could try to change the default probe for EnergyTrace - check the section Settings of the EnergyTrace page at:

    https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/emu_energytrace.html

    - Some issue is lingering in your workspace. In this case, you can simply try to see if the function works on a different workspace or try to issue CCS with the -clean option (something mentioned in section 9.4 of the CCS User's Guide). 

    https://software-dl.ti.com/ccs/esd/documents/users_guide/index.html

    - A temporary file may be getting in the way to launch this. Locate the directory %HOMEPATH%\.TI-trace and erase its contents (or rename the directory). 

    Hope this helps,

    Rafael

  • 0 in reply to desouza
    Guru 735685 points

    I already try to change the default probe for EnergyTrace - but it doesn't fix my problem. Using "-clean" cannot fix the issue. I also try to delete everything under directory %HOMEPATH%\.TI-trace but the problem is still there. Do you have other suggestions?

  • 0 in reply to YiKai Chen
    TI__Guru**** 171004 points

    Yikai,

    At this point I can't pinpoint a root cause. The last attempts would be:

    - Delete the CCS temporary files at %APPDATA%\Texas Instruments\CCS. This is a long shot, but perhaps it may help.

    - Update the TI Emulators component (a new version was released this afternoon). This may help fixing a component or two that may have been corrupted. 

    - If nothing works well, I am afraid the last attempt would be to reinstall CCS altogether. 

    Regards,

    Rafael

  • 0 in reply to desouza
    Guru 735685 points

    I tried delete the CCS temporary files at %APPDATA%\Texas Instruments\CCS and reinstall CCS10. Both doesn't work.... Too bad...Is there still anything I can do to fix this? Or can you tell me when I can get the CCS log for you to clarify this issue?

  • 0 in reply to YiKai Chen
    Guru 735685 points

    After I reinstall CCS 10 and update everything, it finally comes back. Cheers!

  • 0 in reply to YiKai Chen
    TI__Guru**** 171004 points

    Yikai,

    Thank you for reporting back your findings. It is surely annoying that the tool was so broken that it required a reinstall, but if one of its .jar files got corrupted, I can see this happening. 

    Unfortunately the EnergyTrace does not produce any debugging log under the hood - the Debug Server is not launched and therefore its associated log is not created. One slim chance of capturing something was the workspace log (under the subdirectory .metadata), but even still I suspect the EnergyTrace would not contribute to it. 

    At this point I can only monitor the traffic here to track similar scenarios.

    I apologize for the inconvenience,

    Rafael

  • 0 in reply to desouza
    Guru 735685 points

    Anyway, Thanks a lot for your help and do hope you can find a way to avoid this issue on later CCS release.