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/ENERGYTRACE: EnergyTrace++ not working with CC1310 Launchpad

Part Number: ENERGYTRACE
Other Parts Discussed in Thread: CC1310, CC1350, LAUNCHXL-CC1352R1, LAUNCHXL-CC1310

Tool/software: Code Composer Studio

I have the XDS110 with an add-on module connected to the CC1310 LP where the power is supplied via the XDS probe pins TGTSUPPLYOUT. The connection is shown below. I am able to start the energy trace using CCS10 but when I switch to energy trace++ mode, the power monitor fails to start and I get fail to stream ET. Is CC1310 not supported by EnergyTrace++ mode or am I missing something here?

Any directions will be a great start to get this working as I am interested to see in what states my CPU and peripherals are so that I can debug and minimize the overall power consumption.

  • Hi,

    I am able to make ET++ work on my CC1350 board (same architecture as CC1310), therefore I wonder if something else may be wrong in the setup or with temporary files. 

    The first thing I would check is if the configuration is set to 4-pin JTAG - otherwise the tool will throw back an error. 

    Other troubleshooting aspects can be found in the thread below - despite it describes a slightly different problem, it shows some useful methods to try to workaround this issue. 

    https://e2e.ti.com/support/tools/ccs/f/81/t/908536

    Hope this helps,

    Rafael

  • Hi,

    Thanks for these tips. I will try it out and see if it works!

  • After spending almost 2 hours and trying all the possible solutions that have been mentioned here:

    https://e2e.ti.com/support/tools/ccs/f/81/t/908536

    as well as on the other threads plus installing a fresh CCSv10, did not manage to get EnergyTrace++ to work on CC1310 LP. 

    As usual, EnergyTrace works but not the EnergyTrace++ which is the most important aspect.

    Any further attempts seem to be futile. I am not at all happy with the outcome so far. This XDS110 ET module is supposed to make things simpler rather than a painstaking task.

    Also what surprises me is that even enabling the EnergyTrace++ in the preferences

    when the ET is running, the ET++ icon is disabled 

    and when I click preferences again then the states graph appears but the ET fails to start streaming.

    Is there an issue with the CCS10 or something wrong with the XDS, I have no clue how to get it running.

  • Hi,

    The screenshots hint that you are using macOS. There were a few issues with EnergyTrace and macOS, but I recall being able to use EnergyTrace++ on this architecture after installing CCSv10 or CCSv10.1 (I know there are reported issues with CCSv9.1).

    I will try this mode in this OS and report back.

    Regards,

    Rafael

  • Hi,

    I have tested both the standalone XDS110+HDR and a Launchpad (LAUNCHXL-CC1352R1) on both CCSv9.3 and CCSv10.0 without issues. The OS I am using is Catalina (10.15.4) on a MacBook Pro 2013. (ignore the errors below; the debug probe was disconnected before launching the debugger)

    (edit) one aspect important: did you set your target configuration to 4-pin JTAG? ET++ does not work with cJTAG, which is the default setting of the target configuration file (.ccxml).

    With this, I am unsure what else to do to workaround this. I will try to get help from other developers and see if they could provide any additional insights.

    Regards,

    Rafael

  • Hi Rafael,

    Yes, I am using macOS with CCSv10. After I was unsuccessful to make XDS work on my macOS, I then freshly installed the latest version of CCS on a windows machine with the config to 4-pin JTAG, but still energytrace++ did not work with CC1310-LP.

    I have purchased a CC1352R-LP and will try it out once I receive the board.

    Thanks for the feedback. I will report back once I get it working.

    Rajeev

  • Hi Rafael,

    I tested the standalone XDS110 + HDR module with my CC1352R-LP and the configurations outline by you worked with the current CCS10 installed on my MacBook.

    Then, I switched to the CC1310-LP and tested it out but as usual, EnergyTrace+ failed to work at all.

    Would it be possible for you to test on CC1310 (if you have a board laying around) so that our outcomes can be compared? It looks like to me that something is broken (possibly in CCs) that's why EnergyTrace+ does not work on CC1310 architecture while it works on CC1350 and onwards.

    Thanks

    Rajeev

  • Rajeev,

    Thank you for performing further tests. Unfortunately I don't have a CC1310 with me (locked at my office due to the quarantine) but, as you can see from my previous screenshot, I tested on the CC1350 and it worked. There are no differences between the two devices with regards to the EnergyTrace and JTAG connectivity, at least according to the device experts (reference here), but I wonder if there is something else at play here. I will have to investigate some more and see if I can also get some insights from a device expert. 

    Regards,

    Rafael

  • Rajeev,

    I ordered a CC1310 Launchpad so I could be absolutely certain about the operation of ET+ on this device. It may take a couple of days to arrive. 

    Regards,

    Rafael

  • Rajeev,

    The LAUNCHXL-CC1310 board arrived and indeed the ET+ mode on this device is not operational. 

    There is a chance this device may be a previous generation of the CC13xx family, thus I am confirming these details with the developer of EnergyTrace. 

    At this point I would consider treating the CC1310 device as not having ET+. Sorry.

    I apologize for the inconvenience,

    Rafael

  • Hi Rafael,

    Thanks for getting back to me on this and taking out your precious time to validate my findings. After those experiments, that's what my conclusion was but I was waiting for confirmation from you.

    Please update the respective EnergyTrace documentation to reflect that CC1310 is not supported in ET+ mode.

    Thanks once again.

    Rajeev