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.

MSP430F5529: Installing USB Driver From Context Menu "Install" Selection or EXE

Part Number: MSP430F5529


I recently completed a design using the MSP430F5529 as a USB-to-Serial bridge, utilizing the built-in USB module. I used the MSP USB Descriptor Tool to generate my .inf file and, along with the example .inf files, I got it to behave as expected. I then went through the process of generating a .cat file and signing the software. That all works great, and I can install the driver on Windows 7 and 8 by going through the device manager. However, the process of installing a driver by navigating to the .inf file through the device manager is tedious and not something we want the customer to have to deal with. I would like to replace this process with one that only requires the customer to either right-click the .inf file and select "Install", or simply run an executable. Either one is acceptable, I do not necessarily need both options.

I noticed that when the MSP Descriptor Tool generates the .inf file, it does not include the DefaultInstall section. I presume this section is what is run when "Install" is selected from the right-click context menu. I have not been able to find a good example showing how to write this section to do what we need it to do. I have been through Microsoft documentation but it is all very generic and does not help much with the problem at hand.

How would one go about bypassing the driver installation through the device manager and instead run the installation from the .inf right-click context menu or from an executable (a batch file, for example)?

Thank you,
Isaiah Washburn

  • Hello Isaiah,

    I'm not sure this is something our USB Descriptor Tool can support. Let me speak with our USB experts to see if we have any additional information.
  • Hello,

    Maybe these articles might help with creating the batch file:

    Right clicking Inf file

    Install from command line

    Regards,

    Arthi

  • Hello Arthi,

    Unfortunately this does not help me much. The links you posted describe .inf files that can already be "installed" using the "Install" option in the right-click context menu. The inf files generated with the MSP USB Descriptor Tool do not have the necessary sections to make the "Install" option in the menu work. I am looking for guidance on how to modify the .inf file so that it can be installed using that method. Once that is done then writing a script will be a breeze.

    Thank you,

    Isaiah Washburn

  • Hi Isaiah,

    Maybe you can try copying the [DefaultInstall] section that is listed in the msp430._ti_signed.inf file found in one of the CDC examples.  Please do understand that the inf files in the CDC examples have been certified and signed so you will not be able to update those particular inf files for your needs but you should be able to follow the format listed in the .inf file to update your custom .inf file.

    Regards,

    Arthi

  • Hello again,

    As a matter of fact this was one of the first things I tried. I actually copied the entire msp430_ti_signed.inf file and replaced bits of it with our own manufacturer/product-specific data, VID/PID, etc. When I right-click the .inf file and choose "install" it asks me if I want to install the software, to which I reply yes. It acts like it installs the driver but the device still remains unrecognized in the device manager (The yellow warning triangle appears next to its name) and it is still located under "Other devices". For the record I am developing on Windows 7, but I have tested on Windows 8 and have the same issue.
  • Well, I am out of ideas then. Maybe the MS community might be able to help you.

    Regards,
    Arthi
  • Oh, by the way, maybe the reason you might be getting the yellow bang, could be that the VID/PID is already installed and now you are trying to install the same VID/PID but with a different .inf file content. You might need to either get a different PID or clean out the Windows register before experimenting with your .inf file.
  • Good morning, my apologies for the delay in response.

    Unfortunately removing the VID/PID entry from Windows did not seem to help. I used USBDeview to uninstall all instances of my VID/PID combination (there was only one, anyway) and started fresh, but unfortunately had the same problem. It looks like it installed, but the warning icon still appears in the device manager, even after a reboot.

    Is there anyone else who might have further suggestions?

    Thank you,
    Isaiah Washburn
  • Hello Isaiah,

    Unfortunately, I don't think we have any other suggestions for you on this. I am sorry we could not help you further.

**Attention** This is a public forum