Quantcast
Channel: Forums - Recent Threads
Viewing all articles
Browse latest Browse all 262198

CCS/TMS320C5535: Unable to initiate JTAG communications using a XDS200 spectrum digital programmer

$
0
0

Part Number:TMS320C5535

Tool/software: Code Composer Studio

Hello,

I’m trying to establish communications with a TMS320C5535 (TMS320C5535AZHH10) DSP over its JTAG interface using the Code Composer Studio 7.4.

When I hit the "test communications" button, I get the following output/error:

[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\msz\AppData\Local\TEXASI~1\
    CCS\ti\1\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 'Jan 24 2019'.
The library build time was '13:59:06'.
The library package version is '8.0.903.6'.
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]

The connection configuration is shown here:

The connection to the XDS200 is as follows. The EMU 0 and EMU 1 Pins are not connected to the XDS200 and are Pulled High.

XDS200 information:

Spectrum Digital, Inc.   P/N: 516410 -0001A    S/N: X2B_1509631      Product: XDS200      TMDSEMU200-U, Rev: B, (V) 0033317

C:\ti\ccsv7\ccs_base\common\uscif\xds2xx>xds2xx_conf get xds2xxu 0
boardRev=1
ipAddress=0.0.0.0
ipConfig=dhcp
ipGateway=0.0.0.0
ipNetmask=0.0.0.0
productClass=XDS2XX
productName=XDS200
serialNum=00:0E:99:04:36:1A
swRev=1.0.0.8
hostCPU=AM1802
emuCtrlType=Bit bang
extMemType=SDRAM
portUSB=true
portENET=false
portWIFI=false
portRS232=false
EnableUSBSerial=false
CurrentMeasure=false

Is there something wrong with the way I have connected the XDS200?

The Spectrum Digital programmer is listed as "Texas Instruments XDS2xx usb debug probe" might that be the cause of the issue?


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>