Can't connect XDS200! Possible Windows 10 driver issue

Hi,

I forgot to mention that on other computers debugger work.

Ok.. I follow a steps from your link:
When I make "Test Conection" in .ccxml first time I get:

[Start: Texas Instruments XDS2xx USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\Mare\AppData\Local\TEXASI~1\CCS\
    ti\0\0\BrdDat\testBoard.dat

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

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
The library build date was 'Sep 28 2018'.
The library build time was '16:56:12'.
The library package version is '8.0.803.0'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '13' (0x0000000d).
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]-----------------------------

This emulator does not create a reset log-file.

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS2xx USB Debug Probe_0]

It looks good but just on the first try...
If I run "Test Connection" again I get:

[Start: Texas Instruments XDS2xx USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\Mare\AppData\Local\TEXASI~1\CCS\
    ti\0\0\BrdDat\testBoard.dat

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

This utility has selected a 560/2xx-class product.
This utility will load the program 'xds2xxu.out'.
E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Open::dtc_io
Failed to open i/o connection (xds2xxu:0)

An error occurred while soft 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 '-250' (0xffffff06).
The title is 'SC_ERR_ECOM_EMUNAME'.

The explanation is:
An attempt to access the debug probe via USCIF ECOM has failed.

[End: Texas Instruments XDS2xx USB Debug Probe_0]

Also when I try to run Debug:

Error initializing emulator:
(Error -2083 @ 0x0)
Unable to communicate with the debug probe. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.
(Emulation package 8.0.803.0)

I found on forum ->  issues about hubs. I change the USB port on the computer and upper story repeat (first-time success connection then debugger fails to connect...)

I'm researching further...

Update:

When I change port I get one-shot chance for connecting (but it seens that it work just in case when port has never been connected with debugger before), and try:

C:\ti\ccsv7\ccs_base\common\uscif\xds2xx>xds2xx_conf get xds2xxu 0
boardRev=1
ipAddress=0.0.0.0
ipConfig=dhcp
ipGateway=0.0.0.0
ipNetmask=0.0.0.0
productClass=XDS2XX
productName=XDS200
serialNum=00:0E:99:04:3E:BD
swRev=1.0.0.8
hostCPU=AM1802
emuCtrlType=Bit bang
extMemType=SDRAM
portUSB=true
portENET=false
portWIFI=false
portRS232=false
EnableUSBSerial=false
CurrentMeasure=false

Then I try to run debug in CCS and it works! After I Terminate....

C:\ti\ccsv7\ccs_base\common\uscif\xds2xx>xds2xx_conf get xds2xxu 0
Error : test failed

Does it smell like windows/driver issue? 

Mare,

Please apologize for the delay; I missed your past replies.

The first scenario certainly seems odd, given that it seems the dbgjtag utility (that runs under the "Test Connection" function) is holding control over the XDS200. By extension, it seems the first process that accesses the XDS200 holds control over it, preventing any other utilities from accessing the device. The wide span across versions (CCSv7.2.0 and TI Emulators component 8.0.803.0) may explain this, but at this point I can't tell further.

If I understood correctly the last scenario, it sounds very familiar; once CCS accesses the probe once, it tends to hold control until CCS is fully closed. That was the subject of a discussion a while ago but it was never moved forward due to other priorities.

I am out of the office at the moment but will try these scenarios later today and report back. I am using Windows 10 Pro Build 1709 and have a few versions of CCS installed, including 7.2.0 and later.

Regards,
Rafael

Hi,

Now I made reinstal of CCS.
Version: 7.2.0.00013 
Emulation package: 6.0.628.3.

Problem is NOT resolved.