Free Software USB Packet Sniffer and Logic Analyzer. Download this Freeware USB Explorer and Protocol Analyser for Windows. Capture and Monitor USB Devices and Applications Data. Dfu-util windows free download. Dfu-util dfu-util is a host side implementation of the DFU 1.0 and DFU 1.1 specifications of the USB forum. Windows Apps for USB Drivers. Windows Apps for USB Drivers. Download Microsoft's Sidewinder Game Controller Software. Standard Enhanced PCI to USB Host Controller.

USB interface association descriptor (IAD) allows the device to group interfaces that belong to a function. This topic describes how a client driver can determine whether the device contains an IAD for a function.

The Universal Serial Bus Specification, revision 2.0, does not support grouping more than one interface of a composite device within a single function. However, the USB Device Working Group (DWG) created USB device classes that allow for functions with multiple interfaces, and the USB Implementor's Forum issued an Engineering Change Notification (ECN) that defines a mechanism for grouping interfaces.

The ECN specifies a USB descriptor, called the Interface Association Descriptor (IAD), that allows hardware manufacturers to define groupings of interfaces. The device classes that are most likely to use IADs include:

• USB Video Class Specification (Class Code - 0x0E)

• USB Audio Class Specification (Class Code - 0x01)

• USB Bluetooth Class Specification (Class Code - 0xE0)

Windows 7, Windows Server 2008, Windows Vista, Microsoft Windows Server 2003 Service Pack 1 (SP1), and Microsoft Windows XP Service Pack 2 (SP2) support IADs.

The following subsections describe information about how to use IADs.

How should a composite device alert the operating system that it has IADs in its firmware?

Manufacturers of composite devices typically assign a value of zero to the device class (bDeviceClass), subclass (bDeviceSubClass), and protocol (bDeviceProtocol) fields in the device descriptor, as specified by the Universal Serial Bus Specification. This allows the manufacturer to associate each individual interface with a different device class and protocol.

The USB-IF core team has devised a special class and protocol code set that notifies the operating system that one or more IADs are present in device firmware. A device's device descriptor must have the values that appear in the following table or else the operating system will not detect the device's IADs or group the device's interfaces properly.

These code values also alert versions of Windows that do not support IADs to install a special-purpose bus driver that correctly enumerates the device. Without these codes in the device descriptor, the system might fail to enumerate the device, or the device might not work properly.

A device can have more than one IAD. Each IAD must be located immediately before the interfaces in the interface group that the IAD describes.

The function class (bFunctionClass), subclass (bFunctionSubclassClass), and protocol (bFunctionProtocol) fields of the IAD must contain the values that are specified by the USB device class that describes the interfaces in the function.

The class and subclass fields of the IAD are not required to match the class and subclass fields of the interfaces in the interface collection that the IAD describes. However, Microsoft recommends that the first interface of the collection have class and subclass fields that match the class and subclass fields of the IAD. The following table indicates which fields should match.

The bFirstInterface field of the IAD indicates the number of the first interface in the function. The bInterfaceCount field of the IAD indicates how many interfaces are in the interface collection. Interfaces in an IAD interface collection must be contiguous (there can be no gaps in the list of interface numbers), and so a count with a first interface number is sufficient to specify all of the interfaces in the collection.

Accessing the contents of an IAD

Client drivers cannot access IAD descriptors directly. The IAD Engineering Change Notification (ECN) specifies that IADs must be included in the configuration information that devices return when they receive a request from host software for the configuration descriptor (GetDescriptor Configuration). Host software cannot retrieve IADs directly with a GetDescriptor request.

However, client drivers can query a USB device's parent driver for the device's hardware identifiers (IDs), and the device's hardware IDs contain embedded information about the fields of the IAD.

USB Interface Association Descriptor Example

The following illustrates a descriptor layout for a composite USB device. The example device has two functions:

Function 1: Video Class
This function is defined by an interface association descriptor (IAD) and contains two interfaces: interface zero (0) and interface one (1).

The system generates hardware and compatible identifiers (IDs) for the function, as described in Support for the Wireless Mobile Communication Device Class. After matching the appropriate INF file, the system loads the Video Class driver stack.

Function 2: Human Input Device
This function contains only one interface: interface two (2).

The system generates hardware and compatible IDs for the function, as described in Enumeration of Interface Collections on USB Composite Devices. After matching the appropriate INF file, the system loads the Human Input Device (HID) class driver.

The descriptor is as follows:

Device Descriptor:

Configuration Descriptor:

Alereon Wireless Usb Host Dfu Driver Download For Windows 10

Interface Association Descriptor:

Interface Descriptor (Video Control):

Alereon Wireless Usb Host Dfu Driver Download For Windows 8.1

Class Specific Descriptor(s):

Endpoint Descriptor(s):

Interface Descriptor (Video Streaming):

Class Specific Descriptor(s):

Endpoint Descriptor(s):

Interface Descriptor (Human Input Devices):

Class Specific Descriptor(s):

Endpoint Descriptor(s):

Alereon Wireless USB Host DFU Driver Download For Windows

Related topics