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, while my XDS100v2 works fine

Part Number: TMDSEMU110-U
Other Parts Discussed in Thread: TMS320F28379D

Tool/software: Code Composer Studio

Hey every one

We have a customized board with TMS320F28379D microcontroller. 

I am able to programming and debugging with my XDS100v2. However, I purchased a XDS110 debugger and unfortunately I can't program/debug now.

Error code is as below:


[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\ycetin\AppData\Local\TEXASI~1\CCS\
ti\2\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 27 2018'.
The library build time was '13:02:43'.
The library package version is '8.0.903.4'.
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]

The corresponding schematic is as follows:

By the way, I tried nearly all of the suggested ideas in the forum

- Device reset

- Drivers verified

- Firmware upgraded

- Checked on different XDS110 debuggers, different cables, different boards 

- Tried at lower frequencies including 1Mhz, 500kHz, 100kHz

- Also I shortened R14 (2k2 ohm resistor) in my HW and still no success

- On the other hand, we changed nRESET (XDS110 - pin no: 15) with TRSTn (XDS110 - pin no: 2). Because it is connected in this way at XDS100v2 and still no success (the figure is below)

Any suggestions will be appreciated, thanks for your time

  • Hi,

    Thank you for the very detailed post. The F28x family of devices has a very specific issue with strong pull down resistors on the TRST signal.

    Please check the reference below and search for the error code 233.:
    dev.ti.com/.../

    Hope this helps,
    Rafael
  • Hello Rafael,

    Thanks for your reply. 

    First of all, We changed the pull-down resistor from 2.2k ohm to 10k ohm. But we didn't able to program/debug with CM10 (20-10 pin) header despite of this change.

    Then we changed the CM10's pin 10 from XDS110's pin 15 (nRESET) to XDS110's pin 2 (TRSTn) and now we can program/debug now.

    So, as you can see our schematic above post, do we need to make a modify on our hardware to use with original CM10 (20-10 pin) header?

  • Hi Desouza,

    I have exactly the same problem. I connected the NReset pin to the TRSTn and it worked, what is the solution for it ?

    Thanks.
  • Yasin,

    Please apologize; I missed your last reply.

    Thanks for the added information; this is really interesting.

    Since the Cortex M family of devices only features 4-wire JTAG (TCK, TMS, TDO, TDI), its corresponding standard connectors do not provide for the TRST signal. However, certain TI devices (including the F28x) still require this signal to properly initiate the JTAG transfers.

    Given the XDS110 Debug Probe features this signal on its cTI 20-pin connector, the re-route of the signal is a valid proposition and I don't necessarily see any loss of functionality for the F28x target devices.

    Hope this helps,
    Rafael