以下是相关类型的详细说明:
 
地址:https://www.usb.org/documents
 
搜索device class
 
以下是USB所有支持的设备类型代码.
 
地址:http://www.usb.org/developers/defined_class
 
USB Class Codes                    
 
November 17, 2009
 

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 contained in three bytes with the names Base Class, SubClass, and Protocol. (Note that ‘Base Class’ is used in this description to identify the first byte of the Class Code triple. That terminology is not used in the USB Specification). There are two places on a device where class code information can be placed.One place is in the Device Descriptor, and the other is in Interface Descriptors. Some defined class codes are allowed to be used only in a Device Descriptor, others can be used in both Device and Interface Descriptors, and some can only be used in Interface Descriptors. The table below shows the currently defined set of  Base Class values, what the generic usage is, and where that Base Class can be used (either Device or Interface Descriptors or both).
 
 
 
 
 
 
 
 
Base Class
 
 
Descriptor Usage
 
 
Description
 
 
00h
 
 
Device
 
 
Use class information in the Interface Descriptors
 
 
01h
 
 
Interface
 
 
Audio  
 
 
02h
 
 
Both
 
 
Communications and CDC Control
 
 
03h
 
 
Interface
 
 
HID (Human Interface Device)
 
 
05h
 
 
Interface
 
 
Physical
 
 
06h
 
 
Interface
 
 
Image
 
 
07h
 
 
Interface
 
 
Printer
 
 
08h
 
 
Interface
 
 
Mass Storage
 
 
09h
 
 
Device
 
 
Hub
 
 
0Ah
 
 
Interface
 
 
CDC-Data
 
 
0Bh
 
 
Interface
 
 
Smart Card
 
 
0Dh
 
 
Interface
 
 
Content Security
 
 
0Eh
 
 
Interface
 
 
Video
 
 
0Fh
 
 
Interface
 
 
Personal Healthcare
 
 
DCh
 
 
Both
 
 
Diagnostic Device
 
 
E0h
 
 
Interface
 
 
Wireless Controller
 
 
EFh
 
 
Both
 
 
Miscellaneous
 
 
FEh
 
 
Interface
 
 
Application Specific
 
 
FFh
 
 
Both
 
 
Vendor Specific
 
 
 
 
 
 

Base Class 00h (Device)
 
This base class is defined to be used in Device Descriptors to indicate that class information should be determined from the Interface Descriptors in the device. There is one class code definition in this base class.  All other values are reserved.
 
 
 
This value is also used in Interface Descriptors to indicate a null class code triple.
 
 
 
 
 
 
 
 
Base Class
 
 
SubClass
 
 
Protocol
 
 
Meaning
 
 
00h
 
 
00h
 
 
00h
 
 
Use class code info from Interface Descriptors
 
 
 
 
 
 

Base Class 01h (Audio)
 
This base class is defined for Audio capable devices that conform to the Audio Device Class Specification 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 may only be used in Interface Descriptors.
 
 
 
 
 
 
 
 
Base Class
 
 
SubClass
 
 
Protocol
 
 
Meaning
 
 
01h
 
 
xxh
 
 
xxh
 
 
Audio device
 
 
 
 
 
 
Base Class 02h (Communications and CDC Control)
 
 
 
This base class is defined for devices that conform to the Communications Device Class Specification 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.  Note that the Communication Device Class spec requires some class code values (triples) to be used in Device Descriptors and some to be used in Interface Descriptors.
 
 
 
 
 
 
Base Class
 
 
SubClass
 
 
Protocol
 
 
Meaning
 
 
02h
 
 
xxh
 
 
xxh
 
 
Communication device class
 
 
 
 
Base Class 03h (HID – Human Interface Device)
 
This base class is defined for devices that conform to the HID Device Class Specification 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
 
 
03h
 
 
xxh
 
 
xxh
 
 
HID device class
 
 
 
 
Base Class 05h (Physical)
 
This base class is defined for devices that conform to the Physical Device Class Specification 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
 
 
05h
 
 
xxh
 
 
xxh
 
 
Physical device class
 
 
 
 
 
 
Base Class 06h (Still Imaging)
 
