USB设备类型代码（class类型）

Base Class E0h (Wireless Controller)

This base class is defined for devices that are Wireless controllers. Values not shown in the table below are reserved. These class codes are to be used in Interface Descriptors, with the exception of the Bluetooth class code which can also be used in a Device Descriptor.


Base Class
SubClass
Protocol
Meaning

E0h
01h
01h
Bluetooth Programming Interface.  Get specific information from the Bluetooth SIG.

02h
UWB Radio Control Interface.  Definition for this is found in the Wireless USB Specification in Chapter 8.

03h
Remote NDIS.  Information can be found at: http://www.microsoft.com/windowsmobile/mobileoperators/default.mspx

02h
01h
Host Wire Adapter Control/Data interface.  Definition can be found in the Wireless USB Specification in Chapter 8.

02h
Device Wire Adapter Control/Data interface.  Definition can be found in the Wireless USB Specification in Chapter 8.

03h
Device Wire Adapter Isochronous interface.  Definition can be found in the Wireless USB Specification in Chapter 8.

Base Class EFh (Miscellaneous)

This base class is defined for miscellaneous device definitions. Values not shown in the table below are reserved.  The use of these class codes (Device or Interface descriptor) are specifically annotated in each entry below.


Base Class
SubClass
Protocol
Meaning

EFh
01h
01h
Active Sync device.  This class code can be used in either Device or Interface Descriptors.  Contact Microsoft for more information on this class.

02h
Palm Sync.  This class code can be used in either Device or Interface Descriptors.

02h
01h
Interface Association Descriptor.  The usage of this class code triple is defined in the Interface Association Descriptor ECN that is provided on www.usb.org.  This class code may only be used in Device Descriptors.

02h
Wire Adapter Multifunction Peripheral programming interface. Definition can be found in the Wireless USB Specification in Chapter 8.  This class code may only be used in Device Descriptors

03h
01h
Cable Based Association Framework.  This is defined in the Association Model addendum to the Wireless USB specification.  This class code may only be used in Interface Descriptors.

Base Class FEh (Application Specific)

This base class is defined for devices that conform to several class specifications found on the USB-IF website.  That specification defines the usable set of SubClass and Protocol values.  Values outside of that defined spec are reserved.  These class codes can only be used in Interface Descriptors.


Base Class
SubClass
Protocol
Meaning

FEh
01h
01h
Device Firmware Upgrade.  Device class definition provided on www.usb.org.

02h
00h
IRDA Bridge device.  Device class definition provided on www.usb.org.

03h
00h
USB Test and Measurement Device.  Definition provided in the USB Test and Measurement Class spec found on www.usb.org.

01h
USB Test and Measurement Device conforming to the USBTMC USB488 Subclass Specification found on www.usb.org.

Base Class FFh (Vendor Specific)

This base class is defined for vendors to use as they please.  These class codes can be used in both Device and Interface Descriptors.


Base Class
SubClass
Protocol
Meaning

FFh
xxh
xxh
Vendor specific
时间： 2024-10-07 20:20:54

USB设备类型代码（class类型）的相关文章

USB Class Codes usb设备类型代码

Defined 1.0 Class Codes USB Class Codes                     March 2, 2006 USB defines class code information that is used to identify a device’s functionality and to nominally load a device driver based on that functionality. The information is conta

C# 动态添加类、动态添加类型、代码添加类型

原文:C# 动态添加类.动态添加类型.代码添加类型 引用控件: DLL下载地址:http://pan.baidu.com/s/1nv2GUWL public class TypeCreator { public static Type Creator(string ClassName, int PropertiesCount) { IDictionary<string, Type> Properties = new Dictionary<string, Type>(); Type

