TMS320F28035: XDS100v1 USB emulator driver not getting installed in CCS 12.8.0

Hello,

MM said:

Re installing CCS did not help (Installed full package not custom). Below is the screenshot from C:\ti\ccs1280\ccs\ccs_base\common\targetdb\connections

TIXDS100usb_Connection.xml is for the XDS100v1.

MM said:

I want to use onboard emulator XDS100v1 but not getting option in target configuration drop down.

Do you not see this option?

It should apply for all XDS100v1 probes regardless of vendor.

Hi Ki,

I can see that option but I get error when I try to connect. Copied error message below

[Start: Texas Instruments XDS100v1 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:\Users\E40070~1\AppData\Local\TEXASI~1\
CCS\ccs1280\0\0\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100/110/510 class product.
This utility will load the adapter 'jioserdesusb.dll'.
The library build date was 'Jul 24 2024'.
The library build time was '18:57:55'.
The library package version is '12.8.0.00189'.
The library component version is '35.35.0.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).

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 '-150' (0xffffff6a).
The title is 'SC_ERR_FTDI_FAIL'.

The explanation is:
One of the FTDI driver functions used during
configuration returned a invalid status or an error.

[End: Texas Instruments XDS100v1 USB Debug Probe_0]

MM said:

The value is '-150' (0xffffff6a).
The title is 'SC_ERR_FTDI_FAIL'.

The debugger was unable to open a connection with the XDS100v1. It could caused by a variety of factors.

Check our the troubleshooting section for the XDS100:

https://software-dl.ti.com/ccs/esd/documents/xdsdebugprobes/files/XDS100.pdf

See the FAQ on page 12 "I got a -150 SC_ERR_POD_FAIL" error. Also try running <CCS INSTALL DIR>\ccs\ccs_base\common\uscif\xds100serial.exe to see if an XDS100 is detected.

Nothing happens when I try to run <CCS INSTALL DIR>\ccs\ccs_base\common\uscif\xds100serial.exe. Command prompt pops up and closes in a second

I can see XDS 100 active in device manager

Do you see any problems in Target configuration?

Thank you ki

I am able to connect to controller and program after running xds100serial.exe. Not sure what was the issue before

I'm not sure either.

xds100serial is just a utility to detect any XDS100 probes and allow you to change the serial number for it.

In any case I'm glad things are working for you.

I am stuck again. Connection stopped working. I did not change anything, since I am not sure how it worked before, I don't know how to fix this

Have you encountered issue like this?

This error is generated by TI's USCIF driver or utilities.

The value is '-150' (0xffffff6a).
The title is 'SC_ERR_FTDI_FAIL'.

The explanation is:
One of the FTDI driver functions used during
configuration returned a invalid status or an error.

MM said:

I am stuck again. Connection stopped working. I did not change anything, since I am not sure how it worked before, I don't know how to fix this

It sounds like your connection with the debug probe unstable. Try switching your USB cable. If you are connected to a USB hub, try connecting directly to your PC.

I was using debug probe which came with experiment kit. Connected directly to the computer. 

Tried with another cable but issue not resolved

what is the results of running xds100serial from the command line?

Weird!. It started working after connecting to different computer and then connecting back to mine

Running xds100serial always shows right connection

Thank you so much for your continuous help. I will try to find root cause of this issue

MM said:

Weird!. It started working after connecting to different computer and then connecting back to mine

There is something flakey here. Maybe the HW kit itself.