Our costumer is developing the project on EK-LM4F232H5QD. He will use XDS100v3 for debuging and programming the final device. Now client wants to check compatibility of XDS100v3 with LM4F232H5QD on the evalution board directly. For this purpose pin 3 of J1 header(~EXTDEBUG) on EK-LM4F232H5QD is tied to GND. On XDS100v3 TCK is connected to RTCK. TDI, TDO, TCK, TMS, TRST, GND, 3V3 lines from XDS100v3 are connected to EK-LM4F232H5QD. But when customer tests the conection in CCS v5.3.0.00090, the message is coming:
[Start]
Execute the command:
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
[Result]
-----[Print the board config pathname(s)]------------------------------------
C:\Users\PROKOP~1.RBA\AppData\Local\.TI\
1989394224\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 'jioserdesusbv3.dll'.
The library build date was 'Oct 3 2012'.
The library build time was '21:58:41'.
The library package version is '5.0.872.0'.
The library component version is '35.34.40.0'.
The controller does not use a programmable FPGA.
An error occurred while hard opening the controller.
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-183' (0xffffff49).
The title is 'SC_ERR_CTL_CBL_BREAK_FAR'.
The explanation is:
The controller has detected a cable break far-from itself.
The user must connect the cable/pod to the target.
[End]
Where can be a mistake? Which way is suitable to check XDS100v3 on EK-LM4F232H5QD directly?
Thanks for help ahead of time.
