WinUSB
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
| Developer(s) | Microsoft |
|---|---|
| Operating system | Microsoft Windows |
| Type | Device driver |
| Website | msdn |
WinUSB is a generic USB driver provided by Microsoft, for their operating systems starting with Windows Vista but which is also available for Windows XP. It is aimed at simple devices that are accessed by only one application at a time (for example instruments like weather stations, devices that only need a diagnostic connection or for firmware upgrades). It enables the application to directly access the device through a simple software library. The library provides access to the pipes of the device. WinUSB exposes a client API that enables developers to work with USB devices from user-mode. Starting with Windows 7, USB MTP devices use WinUSB instead of the kernel mode filter driver.
Advantages and disadvantages
[edit]Advantages
[edit]- Does not require the knowledge to write a driver
- Speeds up development
Disadvantages
[edit]- Only one application can access the device at a time
- Does not support isochronous transfers prior to Windows 8.1
- Does not support USB Reset (as requested by DFU protocol for example)
- On other operating systems, the device still needs a custom driver
WCID
[edit]A WCID device, where WCID stands for "Windows Compatible ID", is a USB device that provides extra information to a Windows system, in order to facilitate automated driver installation and, in most circumstances, allow immediate access. WCID allows a device to be used by a Windows application almost as soon as it is plugged in, as opposed to the usual scenario where a USB device that is neither HID nor Mass Storage requires end-users to perform a manual driver installation. As such, WCID can bring the 'Plug-and-Play' functionality of HID and Mass Storage to any USB device (that sports a WCID aware firmware). WCID is an extension of the WinUSB Device functionality.[1]
Other solutions
[edit]One solution is the use of a predefined USB device class. Operating systems provide built-in drivers for some of them. The most widely used device class for embedded devices is the USB communications device class (CDC). A CDC device can appear as a virtual serial port to simplify the use of a new device for older applications.
Another solution is UsbDk. UsbDk supports all device types including isochronous and provides simpler way for device access acquisition that does not involve INF files creation and installation. UsbDk is open source, community supported and works on all Windows versions starting from Windows XP.
If the previous solutions are inappropriate, one can write a custom driver. For newer versions of Microsoft Windows, it can be done using the Windows Driver Foundation.
References
[edit]- ^ "pbatard/libwdi". GitHub. Retrieved 2020-05-14.
- "How to Use WinUSB to Communicate with a USB Device". Microsoft. 2007-12-05. Archived from the original on August 28, 2008. Retrieved 2008-07-09.
- "WinUSB". Microsoft Developer Network. Retrieved 2010-07-07.
- "USB 2.0 Specification". USB Implementers Forum, Inc. 2007-03-15. Retrieved 2007-03-27. The newest version can be found at USB.org
- As of this edit, this article uses content from "WCID Devices", authored by Pete Batard (pbatard), Patrick Stewart (patstew), Chih-Wei, and Manuel Odendahl (wesen), which is licensed in a way that permits reuse under the Creative Commons Attribution-ShareAlike 4.0 International License, but not under the GFDL. All relevant terms must be followed.
