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/SIMPLELINK-CC13X2-26X2-SDK: EnergyTrace still not working with CCS9.3

Part Number: SIMPLELINK-CC13X2-26X2-SDK
Other Parts Discussed in Thread: ENERGYTRACE

Tool/software: Code Composer Studio

After my complain about the not working EnergyTrace in CCS9.2 i've got the answer that the problem is solved with CCS9.3. But it is not solved. It is still not working.

If i start EnergyTrace while in debug-mode i get a bunch of errormessages in the console window :

Cortex_M4_0: GEL Output: Memory Map Initialization Complete.
Cortex_M4_0: GEL Output: Board Reset Complete.
IcePick_C: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001)
CS_DAP_0: Error: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001)
IcePick_C: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001)
IcePick_C: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001)
IcePick_C: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001)

Beside this i get unrealistic values: Peak-Current 120mA with all task are sleeping and wait for some HW-events.

And if i try to start EnergyTrace in Stand-alone-mode, it doesn't start. It shows a progress window with 'Detecting EnergyTrace Pod' and after a short time the window disappears and nothing more happens.

  • Hi Jan,

    What example project are you using and from what SimpleLink SDK?

    Can you try with a new CCS workspace?

  • After creating a new empty workspace everthing seems to work. Can you tell which configuration files are responsible for the EnergyTrace, and should deleted to make EnergyTrace working with my development Workspace?

    Regards

    Jan

  • Hi Jan

    Jan Ingwer Baer said:
    . Can you tell which configuration files are responsible for the EnergyTrace, and should deleted to make EnergyTrace working with my development Workspace?

    Try deleting the files in:

    [WORKSPACE  FOLDER]\.metadata\.plugins\com.ti.dvt.energytrace\

    Thanks

    ki

  • Thank you for your reply, but it doesn't work.

  • After creating a new workspace EnergyTrace starts. After one time applying the EnergyTrace preferences it does not start any longer.

    I think this is a major issue.

  • I having playing around with the stand-alone EnergyTrace feature in CCSv9.3.0 with my CC1312 LaunchPad. So far it was been working without issue. I set the one time preferences, apply the changes and it works. Subsequent sessions continue to work fine. 

    It must be some issue specific to your environment. Please provide your Eclipse logs and what exact host OS version you are using.

    Thanks

    ki

  • Jan Ingwer Baer said:
    After creating a new workspace EnergyTrace starts. After one time applying the EnergyTrace preferences it does not start any longer.

    Also, both the standalone and CCS debug-mode ET fails (the XDS110 error messages occur)?

  • 
    

    I have different problems with EnergyTrace. standalone and debug-mode:

    standalone EnergyTrace

    - Create new Wokspace c:\CCS-ET-Test
    -> Stand-alone ET start
    
    - Changed preference for ET :
      Window->Preferences->Code Composer Tools->Advanced Tools->EnergyTrace
      change Cell Type to Custom, 3.0V, 220mAh
      'Apply and Close'
    -> Stand-alone ET does not start : 
      Show Progress Window : Detecting Energy Trace Pod, Progress Window closes and nothing more happens.
    
    - Open preferences window again and close it with 'Cancel'
    -> Stand-alone ET starts again
    
    - Open preferences window again and close it 'Apply and Close'
    -> Stand-alone ET does not start : 
      Show Progress Window : Detecting Energy Trace Pod, Progress Window closes and nothing more happens.
    
    Opening the preferences from within the ET-window and closing with 'Apply and Close' has the same effect.
    
    Host-OS : Windows 10 Pro, 64-bit, Version 1803, OS-build:17134.1246
    CCS Version: 9.3.0.00012 

    debug-mode EnergyTrace

    Some error messages :

    IcePick_C: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001) 
    IcePick_C: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001) 
    CS_DAP_0: Error: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001) 
    IcePick_C: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001) 
    CS_DAP_0: Error: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001) 
    IcePick_C: Error: (Error -261 @ 0xFFFFFEFB) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001) 

    Cortex_M4_0: Error: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001) 
    Cortex_M4_0: Trouble Reading Register REG_ENDIAN: (Error -215 @ 0x0) The semaphore for the test bus controller is in a time-out state. Unified-SCIF was unable to acquire the semaphore used to express ownership of a controller by a utility or debugger. You may have to exit other clients because the timeout occurred. (Emulation package 9.1.0.00001) 
    

    Different errors running ET in debug mode :

    • Start debug-mode -> Open ET -> Start application -> ET++ collect data for 10 s, but the red-button still lit -> Click red button to stop ET -> Freeze
    • Start debug-mode -> Open ET -> Start application -> ET++ start to collect data -> XDS110-ErrorMessage: Cortex_M4_0: Error: (Error -261 @ 0x0) Invalid response was received from the XDS110. (Emulation package 9.1.0.00001) -> ET++ stop to collect data and debugger stops at unkonown location
    • Start debug-mode -> Open ET -> Start application -> ET++ start to collect data but time counter does not run regulat and many error-messages IcePick_C & CS-DAP (see above) -> After some time ET stop to collect data -> After switching window to append to this message CCS is frozen.

    Host-OS and CCS-version same as above.

    Summary :

    On my system EnergyTrace does not work reliable. In special the debug-mode EnergyTrace is nearly unusable because i have to abort and restart CCS after most runs.

  • Jan,

    Sorry to hear of your struggles with EnergyTrace. I am unable to reproduce this myself, hence I have escalated the issue to the EnergyTrace experts. I will be sure to update this thread as I get any updates to share.

    ki

  • One more question - what exact device are you working with? And what kind of board (LaunchPad)?

    Thanks

    ki