TMS570LC4357: TMDSEMU200-U and TMS570LS3137 connection issue

Dejan Sajic

Part Number: TMS570LC4357
Other Parts Discussed in Thread: TMS570LS3137

Hello,
We have a customer who has a custom development board using the TMS570LS3137 ARM chip. They prefer the Lauterbach debugger T32 with a LA-3253 debug cable. This setup works and we can program and debug with it. Now we want to switch to CCS + XDS200 debugger and it doesn't work with the provided "20e_cTI-20t_ARM Pin Converter" connector.
The connectors should be the same 20 pin ARM and I don't see any reason why it shouldn't work out of the box?

Can you support me with this issue?

Lauterbach Connector Pinout:

CCS configuration:

Error Log:

[Start: Texas Instruments XDS2xx USB Debug Probe]

Execute the command:

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

[Result]

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

C:\Users\D4854~1.SAJ\AppData\Local\TEXASI~1\
CCS\ccs1200\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Jun 18 2022'.
The library build time was '03:06:08'.
The library package version is '9.8.0.00235'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '13' (0x0000000d).
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]-----------------------------

This emulator does not create a reset log-file.

-----[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 XDS2xx USB Debug Probe]

over 3 years ago

0 QJ Wang over 3 years ago

TI__Guru**** 193286 points

Hi Dejan,

nTRST is JTAG “Test Reset”. It is low active, and resets the TAP by a certain JTAG sequence. The target device requires that the nTRST is first held low for a few TCK cycles and then raised after the TCK signal has started running, so the device can detect a rising edge on nTRST.

A pull-down resistor should be added onto nTRST on target side. It ensures the on-chip debug logic is inactive when the debugger is not connected. Can you post the schematics of JTAG signals on your target board?

0 Dejan Sajic over 3 years ago in reply to QJ Wang

Prodigy 10 points

Hi QJ Wang,
thanks for your support. Unfortunately, I do not have the schematics and because it's third party HW (Hydac) there is no way to get it. (https://www.hydac.com/che-de/produkte/steuerungstechnik-konnektivitaet/mobil-controller-displays-konnektivitaet/steuergeraete/hy-ttc-540.html)
If it works with the Lauterbach then it should be the same logic implemented or?

0 QJ Wang over 3 years ago in reply to Dejan Sajic

TI__Guru**** 193286 points

The linker doesn't work:

0 QJ Wang over 3 years ago in reply to QJ Wang

TI__Guru**** 193286 points

The value is '-233' (0xffffff17).
The title is 'SC_ERR_PATH_BROKEN'.

It looks like there is no TDO from the device. Can you check the voltage level of the TDO pin and nTRST pin when xds200 emulator is connected to the board?