This base class is defined for devices that conform to the Imaging Device Class Specification 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.
 
 
 
 
 
 
Base Class
 
 
SubClass
 
 
Protocol
 
 
Meaning
 
 
06h
 
 
01h
 
 
01h
 
 
Still Imaging device
 
 
 
 
 
 
Base Class 07h (Printer)
 
This base class is defined for devices that conform to the Printer Device Class Specification 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
 
 
07h
 
 
xxh
 
 
xxh
 
 
Printer device
 
 
 
 
 
 
Base Class 08h (Mass Storage)
 
This base class is defined for devices that conform to the Mass Storage Device Class Specification 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
 
 
08h
 
 
xxh
 
 
xxh
 
 
Mass Storage device
 
 
 
 
 
 
Base Class 09h (Hub)
 
This base class is defined for devices that are USB hubs and conform to the definition in the USB specification.  That specification defines the complete triples as shown below.  All other values are reserved.  These class codes can only be used in Device Descriptors.
 
 
 
 
 
 
Base Class
 
 
SubClass
 
 
Protocol
 
 
Meaning
 
 
09h
 
 
00h
 
 
00h
 
 
Full speed Hub
 
 
01h
 
 
Hi-speed hub with single TT
 
 
02h
 
 
Hi-speed hub with multiple TTs
 
 
 
 
 
 
Base Class 0Ah (CDC-Data)
 
This base class is defined for devices that conform to the Communications Device Class Specification 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
 
 
0Ah
 
 
xxh
 
 
xxh
 
 
CDC data device
 
 
 
 
 
 
Base Class 0Bh (Smart Card)
 
This base class is defined for devices that conform to the Smart Card Device Class Specification 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
 
 
0Bh
 
 
xxh
 
 
xxh
 
 
Smart Card device
 
 
 
 
 
 
Base Class 0Dh (Content Security)
 
This base class is defined for devices that conform to the Content Security Device Class Specification 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
 
 
0Dh
 
 
00h
 
 
00h
 
 
Content Security device
 
 
 
 
 
 
Base Class 0Eh (Video)
 
This base class is defined for devices that conform to the Video Device Class Specification 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
 
 
0Eh
 
 
xxh
 
 
xxh
 
 
Video device
 
 
 
 
 
 
Base Class 0Fh (Personal Healthcare)
 
This base class is defined for devices that conform to the Personal Healthcare Device Class Specification 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 should only be used in Interface Descriptors.
 
 
 
 
 
 
Base Class
 
 
SubClass
 
 
Protocol
 
 
Meaning
 
 
0Fh
 
 
xxh
 
 
xxh
 
 
Personal Healthcare device
 
 
 
 
 
 
Base Class DCh (Diagnostic Device)
 
This base class is defined for devices that diagnostic devices. There is currently only one value defined. All other values are reserved. This class code can be used in Device or Interface Descriptors.
 
 
 
 
 
 
Base Class
 
 
SubClass
 
 
Protocol
 
 
Meaning
 
 
DCh
 
 
01h
 
 
01h
 
 
USB2 Compliance Device.  Definition for this device can be found at http://www.intel.com/technology/usb/spec.htm
 
 
 
 
 
 
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 www.bluetooth.com.
 
 
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
 
 
04h
 
 
 
 
Bluetooth AMP Controller. Get specific information from www.bluetooth.com.
 
 
2h
 
 
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
 
 
 
 
 
 
以下是相关类型的详细说明:
 
地址:http://www.usb.org/developers/devclass_docs
 
Approved Class Specification Documents 
 
 
 
If you have questions regarding any of these documents please contact the DWG chair (dwg-wg-chair@usb.org) and your questions will be channeled to the appropriate group.
 
Audio Class
 
Audio Device Class Spec for Basic Audio Devices and Adopters Agreement (.zip format, size 1.33MB)
Audio Device Document 1.0
Audio Data Formats 1.0
Audio Terminal Types 1.0
USB MIDI Devices 1.0
Audio Devices Rev. 2.0 Spec and Adopters Agreement (.zip format, size 1.28MB) 
 
