CCS/TMS320F28075: Test connection to XDS110 JTAG debugger fails but XDS100v2 works fine

Andrew Paquette

Part Number: TMS320F28075

Tool/software: Code Composer Studio

I have been using the XDS110v2 JTAG debugger without any problems, programming a custom board with TMS320F28075. I purchased the XDS110, and I am having trouble getting the connection working. I made a new target configuration file for the XDS110, and when I test the connection I get the following error (I'll just paste the whole log here):

----------------

[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\APAQUE~1\AppData\Local\TEXASI~1\
CCS\ti\1\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 'Dec 9 2016'.
The library build time was '13:48:53'.
The library package version is '6.0.504.1'.
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 '-230' (0xffffff1a).
The title is 'SC_ERR_PATH_MEASURE'.

The explanation is:
The measured lengths of the JTAG IR and DR scan-paths are invalid.
This indicates that an error exists in the link-delay or scan-path.

[End: Texas Instruments XDS110 USB Debug Probe_0]

----------------

Since the XDS100v2 works fine, that seems to eliminate any hardware problems on my board. I tried changing the TCLK from the XDS110's default of 2.5MHz to the XDS100v2's default of 1MHz (and even 100kHz), and it didn't help. We are connecting to the board with the Tag Connect TC2050-IDC (8 in. long), with Tag Connect's TC-C2000-M adapter board, and then either directly to the XDS100v2 or to the XDS110 through the XDS110's ribbon cable and included 14pin adapter board. However, dropping the frequency to 100kHz should help if the cable lengths were a problem?

I'm using CCS Version: 7.0.0.00043, running on Windows 10.

Any help would be appreciated.

over 8 years ago

0 Andrew Paquette over 8 years ago

Prodigy 225 points

I noticed that the target configuration file for the XDS110 is using drivers for the xds510icepick, but when I updated CCS7 and got the latest emulation package, it is still referencing the xds510 drivers, so I guess that's normal? Anyways, here are the two target config files (again, the XDS110 won't get a successful test connection, but the XDS100v2 does):

---------------

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
    <configuration XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS110 USB Debug Probe_0" href="connections/TIXDS110_Connection.xml" id="Texas Instruments XDS110 USB Debug Probe_0" xml="TIXDS110_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS110 USB Debug Probe_0">
            <instance XML_version="1.2" href="drivers/tixds510icepick_c.xml" id="drivers" xml="tixds510icepick_c.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510c28x.xml" id="drivers" xml="tixds510c28x.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510cla1.xml" id="drivers" xml="tixds510cla1.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds510cs_child.xml" id="drivers" xml="tixds510cs_child.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320F28075_0" href="devices/tms320f28075.xml" id="TMS320F28075_0" xml="tms320f28075.xml" xmlpath="devices"/>
            </platform>
        </connection>
    </configuration>
</configurations>

---------------

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<configurations XML_version="1.2" id="configurations_0">
<configuration XML_version="1.2" id="Texas Instruments XDS100v2 USB Debug Probe_0">
        <instance XML_version="1.2" desc="Texas Instruments XDS100v2 USB Debug Probe_0" href="connections/TIXDS100v2_Connection.xml" id="Texas Instruments XDS100v2 USB Debug Probe_0" xml="TIXDS100v2_Connection.xml" xmlpath="connections"/>
        <connection XML_version="1.2" id="Texas Instruments XDS100v2 USB Debug Probe_0">
            <instance XML_version="1.2" href="drivers/tixds100v2icepick_c.xml" id="drivers" xml="tixds100v2icepick_c.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds100v2c28x.xml" id="drivers" xml="tixds100v2c28x.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds100v2cla1.xml" id="drivers" xml="tixds100v2cla1.xml" xmlpath="drivers"/>
            <instance XML_version="1.2" href="drivers/tixds100v2cs_child.xml" id="drivers" xml="tixds100v2cs_child.xml" xmlpath="drivers"/>
            <platform XML_version="1.2" id="platform_0">
                <instance XML_version="1.2" desc="TMS320F28075_0" href="devices/tms320f28075.xml" id="TMS320F28075_0" xml="tms320f28075.xml" xmlpath="devices"/>
            </platform>
        </connection>
    </configuration>
</configurations>

---------------

0 desouza over 8 years ago in reply to Andrew Paquette

TI__Guru**** 169894 points

Hi,

Unfortunately I don't have a F28075 board with me, but I threw a lot of F28x devices to my XDS110 probe and was unable to reproduce this issue here: I used F28335, F28069, F2812 and F28377D.

>> However, dropping the frequency to 100kHz should help if the cable lengths were a problem?
Usually that is the case if there are issues with crosstalk or delays. However, the TCLK speed may be hopeless if the strength of the output drivers is not enough to drive the longer wires, connectors, etc. (we recommend 6 in maximum).

>> (...)it is still referencing the xds510 drivers, so I guess that's normal?
Yes, that is normal.

At this point my only recommendation would be to minimize the total connection length and retry. In the meantime I will keep trying to "break" any configurations here.

Hope this helps,
Rafael

Code Composer Studio™︎

Code Composer Studio forum

CCS/TMS320F28075: Test connection to XDS110 JTAG debugger fails but XDS100v2 works fine