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/TMS570LC4357: I can no longer flash code to the HDK for a debug session

Part Number: TMS570LC4357

Tool/software: Code Composer Studio

Hello,

I have been able to repeatedly compile and launch a debug session with the HDK over the past month.

Sometimes when the computer comes out of hibernation or low power standby, it has trouble connecting to the board.

If I disconnect power to the board, and disconnect and reconnect the USB cable, the connection is usually reestablished.

Sometimes I have needed to completely reboot the computer, and then connection is OK.

But now, the connection continuously fails. There is no method or procedure that causes a successful connection anymore.

Is there a means to reset the drivers for the jtag USB Debug Probe?

I have changed to a new HDK board, a new USB cable, and tried all the different available USB ports, and NOTHING is working anymore!

I go into the Project Properties panel, and check verify for the Texas Instruments XDS100V2 USB Debug Probe, and I get:

This error is generated by TI's USCIF driver or utilities. The value is '-150' (0xffffff6a). The title is 'SC_ERR_FTDI_FAIL'. The explanation is: One of the FTDI driver functions used during configuration returned a invalid status or an error.

Since this error is reported for different HDK hardware, different USB cables, and different USB ports, I primarily suspect it is due to a fault in a driver that needs updated.

Please advise on the best way to update or repair drivers for this functionality, please help provide a method to reliably enable connection for loading/starting a debug session on the HDK.

Thank You,

-Joseph 

  • Hi Joseph,

    You may try to uninstall the ftdi driver using the ftdi tool: CDM Uninstaller 1.4 - Windows Device Driver Uninstaller at www.ftdichip.com/.../Utilities.htm

    After that, you need to reinstall the driver from the CCS
  • The debugger was connecting for several days after I tried this Uninstaller.

    But now I am getting the same error again.

    I tried funning the CDM Uninstaller again, and the log report for the Uninstaller shows that the driver was not found.

    The system still won't connect when I start a debug session.

    What is the process to reinstall the driver from CCS?

    Thank You,

    -Joseph

  • Look at the security privileges. Sometimes OS updates can change those, or change what effect they have.
  • Hello Joseph,

    You can install the emulator driver from the CCS package or using the emulator package. Here is the link to download emulation SW package:

    processors.wiki.ti.com/.../XDS_Emulation_Software_Package
  • Hello QJ,
    I was able to download the emulation software package using the provided link.
    Are there instructions for how to install the drivers?
    Thank you,
    -Joseph
  • Hi Joseph,

    1. Exit all CCS instances before proceeding
    2. On Windows, right click on the downloaded file and select Run as Administrator
    3. Accept the license agreement
    4. For the destination folder use the full path up to ccsv7 directory (where ccs_base is located). 
    5. Select Typical installation
    6. Wait for the installation to complete and click Finish

  • Hello QJ,
    Thank you for the guidance, but it is still not connecting after emulator install process.
    Is there a way to reinstall the Windows Driver Packages:
    FTDI CDM Driver Package - Bus/D2XX Driver
    FTDI CDM Driver Package - VCP Driver
    are these at all related?
    The Error message I get is:

    This error is generated by TI's USCIF driver or utilities.

    The value is '-150' (0xffffff6a).
    The title is 'SC_ERR_FTDI_FAIL'.

    The explanation is:
    One of the FTDI driver functions used during
    configuration returned a invalid status or an error.

    [End]
  • One other clarifying question:
    The default install location is C:\TI, and there is a ccs_base folder there, and in the ccsv7 folder, there is also a ccs_base. So which folder should be used for the installation destination? The C:\TI, or C:\TI\ccsv7?
  • Hello QJ,
    Thank you for your assistance in addressing this issue. I still do not have a working connection.
    There is a notice at the bottom of CCS, and when I select items to update, I get an error notice that the updates could not be installed.
    An error occurred while collecting items to be installed
    session context was:(profile=epp.package.cpp, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
    No repository found containing: org.eclipse.update.feature,com.ti.c2000.support.win32,4.2.4.0
    No repository found containing: binary,com.ti.c2000.support.win32_root,4.2.4.0
    No repository found containing: org.eclipse.update.feature,com.ti.dsflash.win32,8.0.0.1213
    No repository found containing: binary,com.ti.dsflash.win32_root.win32.win32.x86,8.0.0.1213
    No repository found containing: org.eclipse.update.feature,com.ti.emulation.pack.win32,7.0.188.0
    No repository found containing: binary,com.ti.emulation.pack.win32_root.win32.win32.x86,7.0.188.0
    Is this expected?
    Thank You,
    -Joseph
  • Hi Joseph,

    It should be installed to c:\ti\ccsv7

    4. For the destination folder use the full path up to ccsv7 directory (where ccs_base is located).

    The new drivers will be installed to c:\ti\ccsv7\ccs_base\
  • OK,
    I completely UNINSTALLED Code Composer and reinstalled, then there was a notice that there were driver updates, so after loading the driver updates, the debug session launched, and I was able to connect and reprogram the HDK.
    I was able to complete several evaluation tests of the new software, and then I wanted to reconnect to the HDK and evaluate a specific portion of code through the debug function. However, I am getting the same error: I can't connect to the board due to same original FTDI driver fault!
    I was JUST able to reconnect and run a debug session an hour ago, now it won't reconnect! What is going on, and what is the corrective action that will permanently resolve this intermittent connection issue?!
    Kind Regards,
    -Joseph
  • I am not associated with TI.
    This sounds like the kind of problems that were OS version dependent some years.
    Sometimes solved with compatibility settings.
    Sometimes solved with changes to sleep timeout settings (USB port goes to sleep and the device plugged into it does not recover).