Battery Charging
 
Battery Charging v1.1 Spec and Adopters Agreement (.zip format, size 292 KB)
 
Cable and Connector
 
Cable and Connector Class 2.0 
Series 'A' Plug form factor Guideline 1.0
USB Connector for Mezzanine Applications Guidelines Rev. 1.0
Micro-USB Cables and Connectors v1.01 Spec and Adopters Agreement
 
Common Class (CCS)
 
Common Class Base Specification 1.0
 
Communications Device Class
 
Class definitions for Communication Devices 1.2 (.zip file format, size 2.61 MB)
 the components of CDC 1.1 have been reorganized as five separate documents:
 ATM120.pdf -- CDC Subclass for Asynchronous Transfer Mode Devices
 CDC120.pdf -- CDC Subclass for Communications Devices
 ECM120.pdf -- CDC Subclass for Ethernet Control Model Devices
 ISDN120.pdf -- CDC Subclass for ISDN Devices
 PSTN120.pdf -- CDC Subclass for PSTN devices
 CDC Subclass for Wireless Mobile Communication Devices 1.1
 CDC v1.2 WMC v1.1 Adopters Agreement

CDC Subclass Specification for Ethernet Emulation Model Devices 1.0
 
Network Control Model Devices Specification v1.0 and Adopters Agreement (.zip format, size 492 KB)
 
Content Security
 
Device Class Definition for Content Security Devices 1.0
Content Security Method 1 - Basic Authentication Protocol 1.0
Content Security Method 2 - USB Digital Transmission Content Protection Implementation 1.0
 
Device Firmware Upgrade Group
 
Device Firmware Upgrade 1.1 (new version 31-Aug-2004)
 
HID Class
 
HID Information
 
Imaging Class
 
Still Image Capture Device Definition 1.0 and Errata as of 16-Mar-2007 (.zip format, size 200 KB)
 
IrDA
 
IrDA Bridge Device Definition 1.0
 
Mass Storage
 
Mass Storage Class Specification Overview 1.3
Mass Storage Bulk Only 1.0
Mass Storage Control/Bulk/Interrupt (CBI) Specification 1.1  
Mass Storage UFI Command Specification 1.0
Mass Storage Bootability Specification 1.0
Lockable Mass Storage Specification 1.0 and Adopters Agreement (.zip format, size 288 KB)
   - Lockable Mass Storage IP Disclosure
 
Media Transfer Protocol
 
Media Transfer Protocol v.1.0 Spec and MTP v.1.0 Adopters Agreement (.zip format, size 1.86MB)
 
Monitor
 
Monitor Device Document 1.0
 
OpenUSBDI
 
OpenUSBDI Specification 1.0
 
Personal Healthcare
 
Personal Healthcare Rev. 1.0, Errata for USB Personal Health Care Device Class and Personal Healthcare Adopters Agreement (.zip format, size 386 KB)
 
Physical Interface Devices
 
Device Class Definition for PID 1.0
 
Power
 
Power Device Class Document 1.0
 
Printer Class
 
Printer Device Class Document 1.1
 
 
Smart Card Class
 
Smart Card CCID version 1.1
Smart Card ICCD version 1.0  
 
Test & Measurement Class
 
Test & Measurement Class Specifications
 
Video Class
 
Video Class 1.1 document set
     USB_Video_Class_1.1
     USB_Video_Identifiers_1.1
     USB_Video_Payload_DV_1.1
     USB_Video_Payload_Frame_Based_1.1
     USB_Video_Payload_MJPEG_1.1
     USB_Video_Payload_MPEG-2_TS_1.1
     USB_Video_Payload_Uncompressed_1.1
     USB_Video_Payload_Stream_Based_1.1
     USB_Video_Transport_1.1
     USB_Video_Example_1.1
     USB_Video_FAQ_1.1
 
Draft Class Specification Documents
 
PC Legacy Compatibility Specification 0.9
 
USB_Video_Compliance_1.09b -- draft for public review
 

 
 
下面是我的个人微信公众号，关注【一个早起的程序员】精彩系列文章每天不断。
 
 
 

