Because of the Thanksgiving holiday in the U.S., TI E2E™ design support forum responses may be delayed from November 25 through December 2. Thank you for your patience.

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.

Error initializing emulator: Interface Communication error

Other Parts Discussed in Thread: MSP-TS430DA38

I went to work on a project using an MSP430 that I started a few months ago but fell by the wayside. When I went to launch my project (that worked previously) however I received the following error: "Error initializing emulator: Could not initialize device interface".

I did some googling and although questions were on much older versions of CCS (I was on 5.3) the consensus seemed to be to update. I updated through the Help>Check for Updates menu option. This resulted in a slightly different error message of "Error initializing emulator: Interface Communication error" but I still cannot launch my project. Then I opted to completely uninstall and reinstall but still receive the second error.

Some other details are that I am using a MSP430-FETUIF with a MSP-TS430DA38 Rev 1.3 test board. And my current exact CCS version is 5.5.0.00077

Quick checklist of things I have already tried (in the order I tried them)

  • Running CCS with the -clean parameter
  • Deleting the .metadata folder in my workspace and recreating the project.
  • Rebooting the computer
  • Closing/uninstalling any software that could be using COM ports
  • Disabling my anti-virus temporarily
  • Updating through "Help>Check for Updates"
  • Completely uninstalling and reinstalling.


I'm not sure what else to try at this point.

  • Hi Joseph

    here a few further things to help debug

    - have you verified you do indeed see the FET appear in your device list along with a virtual MSP com port?

    - have you tried a different USB port, removing any hubs?   I have found for me sometimes a particular port or going through a hub won't work

    - you can download a useful tool from www.elprotronic.com   it is free and has helped me many times verify and debug connection issues as well as manage the firmware version on the FET

    - did you upgrade ccs or install new?   The reason I ask is that we have seen numerous upgrade issues.    This might be part of your problem

    - verify on another pc if possible

    Please keep us informed.

    Best Regards,

    Lisa

  • I'm not sure how I can view my "device list". I cannot find any views in CCS that seem to match that description.

    Well I just tried another USB port (I am not using a hub) which gave me another error "Error initializing emulator: No USB FET was found"

    More pressing matters have arisen so I do not have time for it right this moment but I will try the tool at www.elprotronic.com  when I get a chance. (Just wanted to keep you informed as you asked)

    I originally tried upgrading but when that failed I completely uninstalled and reinstalled.

    I would try another PC but I do not have access to one that I can install new software on.

    Thanks

    Joseph

  • Hi Joseph,

    ok, look in your device manager.   Are you familiar with windows device manager?

    Anyhow, check a couple more things as you are able and please keep us informed. 

    Best Regards,
    Lisa 

  • Oh, now I feel silly for not thinking of that. I went and check it to discover that the FET device had an error stating "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged". I googled that and multiple results said to uninstall and reinstall the device via right clicking on it in Device Manager, selecting uninstall, then scanning for hardware changes. Once I did this it worked.

  • Hi Joseph,

    great, glad to hear you are past the issue and all the best with development.

    Best Regards,
    Lisa 

  • My experience: I was facing the same problem but mine one is solved by just restarting the computer.