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.

  • Resolved

CCS: XDS110 Add-On Energy Trace Debugging

Tool/software: Code Composer Studio

I am attempting to use the Energy Trace HDR for debugging with the CC3220SF LAUNCHXL.

So far I have been able to do the following.

Debug when using an external supply and using an external XDS110 debugging module.

Run an existing program and run energyTrace to see power usage.

What I have not been able to do is debug with the external XDS110 with power being supplied with the Energy Trace HDR.

I have setup a ccxml file as shown below.

When I run Test connection i get the following output.  The problem seems to be that the board does not stay powered during the test.  The following sequence occures then I run Test Connection.

  • 2 sec delay
  • Board powers for approximately 1 second before turning off.
  • 2 sec delay
  • Board powers for approximately 1 second before turning off.

If I use the exact same setup and have the board externally powered the test completes successfully.

As stated above I can use EnergyTrace when not debugging.

The output error I receive is shown below.

[Start: Texas Instruments XDS110 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\BEN~1.GPA\AppData\Local\TEXASI~1\
CCS\ti\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioxds110.dll'.
The library build date was 'Feb 8 2018'.
The library build time was '18:36:28'.
The library package version is '7.0.188.0'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.

The explanation is:
The JTAG IR and DR scan-paths cannot circulate bits, they may be broken.
An attempt to scan the JTAG scan-path has failed.
The target's JTAG scan-path appears to be broken
with a stuck-at-ones or stuck-at-zero fault.

[End: Texas Instruments XDS110 USB Debug Probe]

  • Guru 132420 points
    Hi,

    Thanks for reporting this; somewhat recently I have noticed a similar scenario exclusively with the Test Connection button and the XDS110+HDR pod when used with CC32xx devices. If I recall correctly, this behaviour does not affect other device families such as CC26xx, CC13xx or MSP432.

    Instead, can you try to simply connect to the device? If all connections are correct, the power should be continuously provided to the target.

    I am out of the office, thus I will file a bug report next week for analysis.

    I apologize for the inconvenience,
    Rafael

    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

  • Guru 28430 points

    In reply to desouza:

    Hi Rafael,

    I haven't XDS110 + ETHDR, but do you have selected "High current, wider range lower accuracy" in EnergyTrace preferences ( www.ti.com/.../spruie1 Figure 5)?

    Jan

    Please click to "Verify Answer", if your question was answered.

  • Guru 132420 points

    In reply to Hnz:

    Jan,

    Thanks for the suggestion. If I am not mistaken, the shunt selection shouldn't matter for the XDS110+HDR+CC3220 launchpad, given this combination does should not surpass the lower range's maximum current of 120mA.

    If in doubt, however, you can try to set it to the higher range and get up to 400mA. Optionally, use the auxiliary USB cable connected to the HDR to give you up to 800mA (a single USB2.0 port can yield up to 500mA total, therefore the auxiliary cable is needed).

    Regards,
    Rafael

    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

  • Guru 28430 points

    In reply to desouza:

    Hi Rafael,

    Calibration current of CC3220 is 450mA at 3.3V. In normal PHY calibration mode is calibration done at NWP boot-up.

    Jan

    Please click to "Verify Answer", if your question was answered.

  • Guru 132420 points

    In reply to Hnz:

    Jan,

    Interesting; I wasn't aware of that. In this case, to be sure one should set the current to the higher range then.

    Despite this, I am usually able to power/connect to the board directly, but in this case I suspect the probe must be in overcurrent mode or my board simply did not have any pre-loaded software.

    I will be able to do more experimentation when I return to the office on Monday.

    Cheers,
    Rafael


    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

  • Guru 28430 points

    In reply to desouza:

    Hi,

    Calibration current is only a short peak (24ms) and maybe from this reason it is not big deal.

    Let me know after experiments at your office.

    Regards,
    Jan

    Please click to "Verify Answer", if your question was answered.

  • In reply to Hnz:

    Hnz
    Hi Rafael,

    I haven't XDS110 + ETHDR, but do you have selected "High current, wider range lower accuracy" in EnergyTrace preferences ( www.ti.com/.../spruie1 Figure 5)?

    Jan

    Yes I am using the High Current Option.  However I have tried both options and they have the same effect.

  • In reply to desouza:

    If I have an open EnergyTrace session it does successfully provide power to the board.
  • Guru 132420 points

    In reply to Ben Arnold:

    Hi,

    Please apologize for the delay; I filed today the bug number DBGTRC-3998. Its status can be verified in the link SDOWP in my signature below.

    Unfortunately a fix for this issue will not be available in the next immediate release of our tools, as its release will happen very soon.

    I apologize for the inconvenience,
    Rafael

    When posting, click on the link Insert Code, Attach Files and more... to attach images, files or use nice formatting.

    If my reply answers your question please click on the green button "This resolved my issue".

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.