• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 78 subscribers
  • Views 1542 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.

MSP430: Error initializing emulator: Could not find MSP-FET430UIF on specified COM port

Jonathan Kim
Prodigy 30 points
Other Parts Discussed in Thread: MSP430G2553

I have looked into trying to get rid of non-essential processes solution that many have said worked.
Unfortunately, either I haven't found the right process or something else is wrong because I continue to get this message.

My LaunchPad has been working perfectly for a while using CCSv6 and then a few days ago it just stopped working.

At first I get this error.

Note* I do not use a MSP-FET430UIF. I use the LaunchPad that comes straight from the box.

If I press update I get the following error:

--> MSP430: Error: Could not initialize device interface

If I try to debug again I get the following error.

-->MSP430: Error initializing emulator: Could not find MSP-FET430UIF on specified COM port


This is what I see on my device manager

I use Code Composer and the MSP430 a lot so fixing this problem is crucial to me. If there is any solution please let me know. I've looked online and could not find any that worked.

Thanks.

  • 0
    Guru 227245 points
    i can't provide any other help that what was already posted in numerous other threads regarding the very same topic. Please use the forum search.
    search phrases like "Error initializing emulator" or such will surely reveal a lot of hits.
  • 0 in reply to Jens-Michael Gross
    Prodigy 30 points
    I've looked through all the posts. None seemed to be my solution.

    I have found that although my msp430g2553 chip was in good condition, the launchpad itself was somehow broken. I switched the launchpad with a new one using the same chip and it worked perfectly.

    Do you happen to know what may cause the launchpad to malfunction?
  • 0 in reply to Jonathan Kim
    Guru 227245 points
    Well, a phisical defect is of course a possible cause for a failing communication :)
    Anything that can damage a circuit can damage a LaunchPad. First there are mechanical problems. The micro USB plug can be quite strong holding the cable - and the mount on the PCB tends to be the weaker part after some time. The cable itself is sometimes a problem. One should think that a simple USB 2.0 cable, even if a cheap one, can't be the cause, but it sometimes is.
    Then you shouldn't forget that an USB connection means being connected to the PC power domain. If you have the LaunchPad connected to anything else, e.g. a separate power supply, there can be a GND potential difference that may fry the ciruitry. Even if the currents are low enough that a human wouldn't notice it.
    ESD can cause it to get damaged. People think that grounding oneself will prevent ESD problems, but this isn't the case. Besides the mentioned potential differences, it may be that the device is charged and you discharge it when you touch it. This is ESD too. Just opposite polarity.
    And finally, of course it can be a production failure. Bad soldering (that maybe take place after some small shock or PCB bending, so the device seems to be okay on factory testing).
  • 0 in reply to Jens-Michael Gross
    Prodigy 30 points

    I see.

    Thank you for your quick replies!

**Attention** This is a public forum