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/TMS320F28055: TMS320F28055 works with XDS100v2 but not working with XDS110 debug probe

Part Number: TMS320F28055

Tool/software: Code Composer Studio

Hello friends,

my hardware is working fine with XDS100v2, but when I am using XDS110 then is not working. When I verify device under Property -> General -> Verify.

XDS 110 is giving below message. 

[Start]

Execute the command:

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

[Result]


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

C:\Users\YOGESH~1.SHA\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 'Nov 6 2017'.
The library build time was '10:36:36'.
The library package version is '7.0.100.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]

 

I had seen many people are facing this problem in the forum but no satisfactory answer. Does anybody in the world able to make XDS110 works. One post I saw some lot of XDS110 having some defect, how can I find my XDS has belonged to the same lot or not.

 

thanks 

yogesh

  • Yogesh,

    Specifically for the F28x family of devices, please check the thread below:
    e2e.ti.com/.../2333828

    I am not aware of defective XDS110 reported but instead failed firmware update problems. If you don't mind, could you copy the links to the threads you saw about that?

    Regards,
    Rafael
  • e2e.ti.com/.../2333834
    e2e.ti.com/.../2257436
    e2e.ti.com/.../604691
    e2e.ti.com/.../602655
    e2e.ti.com/.../2428955
    e2e.ti.com/.../592334 this link is for xds100, but i am getting same error.
    one of the chinees site, i had found that this problem is related to CCS version. i dont know if this is correct then please share which version of CCS we have to use with XDS110.
  • Hi,

    Thanks for sending the additional links, but they don't necessarily indicate defective XDS110 pods but instead problems with the pull down resistor on TRST (as I linked in my previous post) and one issue with the firmware update and host OS incompatibility.

    Therefore I ask: did you verify if your board has the same pull down resistor as mentioned in the post I linked before? That would be the striking point that would cause XDS100 work and not XDS110, especially in F28x devices.

    Regards,
    Rafael
  • Hello Rafael,

    I am not saying XDS failed, I am saying I am also getting same error as mentioned in above links.

    yes I had put 2.2 k pull down register, I also tried with 10k pull down also. But it is not working.

    here I want to again mentioned that XDS100v2 is working fine with same hardware.

    please suggest how to make XDS 110 working.

    thanks in Adavance.

    Yogesh

  • Yogesh,

    I see then. In this case, I have been trying to "break" my setup here with the boards I have at my disposal (a few experimenter kits for F28069, F28335, F28035) but so far I couldn't reproduce this particular issue.

    One last idea that may make a difference: the XDS100 usually runs its TCLK at 1MHz, but the XDS110 runs at 2.5MHz. If the board routing shows marginal performance around this frequency, perhaps decreasing the frequency will have beneficial consequences.

    To change that frequency, check the short clip below:
    https://youtu.be/mKxaztkCsYw

    At last, do you mind sharing the portion of your schematics that show the JTAG connections? I suspect there is nothing very different than what is shown in the other threads, but that could help give further ideas.

    Regards,
    Rafael
  • Hello Mr. Rafael,

    Thanks for your reply. I had found some discrepancy, I am using same hardware socket for XDS100v2 and XDS110. This seems to be wrong to me.

    Does both JTAG devices is having different connection pin outs.

    I will check and update. if you have any information on this the please share links.

    thanks

    Yogesh

  • Hello Mr. Rafael,

    I got XDS110 working, but now XDS100v2 stops. Actually earlier I was few registers in JTAG connection (as shown in JTAG CON image) and that we working well for XDS100v2. For XDS110 we have to do connection as per J2 connector below circuit shown.

    o Mr. Rafael,