1、故障现象
 
       在给单位的一台Server2008R2 X64服务器上安装扫描枪的时候发现无法安装扫描枪驱动，打开设备管理器可以看到扫描枪硬件有黄色叹号标记。错误信息如下：
 
 
        Windows给出的错误提示很简单，“该设备的驱动程序未被安装。（代码 28）”，就是安装驱动程序有错，但是具体是什么错误，我们从这里是无法得到的。如果以错误提示或者错误代码为关键字上网搜索的话，相信我你一定得不到太多有用的信息。因为之前另外一台win7x64上安装这个扫描枪驱动是没问题的，所以我知道问题不在驱动本身或者硬件设备上。一开始以为是操作系统版本问题，但08r2和win7本来就是差不多的，绕了一些弯路后，还是决定从错误的根源上找原因。
 
 2、问题分析
 
      上网搜索后，知道驱动安装会生成系统日志保持在C:\Windows\inf\setupapi.dev.log\setupapi.dev.log中。打开这个日志找到相关日志信息再来分析问题就非常简单了。这是一个非常值得学习的小技巧，log日志远比图形界面提供的错误信息完整并且更有指导意义。如下是setupapi.dev.log中驱动安装时的相关错误信息节选：
 
     inf:           Opened INF: 'c:\windows\temp\dmiwu\{de4ae465-6949-463b-9822-287a65fb2b68}\nls_vcp_driver.inf' ([strings])
!    inf:           Could not find include INF file "layout.inf". Error = 0x00000002
!    inf:           Unable to load INF: 'C:\Windows\System32\DriverStore\FileRepository\mdmcpq.inf_amd64_neutral_b53453733bd795bc\mdmcpq.inf'(00000003)
!    inf:           Error 3: The system cannot find the path specified.
!    inf:           Could not find include INF file "mdmcpq.inf". Error = 0x00000003
 
       相比设备管理器提供的错误信息，这里的日志足够清楚了，安装驱动的时候因为打不开mdmcpq.inf文件所以驱动安装无法继续报错了。上面一行的layout.inf文件经过分析上下文是不影响安装进行的，重要的还是缺少mdmcpq这个东西。找到驱动的安装目录，在这个扫描枪驱动的inf文件中有如下行：
 
[VCP_DriverInstall.NT]
Include=mdmcpq.inf
CopyFiles=FakeModemCopyFileSection
AddReg=VCP_DriverInstall.NT.AddReg
 
扫描枪的驱动在安装过程中会用到mdmcpq.inf文件，但是安装时候找不到这个文件，所以出错了。
 
3、解决方法
 
       原因找到了缺少依赖驱动，修复就行了，上网直接搜吧，很容易找到一堆关于mdmcpq缺失的问题。同时也会搜到一些无效的方法，比如复制原版的mdmcpq.inf 和 usbser.sys到system32的inf和drivers目录。
 
       但是从日志很明显知道驱动查找的是C:\Windows\System32\DriverStore\FileRepository\目录。所以最好的方法还是从正常的系统中直接复制C:\Windows\System32\DriverStore\FileRepository\mdmcpq.inf_amd64_neutral_b53453733bd795bc目录到故障系统的同位置目录下，如果复制时提示文件夹没有访问权限，给FileRepository目录增加用户权限就行了。
 
我这里出现故障的系统版本是非原版系统，作者也是小有名气的。但在修改系统过程中难免出现一些隐藏的问题，这种隐藏比较深的故障，对于普通用户来说确实是很难解决的问题。这里非常值得注意的是驱动安装日志用于分析问题的方法，图形化界面虽然友好，但在分析故障原因上有时候的提示太过简化反而变得毫无意义。
 
 
 
 
 
 

I2C
 
简介
 
I2C总线是由Philips公司开发的一种简单、双向二线制同步串行总线。SDA（串行数据线）和SCL（串行时钟线）都是双向I/O线，接口电路为开漏输出．需通过上拉电阻接电源VCC.
 
 
I2C（内部集成电路）总线接口处理微控制器与串行 I2C 总线间的通信。它提供多主模式功 
 能，可以控制所有 I2C 总线特定的序列、协议、仲裁和时序。它支持标准模式 (Sm)、快速模 
 式 (Fm) 和超快速模式 (Fm+)。
 
