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.

MSP-FET not recognized by Windows

Other Parts Discussed in Thread: MSP-FET

Hi,


I do have the same problem as described in "MSP-FET (Last model, the black one) not recognized by Windows 7 x64", except that I have a x32 system. Unfortunately, I don't understand exactly which file Inigo Figuero copied as mentioned in his last post.

(Quote: "In other forum someone solved a similar problem installing manually the drivers for a USB Composite device.")

Could you please clarify, or give me link to the respective forum thread?

Regards

Johannes

  • Hi Johannes,

    It seems like was referring to the usb.inf file in his last post (e2e.ti.com/.../1533986). He said that he checked the C:\Windows\inf directory and did not see that file in there. This file is also located in several other areas in the Windows file system, so you can copy it from another location to the inf directory if it's missing there.

    Regards,
    Akash Patel

  • Hi Akash,

    thanks for your quick reaction.
    I checked my system: The usb.inf file is present in the c:\windows\inf directory. Still, upon plugging in the MSP-FET, no new device is displayed by the device manager, and no installation process is started.

    Any other ideas?

    Regards
    Johannes
  • Hi Johannes,

    Have you tried using the MSP-FET on any other USB port and/or computer? Also, do you have access to another MSP-FET? If so, do you have similar issues with it? 

    Also could you try reinstalling the drivers for the MSP-FET?
    Please connect the MSP-FET to the USB port and then proceed to uninstall the drivers. Once you have done that please disconnect the MSP-FET and try reinstalling the drivers from here: http://www.ti.com/tool/mspds and then plug the MSP-FET back in to see if it works.

    Regards,

    Akash Patel

  • Hi Akash,

    together with your FAE colleague Robert Finger I did the following experiments:

    Different computer (Windows 7, but 64 bit system, I would call it #2 here): MSP-FET is recognized and listed as "unknown device", i. e. driver installation is initiated by windows. My conclusion: The MSP-FET hardware is most likely not defective. I did not do a driver installation on that machine, because I do not want to install Code Composer on it.

    On the original computer (#1), Windows 7, 32 bit, I have Code Composer 6.1.1 installed, and I used it there together with a LaunchPad. The LaunchPad is recognized and the respective driver is installed correctly. My conclusion: The USB port is ok.

    On #1, I already installed the low level USB driver from http://www.ti.com/tool/mspds manually. With no effect. I did not de-install the driver, because there was none (because the USB device was not listed).

    I'm running out of ideas. Maybe order a second MSP-FET and hope that thing work better?

    Regards

    Johannes

  • Hi Johannes,

    I reached out to Robert Finger as well as another colleague to see if we can get more information on the issue and potential remedies. I hope to get back to you soon regarding the issue, however, due to the Easter holiday it may take a few extra days.

    Regards,
    Akash Patel
  • Hi Johannes,

    Sorry for the delayed response. I was wondering if you were able to make any progress on the issue. Can you open Device Manager before connecting the MSP-FET and then connect the MSP-FET and see if the window refreshes? If it is, that means it is detecting the USB connection. Does it show in other devices or unknown devices?

    Regards,
    Akash Patel
  • Hi Akash,


    I had a visit from Robert Finger last friday, and wie managed to get things running. It seems the problems came from the USB cable. I hope that is really the final reason, and I'll keep wathing it. Currently, I did not do any further actions sith the debugger. Fingers crossed ...

    Johannes

  • Hi Johannes,

    Thanks for the update and letting us know what the issue was.

    Regards,
    Akash Patel

**Attention** This is a public forum