• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 80 subscribers
  • Views 1308 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.

Easy Install of INF generated by Descriptor tool

Chad Kidder
Intellectual 455 points

Other Parts Discussed in Thread: MSP430F5659, MSP430F5529

So I've got my project working and I am looking to hand it off to my client.  It would be really nice if the INF file generated by the USB Descriptor tool would allow right-click installation of the INF files.  Currently the device has to fail installation then one has to go in and manually update the driver.  I just want something simple I can tell my clients to do to get the driver installed.  Thanks for the help.

  • 0
    TI__Guru* 80621 points

    Hi Chad,

    There is a detailed discussion on installation of CDC interfaces on Windows in section 2.5 of the USB Examples Guide (included in the USB Developer's Package under MSP430_USB_Software/Documentation). This discusses the different installation options and considerations (like getting an INF file signed by Microsoft, etc).

    If you get your INF file signed then you could use Windows DPInst.exe program to have the driver get pre-installed (how this works is discussed all over the Windows developer forums). However, as the USB Examples Guide notes, the INF file generated by the descriptor tool is not already signed, because it contains the unique VID/PID you have set for your product, and any time this VID/PID is different Microsoft requires the driver to be re-signed (this is why we can't just generate or give you a "signed" driver, because you need to be able to put your own VID/PID for your product). It is still possible to install a driver that is not signed, and that is the method that's discussed further in section 2.5.3  - but this is the reason why the device driver is not just automatically installed and this little bit more involved process is required.

    As for the right-click install (yet another installation method), while this does not currently work with the type of driver INF file that we provide, it is a good feedback and something that we will look into as a possible feature request for future versions.

    For your present situation though, you either have the steps included in the USB Examples Guide, or you can submit to Microsoft to get a signed driver and include the DPInst.exe process into your installer to pre-install the driver (making later installation silent for the user), etc.

    Please note that this is only the case for CDC devices on Windows machines - CDC installs silently on Linux/Mac and other devices like HID or Mass Storage install silently on Windows as well.

    Regards,

    Katie

  • 0 in reply to Katie Pier
    Intellectual 455 points

    Thank you for the verbose reply.  I will appreciate it when the drivers support installation via right click.

  • 0 in reply to Katie Pier
    Genius 3745 points
    HI,

    i have some doubts regarding USB CDC class device. I am planning to use USB CDC device class on device which has in built USB (MSP430F5659). Is it possible to communicate with PC (Host) directly using CDC class on both host and device. i mean PC<- USB-> Device. If not please suggest which device class i can use to handle the communication. I am using first time USB in my project. Please guide me.

    Nitesh
  • 0 in reply to Nitesh Padiyar77
    Intellectual 455 points
    I've used it effectively with the CDC echo example program. That has all the code to get you going. You just need to hook into its main processing loop to act on the code you receive. The trickiest thing I've had to deal with is making sure that all interrupts fire when they need to. I had a project where I used the MSP430F5529 and I had a problem where the SPI interrupt would stop firing after a few characters. I finally just move the writes to a foreground loop and it was happy. You also need to make sure that when you put the device to sleep it is not too deep a sleep.

**Attention** This is a public forum