• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 2190 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.

Code Composer 6.0 MSP430: Error initializing emulator: No USB FET was found

Martin Sandberg
Prodigy 140 points
Other Parts Discussed in Thread: MSP-FET

I didn't see this problem reported for Code Composer 6.0. I'm running Windows 7 Professional Service Pack 1 32 bit.

I just re-installed Code Composer from the DVD and its still reporting "Error initializing emulator: No USB FET was found". This WAS working, but I had to change MSP-FET 430s and that seems to have killed it.

  • 0
    TI__Guru**** 173310 points

    Martin Sandberg said:
    This WAS working, but I had to change MSP-FET 430s and that seems to have killed it.

    Can you try going back to the MSP-FET you were using earlier and check if that still works? 

    Which target board are you connecting to? Is it a TI kit or a custom board? Did you check if the drivers are detected properly by looking at the Device Manager in your PC?  

    You might also want to try installing the latest version of CCS v6.1 and giving that a try. You can download and install from the below link. You can keep your existing installation as-is and just select a different directory to install 6.1 into.
    http://processors.wiki.ti.com/index.php/Download_CCS

  • 0 in reply to AartiG
    Prodigy 120 points
    I have the same problem with CCS V6 full license on Vista Business 32-bit. Yesterday (March 3rd) was working with a MSP430-FET and target board setup that has given reliable service for 8 months. Pressed F11 to connect to the target, then Avast antivirus flashed a message about a "suspected threat: file deleted." CCS closed down, but left the ccs.exe process running; the process had to be terminated via Task Manager.
    This shutdown now occurs every time I try to start a debug session. I can switch to the Debug perspective OK, but the shutdown occurs when attempting to connect to the target.
    I cannot find a log which tells me which file was deleted, nor is the file in the Recycle Bin.
    I have tried updating CCS but got a massive error report about trying to rename a file to the same name (won't work) and a large number of repository files which appear to be non-existent.
    There appears to be no repair facility for a CCSv6 installation.
    I tried re-running the installer, but again, no success.
    I have not yet tried uninstalling and reinstalling: I cannot afford the time. Surely it must be possible to simply reinstate the missing file.
    Anyone else had the same problem? Any slick solutions please?
  • 0 in reply to Raymond Wales
    Prodigy 120 points
    In my previous report, I forgot to mention that my computer was not connected to the internet: the modem was unplugged from the computer. This means that the deleted file had to be on my local machine, and was not an imported file.
    Success! I have a full backup of my hard disk on an external drive. By comparison I found that the deleted file was
    C:\ti\ccsv6\ccs_base\DebugServer\bin\tiofr_tial.dll
    I restored this file to its proper place and the entire system works as it should.
    Between the time of experiencing the problem and solving it, both Avast antivirus and Java have suffered updates.
    It is possible that the Avast definition database has been quietly updated so that it does not now see the .dll as offensive.
    I hope that this helps.
  • 0 in reply to AartiG
    Prodigy 140 points

    I found what the problem was. Code Composer 6 said it couldn't work with the firmware version that was on the MSP-FET. I allowed it to update the firmware and it said it succeeded. In reality, since it was running under parallels on a Macintosh OS X system, it failed, This is due to a timing problem that someone mentioned here. Something like the USB to COM port stack introduces timing uncertainties. This, of course, would be even worse under parallels. So, I had a brick on my hands.

    The solution was your MSP430Flasher! I ran it on a Macintosh system booted up with windows via Bootcamp.

    Execute the command MSP430Flasher.exe -s to force an update of the firmware of the currently attached FET, which does not need to be connected to a target device for this step.

    And Voilå I'm back in business.

    You really need to get your dev system running on Apple, We don't have a Windows machine in the shop

  • 0 in reply to Martin Sandberg
    TI__Guru**** 450411 points
    CCSv6 for Mac is currently in beta and will be released sometime 2H this year.
  • 0 in reply to Ki
    Prodigy 140 points
    And a hearty Thanx! for the Mac support!