|
||
| Products Download Events Support Videos | ||
Technical Support
On-Line Manuals
RL-ARM User's Guide (MDK v4)
RL-RTX
RL-FlashFS
RL-TCPnet
RL-CAN
RL-USB
RL-USB for USB Device Applications
RL-USB Device Library
RL-USB Device Features
RL-USB Device Software Stack
RL-USB Device Functions
RL-USB Device Source Files
RL-USB Device Configuration
Audio Device (ADC) Options
Communication Device (CDC) - ACM Options
Human Interface Device (HID) Options
Mass Storage Device (MSC) Options
Create USB Device Applications
Create ADC Applications
Create CDC ACM Applications
Create HID Applications
Create MSC Applications
Create Composite Applications
Test USB Device Applications
Compliance Tests
Test HID Client Application
RL-USB for USB Host Applications
RL-USB Host Library
RL-USB Host Features
RL-USB Host Software Stack
RL-USB Host Functions
RL-USB Host Source Files
RL-USB Host Configuration
Host Controller Driver Selection
Host Controller Driver Configuration
Host Class Driver Selection
Create USB Host Applications
Create USB Host HID Applications
HID_Kbd Example
Create USB Host MSC Applications
Create USB Host Class Driver
RL-USB Host Constants and Structures
Error constants
Speed constants
Transaction Packet Type constants
Transaction Error Type constants
USB Request Block structure (USBH_URB)
Endpoint structure (USBH_EP)
Driver Capabilites structure (USBH_HCI_CAP)
Device Class Instance structure (USBH_DCI)
Host Controller Instance structure (USBH_HCI)
Host Controller Driver structure (USBH_HCD)
USB Concepts
USB Transfer Rates
USB Network
Basic Communication Model
USB Protocol
Control Transfer
Interrupt Transfer
Isochronous Transfer
Bulk Transfer
Descriptors
Device Configuration
Device Descriptor
Configuration Descriptor
Interface Descriptor
Endpoint Descriptor
Device Qualifier Descriptor
Example Programs
Library Reference
Appendix
Device Qualifier Descriptor
A high-speed capable device that has different device information for full-speed and high-speed must also have a Device Qualifier Descriptor. For example, if the device is currently operating at full-speed, the Device Qualifier returns information about how it would operate at high-speed and vice-versa.
The fields for the vendor, product, device, manufacturer, and serial number are not included. This information is constant for a device regardless of the supported speeds.
If a full-speed only device receives a GetDescriptor() request for a device_qualifier, it must respond with a request error. Then, the host must not make a request for an other_speed_configuration descriptor.
| Offset | Field | Size | Value | Description |
|---|---|---|---|---|
| 0 | bLength | 1 | Number | Size of this descriptor in bytes. |
| 1 | bDescriptorType | 1 | Constant | Device Qualifier Type. |
| 2 | bcdUSB | 2 | BCD | USB Specification Release Number in Binary-Coded Decimal (i.e., 2.10 is 210H). This field identifies the release of the USB Specification with which the device and its descriptors are compliant. At least V2.00 is required to use this descriptor. |
| 4 | bDeviceClass | 1 | Class | Class code (assigned by the USB-IF). If this field is reset to zero, each interface within a configuration specifies its own class information and the various interfaces operate independently. If this field is set to a value between 1 and FEH, the device supports different class specifications on different interfaces and the interfaces may not operate independently. This value identifies the class definition used for the aggregate interfaces. If this field is set to FFH, the device class is vendor-specific. |
| 5 | bDeviceSubClass | 1 | SubClass | Subclass code (assigned by the USB-IF). These codes are qualified by the value of the bDeviceClass field. If the bDeviceClass field is reset to zero, this field must also be reset to zero. If the bDeviceClass field is not set to FFH, all values are reserved for assignment by the USB-IF. |
| 6 | bDeviceProtocol | 1 | Protocol | Protocol code (assigned by the USB-IF). These codes are
qualified by the value of the bDeviceClass and the
bDeviceSubClass fields. If a device supports class-specific
protocols on a device basis as opposed to an interface basis,
this code identifies the protocols that the device uses as
defined by the specification of the device class. If this field is reset to zero, the device does not use class-specific protocols on a device basis. However, it may use classspecific protocols on an interface basis. If this field is set to FFH, the device uses a vendor-specific protocol on a device basis. |
| 7 | bMaxPacketSize0 | 1 | Number | Maximum packet size for other speed. |
| 8 | bNumConfigurations | 1 | Number | Number of other-speed configurations. |
| 9 | bReserved | 1 | Zero | Reserved for future use, must be zero. |
ProductsDevelopment Tools |
Hardware & Collateral |
Downloads |
Support |
Contact |
 |
||||