从模式和主模式
多主模式功能
标准速度模式（高达 100 kHz）
快速模式（高达 400 kHz）
超快速模式（高达 1 MHz）
7 位和 10 位寻址模式
 
I2C start/stop
 
 
开始信号：SCL为高电平时，SDA由高电平向低电平跳变，开始传送数据。
结束信号：SCL为高电平时，SDA由低电平向高电平跳变，结束传送数据。
 
I2C read
 
 
Master发送I2C addr（7bit）和w操作0（1bit），等待ACK
Slave发送ACK
Master发送reg addr（8bit），等待ACK
Slave发送ACK
Master发起START
Master发送I2C addr（7bit）和r操作1（1bit），等待ACK
Slave发送ACK
Slave发送data（8bit），即寄存器里的值
Master发送ACK。或者Master发送NACK，要求结束。
第8步和第9步可以重复多次，即顺序读多个寄存器
 
I2C write
 
 
Master发起START
Master发送I2C addr（7bit）和w操作0（1bit），等待ACK
Slave发送ACK
Master发送reg addr（8bit），等待ACK
Slave发送ACK
Master发送data（8bit），即要写入寄存器中的数据，等待ACK
Slave发送ACK
第6步和第7步可以重复多次，即顺序写多个寄存器
Master发起STOP
 
例子
 
I2C signal diagram: SDA(green) and SCL(yellow)
 
        write 0x55 DAC 
 
 
USB to I2C
 
通过USB虚拟串口实现PC与I2C设备进行通信。使用STM32L073xx MCU，硬件I2C和软件模拟I2C，用看门狗检测运行状态。
 
底层firmware实现代码和硬件电路图见链接：
 
此时I2C是做主机–>https://github.com/tclxspy/USB_I2C_73
另附上I2C做从机的代码–>https://github.com/tclxspy/QSFP28_PSM4
 
