• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 78 subscribers
  • Views 1684 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.

MSP430 USB - vendor specific class

Tom Schultz
Expert 4010 points
Other Parts Discussed in Thread: MSP430F5502, TRF7970A

MSP430 Team,

I am posting this on behalf of my customer.

Our customer hopes to use the WinUSB functions on the PC applications end to interface to our MSP430F5502/TRF7970A product. They also hope to make the device class “Vendor Specific”. It appears that the MSP430 USB Developers Package only provides support for HIS, CDC, and MSC devices. Are you aware of what the implications are if we go down the path of making the product a “vendor Specific” class with the PC application using WinUSB? Any TI API available?

Please let me know what you think.

Thanks,

Tom

  • 0
    TI__Expert 4010 points

    Hello,

    Could someone respond to this request.

    Thanks,

    Tom

  • 0
    TI__Expert 8005 points

    Hello Tom,

    "Are you aware of what the implications are if we go down the path of making the product a “vendor Specific” class with the PC application using WinUSB? Any TI API available?"

    While we do provide the APIs out-of-box for HID, CDC & MSC, it is absolutely possible to customize and create a vendor specific class. All the documentation for the USB module as well as the source for our existing USB stack are available. However, beyond these default class APIs we do not have any additional abstraction layers for the USB.

    It is for sure a custom solution and a custom effort that is hard to judge in scope. It really depends on what vendor specific will mean in each case. Again, fully doable though.

    Keep in mind that the defined classes are provided in order to make development with MSP430 USB easy, requiring as little actual USB development as necessary on the part of the user. Any details as to what is driving the need for a custom class?

    Regards, Zack

**Attention** This is a public forum