• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 1726 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

HELP: CCSv6.2 can't connect EVMK2HX

hao yang95
Intellectual 500 points

I am just newbie here and have a simple question. When I connect EVMK2HX evaluation module to my PC via USB cable and set NewTargetConfiguration in CCSv6.2, the connection test fails and said:

================================================================

[Start: Texas Instruments XDS2xx USB Onboard Debug Probe_0]



Execute the command:



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



[Result]





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



/root/.ti/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 Onboard Debug Probe_0]

================================================================

I set the optiion in NewTargetConfiguration as below:



My computer has the OS of Ubuntu 14.04, installed CCSv6.2, Processor-SDK.

I keep Dip's setting as 0010 in EVM board.

However I could connect EVM in terminal window by command “picocom -b 115200 /dev/ttyUSB0”, so I think the USB cable and port works well.

Could any one help check how to solve this issue?

Really appreciate!!

  • 0 in reply to Ki
    Intellectual 500 points

    Ki-Soo, Thanks for reply!

    I 've checked probable reasons one by one at "processors.wiki.ti.com/.../Debugging_JTAG_Connectivity_Problems

    For this one:
        
        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.


    I've run install_driver.sh and the log is as follows:
        sudo ./install_drivers.sh
        Uninstalling /etc/udev/rules.d/71-ti-permissions.rules
        TI XDS100 installation completed successfully.  Some versions of Linux
        require a reboot in order for the driver to function properly.  For other
        versions restarting udev is sufficient.  Restarting udev now ...
        udev stop/waiting
        udev start/running, process 2552

    I've reboot OS and issue is still there. This log shows that XDS100 has installed, but not XDS200. Is this normal?
       

  • 0 in reply to hao yang95
    Guru 92251 points

    hao yang95 said:
    This log shows that XDS100 has installed, but not XDS200. Is this normal?

    Looking back at the output from running the install_driver.sh it is normal that XDS100 is explicitly reported, but the XDS200 isn't explicitly reported.

  • 0
    Guru 92251 points

    hao yang95 said:
    However I could connect EVM in terminal window by command “picocom -b 115200 /dev/ttyUSB0”, so I think the USB cable and port works well.

    Just to confirm, you are aware there there are multiple USB ports on the EVMK2H:

    a) The micro usb on the baseboard of the EVMK2H is for the serial ports of the SOC and MCU, and that usb enumerates as /dev/ttyUSBx devices.

    b) The micro usb on the plug-in XDS200 is for the XDS200 on-board debug probe, and that usb enumerates as /dev/ttyACMx devices.

    If you want to use the XDS200 on-board debug probe you need a USB cable plugged in to the XDS200 on-board debug probe.

  • 0 in reply to Chester Gillon
    Intellectual 500 points
    Chester,
    Thanks for your kindly clear response!
    I didn't know well about which USB on EVM shall be used before..
    Now I really understand! And the connection is OK! There are two reasons:
    1. I didn't plug in the correct port on EVM, before I use the USB port of the mother board instead of the XDS2xx on-board probe. This is really the basic mistake.
    2. I used USB3.0 instead of USB2.0, which I didn't notice the difference of 2.0 and 3.0.

    Finally,after I used the correct USB port on EVM and USB port on PC, it works!