USB安装成功：
 
 
串口助手调试
 
 
部分代码main.c
 

    #include "main.h"
    #include "stm32l0xx_hal.h"
    #include "usb_device.h"
    #include "i2c.h"
    #include "soft_i2c.h"
    #include "stm32l0xx_nucleo.h"
    #include "usbd_cdc_if.h"
    #include "modsel.h"

    /* Buffer used for transmission */
    //uint8_t aTxBuffer[] = {0x33, 0x34};
    //uint8_t aTxBuffer[] = {0x46, 0x54};//{"FT"}
    uint8_t aTxBuffer[RXBUFFERSIZE];

    /* Buffer used for reception */
    uint8_t aRxBuffer[RXBUFFERSIZE];
    __IO uint16_t hTxNumData = 0;
    __IO uint16_t hRxNumData = 0;
    uint8_t bTransferRequest = 0;

    /* USER CODE BEGIN Includes */

    /* USER CODE END Includes */

    /* Private variables ---------------------------------------------------------*/
    I2C_HandleTypeDef I2cHandle;
    IWDG_HandleTypeDef hiwdg;

    /* USER CODE BEGIN PV */
    /* Private variables ---------------------------------------------------------*/

    /* USER CODE END PV */

    /* Private function prototypes -----------------------------------------------*/
    void SystemClock_Config(void);
    static void MX_GPIO_Init(void);
    static void MX_IWDG_Init(void);

    /* USER CODE BEGIN PFP */
    /* Private function prototypes -----------------------------------------------*/

    /* USER CODE END PFP */

    /* USER CODE BEGIN 0 */

    /* USER CODE END 0 */

    int main(void)
    {
      /* USER CODE BEGIN 1 */

      /* USER CODE END 1 */

      /* MCU Configuration----------------------------------------------------------*/

      /* Reset of all peripherals, Initializes the Flash interface and the Systick. */
      HAL_Init();

      /* USER CODE BEGIN Init */

      /* USER CODE END Init */

      /* Configure the system clock */
      SystemClock_Config();

      /* USER CODE BEGIN SysInit */

      /* USER CODE END SysInit */

      /* Initialize all configured peripherals */
      MX_GPIO_Init();
      MODSELL_Init();
      /* I2C2 init function */ 
    #ifdef HARDWARE_I2C  
      I2C_Init();  
    #else 
      Soft_I2C_Init();
    #endif /* HARDWARE_I2C */

      MX_IWDG_Init();
      MX_USB_DEVICE_Init();

      uint8_t len;
      uint8_t t;
      uint8_t deviceAddress;
      uint8_t regAddress;
      uint8_t length;
      uint8_t read_write;

    #ifdef HARDWARE_I2C
      while(1)
      {
        if(USB_USART_RX_STA&0x8000)
        {
          read_write = USB_USART_RX_Buffer[3];
          deviceAddress = USB_USART_RX_Buffer[4];
          regAddress = USB_USART_RX_Buffer[5];
          length = USB_USART_RX_Buffer[6];

          len = USB_USART_RX_STA&0x3FFF;
          USB_USART_RX_STA=0;

          for(t=0;t<len-8;t++)
          {
            aTxBuffer[t]=USB_USART_RX_Buffer[t+8];
          }

          if(read_write==MASTER_REQ_READ)
          {
            do
            {
              if(HAL_I2C_Mem_Read_IT(&I2cHandle, (uint16_t)deviceAddress, regAddress, I2C_MEMADD_SIZE_8BIT, (uint8_t*)aRxBuffer, length)!= HAL_OK)
              {
                /* Error_Handler() function is called when error occurs. */
                Error_Handler();
              }          
              while (HAL_I2C_GetState(&I2cHandle) != HAL_I2C_STATE_READY){}
            }
            while(HAL_I2C_GetError(&I2cHandle) == HAL_I2C_ERROR_AF);

            CDC_Transmit_FS(aRxBuffer, length);       
          }

          if(read_write==MASTER_REQ_WRITE)
          {
            do
            {
              if(HAL_I2C_Mem_Write_IT(&I2cHandle, (uint16_t)deviceAddress, regAddress, I2C_MEMADD_SIZE_8BIT, (uint8_t*)&aTxBuffer, len-8)!= HAL_OK)
              {
                /* Error_Handler() function is called when error occurs. */
                Error_Handler();
              }      
              while (HAL_I2C_GetState(&I2cHandle) != HAL_I2C_STATE_READY){}
            }
            while(HAL_I2C_GetError(&I2cHandle) == HAL_I2C_ERROR_AF);
          }
        }   


        /* Refresh IWDG: reload counter */
        if(HAL_IWDG_Refresh(&hiwdg) != HAL_OK)
        {
          /* Refresh Error */
          Error_Handler();
        }
      }
    #else
    while(1)
      { 
        if(USB_USART_RX_STA&0x8000)
        { 
          read_write = USB_USART_RX_Buffer[3];
          deviceAddress = USB_USART_RX_Buffer[4];
          regAddress = USB_USART_RX_Buffer[5];
          length = USB_USART_RX_Buffer[6];

          len = USB_USART_RX_STA&0x3FFF;
          USB_USART_RX_STA=0;

          for(t=0;t<len-8;t++)
          {
            aTxBuffer[t]=USB_USART_RX_Buffer[t+8];
          }

          if(read_write==MASTER_REQ_READ)
          {        
            Soft_I2C_Read_Reg(deviceAddress, regAddress, aRxBuffer, length);       
            CDC_Transmit_FS(aRxBuffer, length);
          }  

          if(read_write==MASTER_REQ_WRITE)
          {  
            Soft_I2C_Send_Reg(deviceAddress, regAddress, aTxBuffer, len-8);
          }
        }

        /* Refresh IWDG: reload counter */
        if(HAL_IWDG_Refresh(&hiwdg) != HAL_OK)
        {
          /* Refresh Error */
          Error_Handler();
        }
      }
    #endif /* HARDWARE_I2C */
    }

    /** System Clock Configuration
    */
    void SystemClock_Config(void)
    {
      RCC_OscInitTypeDef RCC_OscInitStruct;
      RCC_ClkInitTypeDef RCC_ClkInitStruct;
      RCC_PeriphCLKInitTypeDef PeriphClkInit;

        /**Configure the main internal regulator output voltage 
        */
      __HAL_PWR_VOLTAGESCALING_CONFIG(PWR_REGULATOR_VOLTAGE_SCALE1);

        /**Initializes the CPU, AHB and APB busses clocks 
        */
      RCC_OscInitStruct.OscillatorType = RCC_OSCILLATORTYPE_HSI|RCC_OSCILLATORTYPE_HSI48;
      RCC_OscInitStruct.HSIState = RCC_HSI_ON;
      RCC_OscInitStruct.HSICalibrationValue = 16;
      RCC_OscInitStruct.HSI48State = RCC_HSI48_ON;
      RCC_OscInitStruct.PLL.PLLState = RCC_PLL_ON;
      RCC_OscInitStruct.PLL.PLLSource = RCC_PLLSOURCE_HSI;
      RCC_OscInitStruct.PLL.PLLMUL = RCC_PLLMUL_4;
      RCC_OscInitStruct.PLL.PLLDIV = RCC_PLLDIV_2;
      if (HAL_RCC_OscConfig(&RCC_OscInitStruct) != HAL_OK)
      {
        _Error_Handler(__FILE__, __LINE__);
      }

        /**Initializes the CPU, AHB and APB busses clocks 
        */
      RCC_ClkInitStruct.ClockType = RCC_CLOCKTYPE_HCLK|RCC_CLOCKTYPE_SYSCLK
                                  |RCC_CLOCKTYPE_PCLK1|RCC_CLOCKTYPE_PCLK2;
      RCC_ClkInitStruct.SYSCLKSource = RCC_SYSCLKSOURCE_PLLCLK;
      RCC_ClkInitStruct.AHBCLKDivider = RCC_SYSCLK_DIV1;
      RCC_ClkInitStruct.APB1CLKDivider = RCC_HCLK_DIV1;
      RCC_ClkInitStruct.APB2CLKDivider = RCC_HCLK_DIV1;

      if (HAL_RCC_ClockConfig(&RCC_ClkInitStruct, FLASH_LATENCY_1) != HAL_OK)
      {
        _Error_Handler(__FILE__, __LINE__);
      }

      PeriphClkInit.PeriphClockSelection = RCC_PERIPHCLK_USB;
      PeriphClkInit.UsbClockSelection = RCC_USBCLKSOURCE_HSI48;
      if (HAL_RCCEx_PeriphCLKConfig(&PeriphClkInit) != HAL_OK)
      {
        _Error_Handler(__FILE__, __LINE__);
      }

        /**Configure the Systick interrupt time 
        */
      HAL_SYSTICK_Config(HAL_RCC_GetHCLKFreq()/1000);

        /**Configure the Systick 
        */
      HAL_SYSTICK_CLKSourceConfig(SYSTICK_CLKSOURCE_HCLK);

      /* SysTick_IRQn interrupt configuration */
      HAL_NVIC_SetPriority(SysTick_IRQn, 0, 0);
    }



    /** Pinout Configuration
    */
    static void MX_GPIO_Init(void)
    {
      /* GPIO Ports Clock Enable */
      //__HAL_RCC_GPIOB_CLK_ENABLE();
      __HAL_RCC_GPIOA_CLK_ENABLE();
    }

    static void MX_IWDG_Init(void)
    {
      hiwdg.Instance = IWDG;
      hiwdg.Init.Prescaler = IWDG_PRESCALER_64;
      hiwdg.Init.Window = 0xfff;
      hiwdg.Init.Reload = 0xfff;
      if (HAL_IWDG_Init(&hiwdg) != HAL_OK)
      {
        _Error_Handler(__FILE__, __LINE__);
      }
    }

    /**
      * @brief  This function is executed in case of error occurrence.
      * @param  None
      * @retval None
      */
    void _Error_Handler(char * file, int line)
    {
      /* USER CODE BEGIN Error_Handler_Debug */
      /* User can add his own implementation to report the HAL error return state */
      while(1) 
      {
      }
      /* USER CODE END Error_Handler_Debug */ 
    }

    #ifdef USE_FULL_ASSERT

    /**
       * @brief Reports the name of the source file and the source line number
       * where the assert_param error has occurred.
       * @param file: pointer to the source file name
       * @param line: assert_param error line source number
       * @retval None
       */
    void assert_failed(uint8_t* file, uint32_t line)
    {
      /* USER CODE BEGIN 6 */
      /* User can add his own implementation to report the file name and line number,
        ex: printf("Wrong parameters value: file %s on line %d\r\n", file, line) */
      /* USER CODE END 6 */

    }
    #endif

