• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 31 subscribers
  • Views 1139 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.

TM4C1294NCPDT: Windows driver for USB Bulk device

Kevin Bui
Prodigy 30 points
Part Number: TM4C1294NCPDT

Hi,

We are developing a USB module with the uC TM4C1294NCPDT.

We would like to develop a USB Windows driver to communicate with this module via USB Bulk device implemented in firmware (with TI SDK).

Is there any sample code for the Windows driver we can start with?

Or using the USB bulk driver provided with TI SDK is good enough for data communication (we will have many custom functions)?

Thanks and Best Regards,

Kevin

  • 0
    TI__Guru**** 183066 points
    Hi Kevin,

    We don't have the vendor-specific Windows drivers for enumerating USB bulk device. There is a TivaWare usb_dev_bulk example. What this example provides is a Windows INF file that instructs the Windows to install the correct drivers to use and what information to store in the registry.
  • 0 in reply to Charles Tsai
    Prodigy 30 points

    Hi Charles,

    Thank you very much for your response!

    My understanding from your answer:

    • TI only provides usb_dev_bulk.inf as a generic USB bulk driver allowing user mode applications to access the USB device without the need for a vendor-specific kernel mode driver.

    We will try this approach for development, but I also would like to know if a vendor-specific kernel mode driver is really needed, where should we start with?

    Thanks,

    Best Regards,

    Kevin

  • 0 in reply to Kevin Bui
    Guru 117855 points

    Kevin Bui said:
    I also would like to know if a vendor-specific kernel mode driver is really needed, where should we start?

    Might your, 'Casting of a far broader 'Investigatory Net' - provide a (superior) start?

    Had you considered:

    • commercially introduced (and available) products - which may nicely 'overlap' your requirement.    (You (may) not (properly/legally) employ these - yet they are sure to (well) illustrate what CAN be achieved!)
    • other (similar) ARM vendors.    Each vendor (usually) enjoys an 'area of specialization.'    The fact that this vendor has (yet) to,  'Produce to your Requirement' - may not 'prove the case'  at (similar) others!
    • USB 'is' complex - unless 'binding requirements'  dictate your exclusive use of, 'USB Bulk Driver/Device' - you may do well to deploy an (easier developed) USB mode/format.

    Often - the best 'direction' for your product/project - flows from your 'USERS!'    

    Reaching market 'early' - so that such (critically valuable) 'user-feedback'  may be (more quickly) absorbed - suggests that 'early/easier USB introduction' may prove, 'Much to your advantage...'

  • 0 in reply to Kevin Bui
    TI__Guru**** 183066 points
    Hi Kevin,
    The INF file supplied with the generic usb_dev_bulk example specifies the WinUSB driver. The WinWSB is a generic Windows driver. The driver supports control, bulk and interrupt transfer. The usb_dev_bulk example demonstrates the bulk transfer which can be handled by the generic WinUSB driver on the PC side. Depending on your application, the generic WinUSB driver may be sufficient for you.
  • 0 in reply to Charles Tsai
    Prodigy 30 points
    Hi Charles,

    Got it. Thank you very much for your support :)

    Best Regards,
    Kevin