• State Answer Suggested
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 7976 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/TMDSEMU110-U: XDS110 not working, but my XDS100v2 works fine.

Charles Walker
Intellectual 265 points
Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: TMS320F28377D, TMS320F28377S

Tool/software: Code Composer Studio

We have been using the XDS100v2 for nearly a year on a project. We decided to split the project into two halves now. so we needed another jtag. We ordered the XDS110. Bottom line it doesnt work.

I followed everything in the manual.

*Firmware upgraded .

*Reset device

*updated CCS to Version 7.

*proper drivers verified.

* tried testing with multple USB cables (known good cables)

*checked the forum for answers

it just does not work.

I have included below the TEST-SCREEN of the issue. and below that the {xml-code of the XDS110} and below that the {xml-code of my working XDS100v2}..

im out of ideas, and plan to return this thing to TI.com if i cant get some quick ideas. 

thanks for any assistance anyone can give me.  

Chuck

-----------------------------------------------Error screen during Target Testing-------------------------------------------------------------

[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\Chuck\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 'Jul 21 2017'.
The library build time was '19:36:41'.
The library package version is '7.0.48.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_0]

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

----------------------------------------------xml-code XDS110------------------------------------------------------

<?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="TMS320F28377D_0" href="devices/tms320f28377d.xml" id="TMS320F28377D_0" xml="tms320f28377d.xml" xmlpath="devices"/>
<device HW_revision="1" XML_version="1.2" description="" id="TMS320F28377D_0" partnum="TMS320F28377D">
<router HW_revision="1.0" XML_version="1.2" description="ICEPick_C router" id="IcePick_C_0" isa="ICEPICK_C">
<subpath id="Subpath_1">
<property Type="numericfield" Value="0x11" desc="Port Number_0" id="Port Number"/>
</subpath>
</router>
</device>
</platform>
</connection>
</configuration>
</configurations>

  • 0
    Intellectual 265 points
    the screen above wouldnt let me type anything else. heres the other xml code for the xds100v2

    ----------XDS100v2-------------------------------------------

    <?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="TMS320F28377D_0" href="devices/tms320f28377d.xml" id="TMS320F28377D_0" xml="tms320f28377d.xml" xmlpath="devices"/>
    <device HW_revision="1" XML_version="1.2" description="" id="TMS320F28377D_0" partnum="TMS320F28377D">
    <router HW_revision="1.0" XML_version="1.2" description="ICEPick_C router" id="IcePick_C_0" isa="ICEPICK_C">
    <subpath id="Subpath_1">
    <property Type="numericfield" Value="0x11" desc="Port Number_0" id="Port Number"/>
    </subpath>
    </router>
    </device>
    </platform>
    </connection>
    </configuration>
    </configurations>
  • 0 in reply to Charles Walker
    TI__Guru 62975 points
    Chuck,

    Under the Advanced settings for the target configuration, you should be able to modify the JTAG clock frequency. It may be worth trying a slower frequency. The XDS100 runs at 1MHz vs 2.5MHz on XDS110.

    Also, make sure that cJTAG/SWD is disabled and that no other emulators are connected to the PC at the same time.

    -Tommy
  • 0 in reply to tlee
    Intellectual 265 points

    that did not fix the problem.

    but i have found more and more posts on the internet about people able to use the XDS100v2 on there custom boards perfectly fine, but unable to get the XDS110 to work and getting the same error as us. (very strange). the XDS110 works just fine when used with a ti.experimenters board with jtag connector thou.. so it would seem that it not working has been ruled out. now to figure out what the xds110 is needing that the xds100v2 doesnt need. our custome board is wired up the way the ti.com experimenters board was wired up for the chip we used. 

    so still at a loss.

    chuck

  • 0 in reply to Charles Walker
    TI__Guru 62975 points
    Chuck,

    I'll move this over to the Code Composer Forum where they should have more experience with XDS110.

    -Tommy
  • 0 in reply to tlee
    TI__Guru 62975 points
    Chuck,

    I don't suppose that you have an external pull-down on the TRST signal?

    e2e.ti.com/.../2290799

    -Tommy
  • 0 in reply to tlee
    Prodigy 65 points

    I noticed that the TRST signal was only driven to 2.4V when high (using XDS110 on a TMS320F28377S) and just connecting my logic analyser solved the problem. Then I changed the 2.2k ohm pull down resistor suggested (by the datasheet for the processor) to a 10k ohm. That solved the problem (the high level is now 2.8V).

    -Thor

  • 0 in reply to Thor Bruun Jørgensen
    Intellectual 265 points

    Sorry about the delay in responce , wasn't getting emails saying I had reply and after a week originally,  I stopped looking . I work evenings so I'll check that out this evening to see what our schematics show.  I'll post back what we find,  sounds like that could be the issue.

    Chuck

  • 0 in reply to Thor Bruun Jørgensen
    TI__Guru**** 171104 points

    Thor,

    Thank you for sharing your findings. You are not the first one that reported issues with F28x devices and the XDS110. I will pass this information to others and see if this can be validated as well.

    As you mentioned, the value of 2.2kΩ is a suggestion and not a hard requirement.

    "The value of this resistor should be based on drive strength of the debugger pods applicable to the design. A 2.2kΩ or smaller resistor generally offers adequate protection."

    Regards,
    Rafael