• State Resolved
  • Locked Locked
  • Replies 12 replies
  • Answers 1 answer
  • Subscribers 81 subscribers
  • Views 1190 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.

CCS/MSP430F5508: Driver signing when using MSP430 USB module

Isaiah Washburn
Intellectual 310 points
Part Number: MSP430F5508
Other Parts Discussed in Thread: MSP-EXP430F5529LP

Tool/software: Code Composer Studio

I am currently in the process of developing a CDC product using the MSP430F5508. My development is being done on the MSP-EXP430F5529LP experimenter's board, which is based around the 'F5529. Once the product development is finished we will need to be able to release it to our customers. We are considering licensing a PID from TI, using TI VID 0x2047, since we do not generally manufacture USB devices. We expect to only sell about 100 of these products per year, so it is not worth it for us to acquire or license our own VID.

Most of the firmware development is complete and I am at the point of testing the device on different machines. I generated the descriptors and INF files using the MSP Descriptor Tool, but the issue I have now is the fact that the driver is unsigned. From what I have read it seems that getting a driver signed by Microsoft is a fairly complicated and lengthy process which is impractical for our purposes. I would like to know if there is a way to obtain a signed driver from TI when we lease our PID which does not require re-signing? What changes constitute a "Custom Driver" that requires it to be re-signed by Microsoft?

Thank you.

  • 0
    TI__Mastermind 26420 points

    Hey Isaiah,

    I think your questions can mostly be awnsered in this thread:  

    It appears that you have 2 options if using the TI VID.  

    1. Use the TI PID and recieve a signed license
    2. Use the descriptor tool and custom PID, but receive unsigned license.  

    To have a customer PID and signed license, you will have to go through the Microsoft registration process that you outlined.  

    Thanks,

    JD

  • 0 in reply to JD Crutchfield
    Intellectual 310 points

    Thank you JD,

    From what you have said it sounds like changing the PID is what causes the driver to become unsigned. If I obtain a PID from TI along with a signed license, am I able to still change the strings displayed to the customer (perhaps by using the descriptor tool), or must I use it as-supplied by TI?

    EDIT: Further reading of the linked thread uncovered this:

    "The .cat file and the .inf file go hand in hand.  So if you change the VID/PID in .inf file the driver installation will fail.  If you change the name in the .inf file, then you will get the warning.  The signed driver is for Texas Instruments and it will say so when a user installs the driver.  If you want a signed driver that lists the name of your company then you will have to go through certfication of your product and selected VID/PID (not TI's VID/PID that is listed in .inf file) with Microsoft. "

    So I believe that answers my question. Whatever we receive from TI must remain untouched in order to retain the certificate.

  • 0 in reply to Isaiah Washburn
    TI__Mastermind 26420 points

    Hey Isaiah,

    That is correct. Arthi, in the other thread is our in house USB expert, so she is the authority on this topic.

    Regards,
    JD

  • 0 in reply to JD Crutchfield
    Intellectual 310 points
    I have a follow-up question. I have acquired a PID by using the following link:

    software-dl-1.ti.com/.../vidtracker.html

    Now that I have the PID (under TI's VID), how to I acquire the .inf and .cat files? Do I still use the descriptor tool provided by TI, as long as I enter my assigned PID? Perhaps I misunderstood but I thought using the descriptor tool automatically meant no signed license.

    Thank you,
    Isaiah Washburn
  • 0 in reply to Isaiah Washburn
    Guru 33653 points

    BTW, your CDC device will be enumerated on Linux / OS X and Win 10 automatically, without asking for any drivers / inf / cat files. Inf file is only needed in older Win versions, 

  • 0 in reply to zrno soli
    Intellectual 310 points
    Thanks zrno. I'm still unclear as to how to acquire a signed driver though, which if I understand correctly, requires the .cat file.
  • 0
    Intellectual 310 points

    Part Number: MSP430F5508

    Tool/software: Code Composer Studio

    I have a follow-up question to my post here: e2e.ti.com/.../2791687. I figured I would copy this question into its own follow-up thread.

    I have acquired a PID from TI by using the following link:

    software-dl-1.ti.com/.../vidtracker.html

    Now that I have the PID (under TI's VID), how to I acquire the .inf and .cat files? Do I still use the descriptor tool provided by TI, as long as I enter my assigned PID? Perhaps I misunderstood but I thought using the descriptor tool automatically meant no signed driver, which is really what I am looking for at this particular point in time.

    Thank you,
    Isaiah Washburn

  • 0
    Guru 243110 points

    The descriptor tool creates only the device firmware and the (unsigned) .inf file.

    The matching .cat file must be created by going through certification with Microsoft.

  • 0 in reply to Clemens Ladisch
    Intellectual 310 points

    According to this answer in my original thread:

    "It appears that you have 2 options if using the TI VID.  

    1. Use the TI PID and recieve a signed license
    2. Use the descriptor tool and custom PID, but receive unsigned license. "

    Option 1 is the choice I took, and I acquired a PID from TI. My understanding based on my last question was that if I use TI's shared VID and their provided PID, I would receive a signed license from TI. Is this not the case?

    Thank you,
    Isaiah Washburn

  • 0 in reply to Isaiah Washburn
    TI__Guru 56685 points
    Hello Isaiah,

    I've merged your newest thread with this one as the two topics seem to be the same. For further discussion on this topic, please keep to this thread.
  • 0 in reply to Isaiah Washburn
    Guru 243110 points

    "TI PID" means one of the PIDs that TI used for its own CDC firmware (in the 03xx range), and that is mentioned in TI's original .inf file, and that TI's original .cat file was created for.

    Microsoft does not certify devices that do not (yet) exist.

    When you got a PID assigned by TI, then did not use option 1 but option 2.

  • 0 in reply to Clemens Ladisch
    TI__Guru 56685 points
    Hello Isaiah,

    I got some clarification form our USB experts on this.

    A user needs to get a certificate from Microsoft and follow their procedure for getting one. The PIDs that are available from TI are not signed and they are there for users to experiment with while developing their product. If they want to release their product with the TI provided VID/PID then the end user will get information displayed that it is an un-signed driver and if the user will give permission to install the driver.

    Section 2.5.2 and 2.6 of the Examples_Guide_MSP430_USB in the MSP430 USB Developer's Pack (www.ti.com/.../MSP430USBDEVPACK) talks more about INF signing and the PIDs available for developers.

**Attention** This is a public forum