A cable break that is near-to itself - Error -182 in TWO XDS560V2 emulators

Hi,

In my company we have four Spectrum Digital emulators:
- 3x XDS560v2 STM,
- 1x XDS510.

So far we had no issues, however all of a sudden I tried to use one of
XDS560v2 and received:

"Error connecting to the target:
(Error -182 @ 0x0)
The controller has detected a cable break that is near-to itself.
The user must connect the cable/pod to the controller.
(Emulation package 5.0.872.0)".

One day everything was fine and the next day in the morning the error occurred.

I switched the cables/pods between two working XDS560v2 and the error was consistent.

Working XDS still worked and the bad one still showed error -182.

I haven't switched the cables back. It seemed for that time that cables are fine.

--------

After two days I came back to the bad emulator. With my colleague we tried to check if the error
occurs on his system - he was actually debugging the application with his device using the third XDS560, so I asked him to try the bad one.

He also got the -182 error. So for the sanity check we tried to once again switch cables but this time between the bad one and the third one.

The only thing we did here was to unplug the cable from the third working one, and then connect it to the bad one and see what happend. Error still occurred so we unplugged the bad one and connected usb cable and power to the working one. We didn't connect the cable for the moment and simply try to see if the same error comes up in the working emulator with acctually cable/pod disconnected. It showed up -182 error. So we decided that the test is over and simply plugged the emulator to the cable and to the device.

And here is the moment when the really bad thing happend. The third one along with the first one are now showing the same error. It's reallly bad.

-------

I have used Sd560v2Config application to verify the error (all previous tests were done in CCSv5.3.0). Here's the results for both bad ones:

Spectrum Digital Configuration Utility

Supports:
XDS560V2 USB

@BEGIN-1
MSG: NUMBER OF EMULATORS CONNECTED : 1

PRODUCT        SERIAL NUMBER        ADDRESS
--------------------------------------------------------------------------------------------------

-------------------
XDS560V2 STM        S560-000E9902D582    18573000
@END-1

@BEGIN-1
MSG: USB LOOPBACK TEST PASSED
@END-1

@BEGIN-2
MSG: USB PRINT STATISTICS COMPLETED
@END-2

@BEGIN-3
MSG: EEOS ON USB SUCCESSFULLY COMPLETED
@END-3

@BEGIN-2

CMD:dbgjtag.exe -d sd560v2u -p 0 -S integrity
Loaded FPGA Image: C:\ti\ccs_v5.3.0\ccsv5\ccs_base\common\uscif\dtc_top.jbc

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 '-182' (0xffffff4a).
The title is 'SC_ERR_CTL_CBL_BREAK_NEAR'.

The explanation is:
The controller has detected a cable break that is near-to itself.
The user must connect the cable/pod to the controller.
@END-2


----------------

Spectrum Digital Configuration Utility

Supports:
XDS560V2 USB

@BEGIN-1
MSG: NUMBER OF EMULATORS CONNECTED : 1

PRODUCT        SERIAL NUMBER        ADDRESS
--------------------------------------------------------------------------------------------------

-------------------
XDS560V2 STM        S560-000E9902D57A    18572200
@END-1

@BEGIN-1
MSG: USB LOOPBACK TEST PASSED
@END-1

@BEGIN-2
MSG: USB PRINT STATISTICS COMPLETED
@END-2

@BEGIN-3
MSG: EEOS ON USB SUCCESSFULLY COMPLETED
@END-3

@BEGIN-1

CMD:dbgjtag.exe -d sd560v2u -p 0 -S integrity
Loaded FPGA Image: C:\ti\ccs_v5.3.0\ccsv5\ccs_base\common\uscif\dtc_top.jbc

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 '-182' (0xffffff4a).
The title is 'SC_ERR_CTL_CBL_BREAK_NEAR'.

The explanation is:
The controller has detected a cable break that is near-to itself.
The user must connect the cable/pod to the controller.
@END-1

-------------

I have given the cables to the our production department so they would inspect the cables under the scope, however the first test when both cables were fine (they workd with the second emulator)
is pretty distrubing.

------------

Is there any thing else I can do ?
I must add that I have made any connects and disconnects of the cable to the emulator
as carefully as possible.

Thanks in advance for any help and suggestions,
Best regards,
Pawel Dabrowski