Usb How To

How to Use WinUSB to Communicate with a USB Device
March 9, 2010
Abstract
Independent hardware vendors (IHVs) who manufacture USB devices must often provide a way for applications to access the device’s features. Historically, this has meant using the Windows® Driver Model (WDM) to implement a function driver for the device and installing the driver in the device stack above system-suppliedprotocol drivers. The Windows Driver Foundation (WDF) is now the preferred model for USB drivers. It provides IHVs with three options for providing access to a USB device:
Implementing a user-mode driver by using the WDF user-mode driver framework (UMDF).
Implementing a kernel-mode driver by using the WDF kernel-mode driver framework (KMDF).
Installing WinUsb.sys as the device’s function driverand providing an application that accesses the device by using the WinUSB API.

This white paper provides guidelines for when to use each option and includes a detailed walkthrough of how to install WinUsb.sys as a device’s function driver and use the WinUSB API to communicate with the device.
This information applies for the following operating systems:
Windows 7
Windows Server® 2008Windows Vista®
Windows XP
References and resources discussed here are listed at the end of this paper.
For the latest information, see:
http://www.microsoft.com/whdc/connect/usb/winusb_howto.mspx

Disclaimer: This is a preliminary document and may be changed substantially prior to final commercial release of the software described herein.

The information contained in this documentrepresents the current view of Microsoft Corporation on the issues discussed as of the date of publication. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information presented after the date of publication.

This White Paper is for informational purposes only.MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying,recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you anylicense to these patents, trademarks, copyrights, or other intellectual property.

Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, email address, logo, person, place or event is intended or should beinferred.

© 2010 Microsoft Corporation. All rights reserved.

Microsoft, MSDN, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Revision History
Date | Change |March 9, 2010 | Updated the INF sample in the section “How to Install WinUsb.sys as a Function Driver.” |
March 30, 2009 | Added additional information for communicating with endpoints. |
December 6, 2007 | Added a section on DFU to the WinUSB FAQ.Removed the note from Table 1 indicating that WinUSB does not support WinUSB selective suspend on Windows XP. |
August 30, 2007 | * Created |...