• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 54 subscribers
  • Views 640 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/TMS570LS3137: Will this combination work: XDS560v2 STM, CCS v8, Windows 10 ?

Hugh Shane
Intellectual 565 points
Part Number: TMS570LS3137
Other Parts Discussed in Thread: TMDS570LS31HDK

Tool/software: Code Composer Studio

I just purchased an XDS560v2 STM JTAG Emulator and am now trying to make it work with CCS v8 under Windows 10 without success. Should I even expect this combination even work? My earlier research seemed to indicate that it would but now I'm not so sure. In any case, when I test the connection I get the following errors. What am I doing wrong?

[Start: Texas Instruments XDS560 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\ShaneH\AppData\Local\Texas Instruments\
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 'xds560.out'.
Failed to open i/o connection (\\.\xds5600)

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 XDS560 Debug Probe_0]

  • 0
    TI__Guru**** 472151 points

    Hi Hugh,

    Hugh Shane said:
    just purchased an XDS560v2 STM JTAG Emulator and am now trying to make it work with CCS v8 under Windows 10 without success. Should I even expect this combination even work?

    Yes, that is a supported configuration. I just validated it myself. I was able to successfully connect to my TMDS570LS31HDK using CCSv8.3.1 and a Blackhawk XDS560v2 debug probe on Windows 10-64

    Hugh Shane said:
    n any case, when I test the connection I get the following errors. What am I doing wrong?

    Hugh Shane said:
    The value is '-250' (0xffffff06).
    The title is 'SC_ERR_ECOM_EMUNAME'.

    You are getting a type of host connection error. It is a communication error between your PC and the XDS560v2 debug probe. There are many potential root causes. Please take a look at the below troubleshooting link for more details and suggestions on how to diagnose:

    http://software-dl.ti.com/ccs/esd/documents/ccsv7_debugging_jtag_connectivity_issues.html#host-connection-error

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 565 points

    I suspect there is a device driver issue. Windows Device Manager reports that "The drivers for this device are not installed." What driver should I install? The debug probe vendor's web site (http://support.spectrumdigital.com/) only lists driver support for CCS up to v4.0.

    Hugh 

  • 0
    TI__Guru**** 472151 points

    Hugh Shane said:
    [Start: Texas Instruments XDS560 Debug Probe_0]

    It looks like you are using the wrong configuration. The above option is for the XDS560 PCI card, NOT the XDS560v2 debug probes.

    You need to select a connection specifically for the XDS560v2. The option needed will depend on the vendor of your XDS560v2 probe. For example, the below image has options for the XDS560v2 for Blackhawk and Spectrum Digital.

    If those options are not available, that means you did not select to install the drivers for them when you installed CCS (they are not enabled by default).

    Since you are also getting a message from Windows that the drivers for your XDS560v2 is not installed, it sounds like you did not install the required drivers when you installed CCS. You can re-run the CCS installer over your existing installation to install additional components that were initially missed.

    Thanks

    ki