方法一：通过修改注册表禁用USB
 
 
 
      原理：只要把注册表HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\USBSTOR路径下的Start值改成4即可禁用USB（默认为3，即允许USB）。
 
      优点：简单易行。
 
      缺点：地球人都知道，很容易识破。
 
      建议：用一个timer或者创建一个线程，来锁定这个值。
 
 
 
      程序代码：
 
 
 
 
 
  
 
   [csharp] 
   view plain
    copy 
   
 
   
 
    print
   ?
  
 
 
 
 
 using Microsoft.Win32;  
   
 /// <summary>  
 /// 通过注册表启用USB  
 /// </summary>  
 /// <returns></returns>  
 public bool RegToRunUSB()   
 {  
     try  
     {  
         RegistryKey regKey = Registry.LocalMachine; //读取注册列表HKEY_LOCAL_MACHINE  
         string keyPath = @"SYSTEM\CurrentControlSet\Services\USBSTOR"; //USB 大容量存储驱动程序  
         RegistryKey openKey = regKey.OpenSubKey(keyPath, true);  
         openKey.SetValue("Start", 3); //设置键值对（3）为开启USB（4）为关闭  
         openKey.Close(); //关闭注册列表读写流  
         return true;  
     }  
     catch (Exception ex)   
     {  
         throw ex;  
     }  
 }  
   
 /// <summary>  
 /// 通过注册表禁用USB  
 /// </summary>  
 /// <returns></returns>  
 public bool RegToStopUSB()   
 {  
     try  
     {  
         RegistryKey regKey = Registry.LocalMachine;  
         string keyPath = @"SYSTEM\CurrentControlSet\Services\USBSTOR";  
         RegistryKey openKey = regKey.OpenSubKey(keyPath, true);  
         openKey.SetValue("Start", 4);  
         openKey.Close();  
         return true;  
     }  
     catch (Exception ex)  
     {  
         throw ex;  
     }  
 }  
 
 

 
