Spectrum Digital XDS560v2 USB Emulator can't connect to 6614

Hi 

I am using Spectrum Digital XDS560v2 Emulator via USB on Win7 PC to connect to 6614.

I keep getting this error:(when run "Test Connection" on target configuration)

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

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]

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

I have run some diagnostics with utility tool from Spectrum Digital (Sd560v2Config ) which seem to be pointing the issue between Emulator& Target Board.

Results from Sd560v2Config utility: 

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

• If using USB Run the Loop back test to verify the USB link between the PC and XDS560V2

STM. -> PASSES

• If using Ethernet use the Eth tab and verify that you can find your ipAddress.-> NA

• At this point either of the communications mediums should be active. From the Dtc Conf tab run a

“get” command. This ensures the next level of communication with the XDS560v2 STM is

functional. -> PASSES

• Make sure you have the XDS560v2 STM connected to your target and your target is powered.

From the DbgJtag tab you should run the Reset and PathLength tests and confirm that both

succeed without error. By running these tests successfully you would have verified that the

emulation processor, emulation controller (FPGA) and target cable are functional. If the tests do

not pass then refer to the TI WIKI for diagnosing scan problems. -> FAILS

• There are a few special circumstances where DbgJtag will fail and it is not related to a scan chain

or target problem. In general these occur when the USCIF component of the TI driver stack is in a

confused state following a CCS abnormal termination. When this occurs the typical errors are -

120, -121 or RPC related errors. If using USB then you may be able to clear it up with a “Force

USB EEOS” from the USB Status tab and then re-run DbgJtag. If the errors persist then you can

reboot the XDS560v2 STM with the “boot” command from the Dtc Conf tab. -> TRIED THIS, THIS DOESN’T CHANGE BEHAVIOR

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

 Any pointers on what might be the issue or any pointers to debug further ?

PC used is Win7, CCS v5.1.1

Thanks !