Am trying to get my JTAG up, but having problems.
First, in creating a target configuration, the connection is set to
"Texas Instruments XDS100v3 USB Emulator" and then the board or device
does't have an OMAP3730, so I selected OMAP3530 and "save
configuration". When I try to click "Test connection" I get a popup
dialog box "Cannot run program /opt/ti/ccsv5/ccs_base/common/uscif/
dbgtag.exe:java.io.IOException: error=2, no such file or directory".
Ok, so it looks like they are expecting this to be on Windows.
So I copy dbgtag to dbgtag.exe and then get some other error that it
can't run it, but does emit what its trying to run, so then I try that
myself from shell:
./dbgjtag.exe -f /home/dneiss/.TI/3205019477/0/0/BrdDat/testBoard.dat -
rv -o -F inform,logfile=yes -S pathlength -S integrity
-----[Print the reset-command software log-
file]-----------------------------
This utility has selected a 100- or 510-class product.
This utility will load the adapter 'libjioserdesusbv3.so'.
The library build date was 'Oct 27 2011'.
The library build time was '18:01:52'.
The library package version is '5.0.520.0'.
The library component version is '35.34.38.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '4' (0x00000004).
The controller has an insertion length of '0' (0x00000000).
This utility will now 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 FTDI FT2232 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for FTDI FT2232 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 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 '-501' (0xfffffe0b).
The title is 'SC_ERR_TEST_MEASURE'.
The explanation is:
The built-in scan-path length measurement failed.
The built-in scan-path reliability tests cannot be
performed without knowledge of the scan-path length.
Try specifying the scan-path lengths in the command-line
options or board configuration file of this utility or debugger.
So looks like am getting this -501 SC_ERR_TEST_MEASURE error. I see an
LED become lighted on the XDS100v3 board, so seems like it started
talking to the board.
Anyone else have any luck getting CCS5 going with this XDS100v3 on
Linux?