• State TI Thinks Resolved
  • Locked Locked
  • Replies 3 replies
  • Answers 1 answer
  • Subscribers 82 subscribers
  • Views 292 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/TMS320F28388D: CCS/TMS320F28388D

Tim Clarke
Prodigy 70 points
Part Number: TMS320F28388D
Other Parts Discussed in Thread: TMDSHSECDOCK, TMDSCNCD28388D

Tool/software: Code Composer Studio

Hi,

Can I use the XDS110 to debug the part with the design I copied from the control card (XDS100v2)? What can I do to the XDS110 Debug Probe HW to convert it to the XDS110v2 Debug Probe?

Thanks.

  • 0
    TI__Mastermind 42195 points

    Tim,

    I am a little confused here, perhaps,  what part of the design did you copy? Please note that the F2838x series of devices support XDS110 and XDS100v2.

    Tim Clarke said:
    Can I use the XDS110 to debug the part with the design I copied from the control card (XDS100v2)?

    To try and answer what I think you're asking:

    The XDS100v2 and XDS110 are completely different designs. You cannot convert one to the other, they are simply different emulators. The F2838x series of devices support XDS110 and XDS100v2. XDS110V2 does not exist, I suppose that was a typographical error.

    The TMDSCNCD28388D EVM has an embedded XDS100v2. It also supports the use of a XDS110 through the TI-14 pin header found on the TMDSHSECDOCK that it optionally connects to. If you develop your own custom board i would suggest putting at TI-20 pin or TI-14 pin header and then either emulator will work.

    Regards,
    Cody 

  • 0 in reply to Cody Watkins
    Prodigy 70 points

    Hi Cody,

    This is the error message i receive when i do a "Test Connection" with the Target Configuration:

    ===== start of message =========

    [Start: Texas Instruments XDS110 USB Debug Probe_0]

    Execute the command:

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

    [Result]


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

    C:\Users\tclarke\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 'May 30 2018'.
    The library build time was '23:03:35'.
    The library package version is '8.0.27.9'.
    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_0]

    ====== end of message ========

    Any feedback is greatly appreciated.

    Thanks.

    Tim

  • 0 in reply to Tim Clarke
    TI__Mastermind 42195 points

    Tim,

    flip through this, it has some good information which you may have not seen yet.

    http://www.ti.com/lit/an/spracf0/spracf0.pdf 

    That error message just means there is some significant communication error. Could be related to some device not being powered or missing a clock input. Maybe the data lines are crossed, disconnected, or wrong. Even a missing pull resistor could cause similar behavior.

    You will need to trace the signals and see where you are having a problem.

    On the bright side it doesn't seem like this is a software issue, so we can rule that out. Your target configuration is setup to use a XDS110, though I would still recommend you confirm that you have configured the correct C2000 device in your target configuration.

    Regards,
    Cody