CCS/TMS570LS0714: XDS110 Debugger error

Hello Andrea,

1. Please shorten the wires for JTAG signals (TCK, TMD, TDO, TDI, nTRST)

2. Please try the slower JTAG speed, for example 1MHz

I tried with a slower JTAG speed at 1 MHz but the problem is the same, I will try tomorrow to shorten the cables but I have a problem even just to recognize the debugger without JTAG connection. So could be another problem?

trying the test connection I get this error:

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.

I shorten the cable and set 1 MHz but the errors are the same. I show you the picture of the cable.

I am trying to charge a "hello world" program on a launchpad TMS570LS12x development kit as well. In this case, I am using the xds110 debugger to power supply the target, and the launchpad has some pins to connect a JTAG, so I connected everything but I have the same problems even just testing the connection. Is there some way to test just the XDS110 debug probe? 

[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\Andrea\AppData\Local\Texas Instruments\
CCS\ccs1011\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 7 2020'.
The library build time was '21:10:18'.
The library package version is '9.2.0.00002'.
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]

Looking at some forum discussions I sow someone use pull up and pull down resistors. In my case, The signal goes directly from the micro to the XDS110 debug, I have no pull-up or pull-down resistors. Is this a problem?

Please add a pull-down to NTRST. 

Which value for the resistor? It will be not so easy as the PCS is done as shown in the previous picture. I will put the resistor directly in to the connector. In addition I would like to comment that I have tried with a TI lanchpad wich has almost the same microcontroller, the launchpad is the  LAUNCHXL2-TMS57012

trying to charge a hello world code with the target configuration as shown in figure above, using the debugger into the lanchpad wich should be the same XDS110 and I have exactly the same problem doing the test connection and the debug. Could it be a software problem? maybe version of CCS? I am using the last 10.1.1.

Using a resistor of 8 kohms tu pulled down the NTRST I have the same error.

I noticed there are 6 wires between JTAG emulator and your board? What are those signals?

JTAG signals of XDS110 header: TCK, TMS, TDI, TDO, nTRST, GND, Vref, RTCK

I am using on JTAG signals of XDS110 header 3.3 V for VTRef-5 and GND for GND-10 with a power supply. In addition:

uC pin                  XDS CTI-20 pin

TMS-108             SWDIO/TMS-1

nTRST-109          NTRST-2

TDI-110               TDI-3

TDO-111             SWO/TDO-7

TCK-112              TCK-11

RTCK-113            NONE

The error seems to be a power supply problem, but I checked the datasheet and the layout and it seems to be right, can you confirm me that? Here is the image of the layout:

Thi is what I see on TDO with the oscilloscope:

Hello,

Please share the GND between JTAG emulator and your board. The JTAG emulator needs to know the power supply (VTref, 3.3V) on your board.

Hello, I did but I have the same problem. In addition I have a launchpad with the same XDS110 debugger and a uC of the same family. The launchpad works correctly and I am comparing the test connection of the debug in both cases. The signal on the PCB are a bit dirty but the big difference is on the TDO. I show you the images below. The images ended in L are the Launchpad signals, the images ended in P are the PCB signals:

There is no response from TMS570. The MCU may be in reset state.

Oh, I didn't see it. So it should be pulled up to 3.3V or it could be pulled up to 1.2V? It is because I have a 1.2V signal on one side of this pin. Which resistor do you recommend me to use for this pull up? Can I connect this pin directly to the voltage without resisotr? In the datasheet as shown in table I can't see any resistor value.

Everything is working correctly now, thank you so much.