方法二：通过独占USB驱动文件禁用USB
 
 
 
      原理：如果U盘第一次在某个电脑上使用，电脑会自动安装该U盘的驱动信息，修改C:\Windows\inf\usbstor.inf和C:\Windows\inf\usbstor.PNF这两个文件。假如我们用C#程序以独占的形式打开他们，那么Windows便无法修改这两个文件，U盘驱动安装不上自然无法使用。
 
      优点：简单易行，不容易识破。
 
      缺点：只能禁用未在该电脑上使用过的U盘。
 
      建议：一定要注意独占的时候文件打开对象要用类的成员变量(也就是模块级变量)，如果用局部变量，会自动被托管程序释放，达不到独占的效果。
 
 
 
      程序代码：
 
      注：以下fs和fs1对象变量我是放在了窗体中，作为窗体类的成员变量。
 

 
 
 
 
 
  
 
   [csharp] 
   view plain
    copy 
   
 
   
 
    print
   ?
  
 
 
 
 
 using System.IO;  
   
 public FileStream fs = null;  
 public FileStream fs1 = null;  
   
 //以独占方式打开文件  
 fs = new FileStream("C:\\Windows\\inf\\usbstor.inf", FileMode.Open, FileAccess.Read, FileShare.None);  
 fs1 = new FileStream("C:\\Windows\\inf\\usbstor.PNF", FileMode.Open, FileAccess.Read, FileShare.None);