Hey there TI support team,
Myself and my lab partner are consistently getting an error message when using the TI XDS100v2. Our target is the TI AM1705. We have checked the VID/PID which are correct for both Channel A and Channel B. We have tried on three different operating systems, lubuntu, Windows 7 and Windows XP. I even formatted my laptop this morning in case it was a collision issue with a previous FTDI driver. On all three machines we have seen the same error message:
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.1.641.0)
The Test Connection utility yields the following output:
[Start: Texas Instruments XDS100v2 USB Debug Probe_0]
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:\DOCUME~1\Alex\LOCALS~1\APPLIC~1\TEXASI~1\
CCS\ti\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 'jioserdesusb.dll'.
The library build date was 'Feb 18 2015'.
The library build time was '23:56:50'.
The library package version is '5.1.641.0'.
The library component version is '35.34.40.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 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: Texas Instruments XDS100v2 USB Debug Probe_0]
Any insight that could be provided into why we are receiving this error message would be great. Other information that may help: We have grounded TDIS on the target board. EMU0 and EMU1 pins are floating. We have a 1k pull up on TRST. TDI, TDO, TMS, TCK, RTCK do not have any external pull ups or pull downs.
Cheers
James
