Am returning to my board after a bit of a hiatus. It was working before. I try to connect to EVM8148 using XDS100V2 JTAG connection. I can see the various JTAG slaves
Error I get is:IcePick_D_0: Error connecting to the target: (Error -150 @ 0x0) One of the FTDI driver functions used during configuration returned a invalid status or an error. (Emulation package 5.0.569.0)
When I go to the ccxml file and click 'Test Connection' I get the following message.
[Start]
Execute the command:
%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity
[Result]
-----[Print the reset-command software log-file]-----------------------------
This utility has selected a 100- or 510-class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Dec 19 2011'.
The library build time was '21:32:12'.
The library package version is '5.0.569.0'.
The library component version is '35.34.39.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).
-----[The log-file for the JTAG TCLK output generated from the PLL]----------
There is no hardware for programming the JTAG TCLK frequency.
-----[Measure the source and frequency of the final JTAG TCLKR input]--------
There is no hardware for measuring the JTAG TCLK frequency.
-----[Perform the standard path-length test on the JTAG IR and DR]-----------
This path-length test uses blocks of 512 32-bit words.
The JTAG IR instruction path-length was not recorded.
-----[Perform the Integrity scan-test on the JTAG IR]------------------------
This test will use blocks of 512 32-bit words.
This test will be applied just once.
Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
-----[An error has occurred and this utility has aborted]--------------------
This error is generated by TI's USCIF driver or utilities.
The value is '-154' (0xffffff66).
The title is 'SC_ERR_FTDI_WRITE'.
The explanation is:
One of the FTDI driver functions used to
write data returned bad status or an error.
[End]
I've tried this with 2 different USB cables in multiple different usb ports with a whole bunch of reboots of board and computer.
Also ran xds100serial.exe and it says:
c:\ti\ccsv5\ccs_base\common\uscif>xds100serial.exe
xds100serial.exe
Scanning for XDS100 emulators...
VID/PID Type Serial # Description
0403/a6d0 XDS100v1/v2 TIUU1AQI Texas Instruments Inc.XDS100 Ver 2.0
Any other ideas?
Thanks,
O..
