• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 196 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.

TMDXRM57LHDK: Cannot connect CCS

Koichiro Tashiro
Mastermind 22070 points

Part Number: TMDXRM57LHDK

Hi,

My customer is trying to connect TMDXRM57LHDK with CCS 10.3.1.
He got below error at Test Connection.

Ｅ_RPCENV_IO_ERROR(-6)No　connection:DTC_IO_Open::dtc_io Failed to open i/o connection(xds2xxu:0) An error occurred shile soft opening the controller.

What is the reason of the failure?
When the board is connected to PC with USB cable, it is recognized as "XDS100debuging probe".

Thanks and regards,
Koichiro Tashiro

  • 0
    TI__Guru**** 192196 points

    Hello Koichiro-san,

    Does your customer use the HDK build-in xds100v2 emulator or use an external xds200 emulator? If the build-in emulator is used, which emulator is selected in target configuration: xds100v2 or xds200?

  • 0 in reply to QJ Wang
    TI__Mastermind 22070 points

    Hi QJ,

    Customer uses the build-in xds100.

    Thanks and regards,
    Koichiro Tashiro

  • 0 in reply to Koichiro Tashiro
    TI__Guru**** 192196 points

    Please check the windows system device manager, when the xds100v2 is properly installed, the xds100 should look like the below image:

    If the xds100 doesn't show up in the windows device manager, it is likely that the xds100v2 was not programmed properly.

    1. You can run the utility <xds100serial.exe> to find out which VID/PID are programmed in the device. The utility is located at the directory:

    CCS_INSTALL_DIR\ccs1030\ccs\ccs_base\common\uscif\

    2. check USB cable or change the USB port the emulator is connected 

    3. Power cycle your target board (HDK)

    4. You may want to check the VID/PID EEPROM was programmed properly using FTDI tool: FT_PROG

    https://ftdichip.com/utilities/

    FT_PROG GUI-->Devices-->Scan and Parse: