• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 80 subscribers
  • Views 543 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Launchpad USB driver conflicts with MSP430-FET430UIF driver?

MikeH
Guru 15580 points


I recently started using the Launchpad with CCSv5.2 However, when I attempt to enter a debug state I get an error saying "Error connecting to the target: Unknown device" or " Error Initializing emulator:  Could not find MSP-FET430UIF on specified Com Port.".....as many others have, judging by the number of posts on this issue.

It appears that there is a USB driver conflict between my MSP-FET430UIF and the Launchpad USB driver. If I uninstall the  MSP-FET430UIF USB driver and restart my PC, the Launchpad works fine. However with the  MSP-FET430UIF USB drivers installed, trying to launch a Launchpad debug sessions always results in one of the two error messages above.

I would be interested in hearing from a TI EMPLOYEE on a confirmation of this issue.


  • 0
    Guru 15580 points

    Can I get some feedback from TI on this? It has become a recurring issue that causes a lot of wasted time de-installing and rebooting my machine. It is easily repeatable and I can provide any details needed for someone at TI to confirm the issue.

    Why is the debugger looking for the MSP-FET430UIF instead of the launchpad? I have de-installed the MSP-FET430UIF from my machine.

  • 0 in reply to MikeH
    Guru 25210 points

    MikeH said:
    It has become a recurring issue that causes a lot of wasted time de-installing and rebooting my machine.

    Realize that I'm not TI, but rather than removing the driver, can you just go in and disable it in the hardware profiles section of Device Manager? Might save you a little bit of time.

  • 0 in reply to Brian Boorman
    Guru 15580 points

    Brian,

    Thanks for the suggestion, but yes, I have tried that. The only thing that seems to work consistently is a re-boot.

**Attention** This is a public forum