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.

TMS320C6748: DSP

Part Number: TMS320C6748

我用XDS560V2仿真器连接TMS320C6748,报错如下:

C:\Users\1\AppData\Local\.TI\3250390240\
0\1\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 'sd560v2u.out'.
E_RPCENV_IO_ERROR(-6) No connection: DTC_IO_Open::dtc_conf
Download failed for file E:\ccs\ccsv5\ccs_base\common\uscif\xds560v2.out

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 named emulator via USCIF ECOM has failed.

[End]

  • 感谢您对TI产品的关注!
    关于你的咨询,你的问题报错看起来跟下面的一样。
    是不是仿真器安装的路径不对,或者重新重新安装一下仿真器驱动试一试。

    https://e2echina.ti.com/support/processors/f/processors-forum/158418/ccs5-5-xds560v2-test-connection

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

    Host connection error

    The error below is thrown by CCS when the device driver is unable to communicate with the JTAG debugger either via USB or Ethernet.
    Due to the nature of the different debug probes, the error messages vary according to the XDS family. This can have several sources:

    • First and foremost: Hardware. Many issues can be caused by the problems described in the previous section Hardware checklist above.
    • The Windows device drivers are not properly installed or failed to initialize. Check the Windows Device Manager, the XDS100 troubleshooting, the XDS110 troubleshooting or the XDS200 troubleshooting.
    • The Linux udev rules are not properly configured. Either check Linux lsusb and udev rules, run the install_drivers.sh script as shown here or check the XDS200 known issues.
    • The JTAG debugger failed to boot properly (XDS200 and XDS560v2). For XDS560v2, check the manufacturer's debug probe manual or the DTC_CONF page to see if it is in Safe Mode.
    • There is another user already connected to the JTAG debugger (XDS220 or XDS560v2 Ethernet-based Debug Probes). For XDS560v2, check the DTC_CONF page to learn how to find which host is using the probe.
    • The JTAG debugger is not powered (some variants of XDS560 and XDS560v2). Check the external power supply.
    • The USB cable has loose contacts or not connected at all. Replace the USB cable and retest.
    • The USB is connected via an incompatible USB HUB or port. Connect the USB cable directly to the host PC or to a different port.
    • The debug probe firmware is incompatible with the OS. This is mostly applicable to XDS110 and XDS200. To verify this you can check the steps shown in the Firmware update section for XDS110 and XDS200.

    The Test Connection button reports a different message, but it refers to the same problem:

        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'.