• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 79 subscribers
  • Views 14282 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.

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

Dmitry Soukhov
Prodigy 40 points

Just received MSP-EXP430G2. After installation of  "Code Composer Studio  Version: 5.1.0.09000" (WinXP Pro, SP3) I can't run debug project.

It looks like CCS can't communicate to the board. Error message "Error initializing emulator: Could not find MSP-FET430UIF on specified COM port" received.

If no board connected - message:"Error initializing emulator: No USB FET was found"

No chip in socked - "Error initializing emulator: Could not find MSP-FET430UIF on specified COM port"

Another COM port in configuration - "Error initializing emulator: Tried to initialize USB FET number 2, but only found 1 USB FETs"

 

If pre-programmed processor is running (temperature demo) some odd symbols are sending to windows terminal programm. So UART and drivers seems to be OK.

 

What might be wrong?

 

  • 0
    Guru 227245 points

    There are many threads (even today) about this problem. Please use the search function.

    However, this may have several reasons.

    Often, a completely unrelated software hijacks the FET COM port. (because there's something answering on this port)
    Such as a smartphone sync software, or a gamers mouse driver.

  • 0 in reply to Jens-Michael Gross
    Genius 4925 points

    Funny things can happen with simple COM-ports, I'm still not sure why, but I managed to make Windows believe that the MSP sending some measurement data over a USB-Serial converter is a serial mouse.

    It was quite annoying as the mouse clicked and moved randomly over the screen - I had to delay the measurement long enough for the USB enumeration of the converter to complete...

  • 0 in reply to Jens-Michael Gross
    Prodigy 90 points

    There might be many posts relating to this topic, but none truly offers an answer to the problem.

  • 0 in reply to Jens-Michael Gross
    Prodigy 40 points

    I see. Actually I spent half a day looking for a solution.

    But eiter threads are with no solution at all or solution is related to CCS4 with fix like "...there was old drivers set..." Both not my case.

    Keep looking.

  • 0 in reply to Alexander Ventura
    Prodigy 40 points

    I can't belive that the only way is to throw avay CCS5 and install something else... I'm still hoping :)

  • 0 in reply to Alexander Ventura
    Genius 4925 points

    On a more serious note, this might be related to the new MSP430.DLLv3, they have updated the debug stack which needs an update for the FET devices, now I doubt that the launchpad comes with the new firmware needed to work with the new dll.

    In the announcement of the new dll I haven't read anything about the launchpad, maybe you could ask your question in that thread.

    You see this kind of problem is so dependent on your PCs setup that we can guess all day long what it might be - there is so much interference between components installed that it's nearly impossible to give a good explanation. It might be that you use a dongle and the driver for that blocks something, or you have some strange software running which tries to connect to COM ports or the antivirus software is blocking some actions of the CCS... In the other thread the mouse driver was the culprit - who would have thought of that?

  • 0 in reply to Bernhard Weller
    Prodigy 40 points

    OK. My case closed. I terminated "Olympus Digital Wave Player" watchdog agent and everything starts.

    If this does not work - I would have tried suggestions mentioned in http://e2e.ti.com/support/microcontrollers/msp43016-bit_ultra-low_power_mcus/f/166/p/148241/536577.aspx thread.

    It's pity such SW problems spoil the impression of TI products. 

**Attention** This is a public forum