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: Error initializing emulator: No USB FET was found

Other Parts Discussed in Thread: MSP430FR6989, MSP-FET

Tool/software: Code Composer Studio

Downloaded to latest CCS Ver 6.2.

CCS is no longer working due to error noted above.

I've searched forrm, but no single solution offered..  

All that supid question and dumb responses, showing incompetentece of TI support staff.

Did TI gave up on its microcontroller business?

  • We would like to assist you with this but you are going to have to provide more helpful information.

    You state that you downloaded the latest CCS, v6.2.  Are you sure that is what you downloaded?  CCSv6.2 is many years old.  CCSv9.2 is the latest.

    You stated that CCS is no longer working.  Was it working prior to downloading the new version?  If so what version were you on before?

    What host operating system are you running on?  Windows, Linux, MacOS?  This error message is common on Linux and MacOS when using a development board or debug probe that is not supported on those platforms.

    Which development board or FET are you attempting to use?  Does if look like either of these pictures?

    Regards,

    John

  • Yes, it’s the correct version. I’m using older version of CCS to avoid code size limitation while not having to pay $500+ for software. Sometimes, my code exceed the code size limit, and I don’t want be bothered with code size limitations every time I start a new project.

    On OS, I’m using Windows 10 Pro version.

    I’ve been using 3 variations or more of TI’s Launchpad; value line G2553, this FRAM version of 5989/6989 and Cortex M3/M4 type. All hardware from TI seems to suffer from this particular error message. This is third MSP430FR6989 hardware with same problem; only remedy I know is to replace the Launchpad with a new one, which is becoming extremely annoying.  In comparison, I have no issue whatsoever with one Arduino hardware for last 10+ years, yet all TI hardware have same issues.  I really think TI need to looking into hardware design of Launchpad, run some operating current beased MTBF analysis. 

  • Note current versions of Code Composer Studio do not have a code size limit or license fee.  That has been the case for a few years now.  You can download the latest verison of Code Composer Studio (9.2) and install it here: http://software-dl.ti.com/ccs/esd/documents/ccs_downloads.html

    However that is not likely to help with the "No USB FET found" error.  That happens when Code Composer Studio is not able to detect the MSP430 development board.  That message would not occur with a Cortex M3/M4 board as it would not have an onboard MSP-FET.

    I will have to move this thread over to the MSP430 team to help you further.  It certainly seems like your boards are getting damaged.  Why that is happening I can't help much with.  I have dozens of MSP430 LaunchPads and eZ430 kits, a number of them over a decade old and I do not run into this on Windows.  I see it on Linux and MacOS when an eZ430 or similar kit is used that is not supported on that platform.

    Regards,

    John

  • John, I deeply appreciate your time in this matter.

    I re-install CCS 6.2, and the CCS software required that I upload new a new firmware on MSP430FR6989 before I load the program to a LaunchPad. This fixes the NO USB FET found error on one unit, but didn’t do much for the other two 6989 units.  Other units must have damaged USB connectivity in hardware as you suggested.

    As for Cortex Launchpad, it doesn’t specifically say NO USB FET found error, but error message read “error connecting to the target,” that I ‘m assuming similar issue with on-board USB emulator.

    I didn’t know that current version of CCS is now royalty free; I am excited to use version 9.2, since I know there are severe bugs in 6.2. Thank you for informing me of TI decision to remove royalty requirement of its software.