.NET(C#)中不同级别的安全透明代码对类型的影响

测试代码将测试一个方法和类默认在全部信任权限下和部分信任权限下的代码类型. 上面说的默认就是指未加入其他安全透明类型的特性. 代码类型可以是: 透明代码(Transparent Code) 关键代码(Critical Code) 可靠关键代码(Safe-critical Code) 测试这三项用到Type类和MethodInfo类中的IsSecurityTransparent,IsSecurityCritical和IsSecuritySafeCritical.注意这些属性不是从它们的共同基类Me

USB信号是什么类型的？ 为什么在D+，D-处要接上拉下拉电阻呢，具体阻值要如何计算

USB协议要求的,1.5K上拉在D+时表示是全速设备,在D-表示不是全速设备有些方案里面(比如PNX5230)推荐D+/D-接下拉1M的电阻是为了提高数据传输稳定性的 ①  usb有主从设备之分,主设备有:pc, 现在市面上的那些插u-disk即可播放mp3的“mp3”之类的,usb 信号是差分信号,信号线为D+, D-,. 在usb host 端, D+,D- 各接一个15kohm 的下拉电阻, 而在usb device端,这时就有高速低速设备的区别了.usb1.0, 1.1,2.0协议中都有

sqlserver数据库表生成C#代码实体类型方法

declare @TableName sysname = 'T_CRM_Customer'declare @Result varchar(max) = '/// <summary>/// ' + @TableName + ' /// </summary>public class ' + @TableName + '{' select @Result = @Result + ' /// <summary> /// ' + CONVERT(NVARCHAR(500), IS

USB描述符【转载】

USB描述符 USB描述符信息存储在USB设备中,在枚举过程中,USB主机会向USB设备发送GetDescriptor请求,USB设备在收到这个请求之后,会将USB描述符信息返回给USB主机,USB主机分析返回来的数据,判断出该设备是哪一种USB设备,建立相应的数据链接通道.那么USB描述符信息到底是一个什么样的数据呢,USB协议中有详细描述. 通用的USB描述符信息包括设备描述符.配置描述符.接口描述符和端点描述符,具体不同的USB设备还包括其它类型的描述符,例如,USB鼠标.键盘还包括HID

[国嵌攻略][162][USB协议分析]

USB设备逻辑结构 在USB设备的逻辑组织中,包含设备.配置.接口和端点4个层次.设备通常有一个或多个配置,配置通常有一个或多个接口,接口通常有零个或多个端点. USB设备描述符 当我们把USB设备(例如USB鼠标)插到我们的PC时,主机能够自动识别出我们的USB设备类型.在每一个USB设备内部,包含了固定格式的数据,通过这些数据,USB主机就可以获取USB设备的类型.生产厂商等信息.这些固定格式的数据,我们称之为USB描述符.标准设备有5种USB描述符:设备描述符.配置描述符.接口描述符.端点

CentOS 7.x 安装教程、硬盘分区、LVM、网络配置、软件源配置、制作USB Disk、U盘安装、网络安装

目录 一．准备安装CentOS 7 1.1CentOS简介 1.1.1介绍CentOS 7 1.1.2官方网站与文档 1.1.3CentOS软件包管理 1.1.4CentOS的正式发音 1.2获得CentOS发行版 1.2.1从镜像站点上下载ISO的镜像文件 1.2.2将ISO镜像文件制作成CD/DVD 1.2.3将ISO镜像文件制作成USB Live 1.3收集硬件信息 1.4硬盘分区方案 1.4.120GB硬盘以及1GB RAM 1.4.280GB硬盘以及1GB RAM 二．安装CentOS

【驱动】USB驱动&#183;入门【转】

转自:http://www.cnblogs.com/lcw/p/3159371.html Preface USB是目前最流行的系统总线之一.随着计算机周围硬件的不断扩展,各种设备使用不同的总线接口,导致计算机外部总线种类繁多,管理困难.USB总线正是因此而诞生的. USB总线提供了所有外部设备的统一连接方式,并且支持热插拔,方便了厂商开发设备和用户使用设备. USB遵循原则 USB的设计目标是对现有的PC机体系进行扩充,但是目前不仅是PC机,许多的嵌入式系统都开始支持USB总线和接口标准.USB