USB状态错误原因
USBD_STATUS调试过USB的同学肯定见过BUS Hound里面给的各种错误提示,但是大家是否知道是什么意思呢?
The USBD_STATUS data type defines USB status values for USB requests.
typedef LONG USBD_STATUS;
The most significant 4 bits of USB status values are defined in the following table.
| Value | Meaning |
|---|---|
|
00 (USBD_STATUS_SUCCESS) |
Request was completed with success. |
|
01 (USBD_STATUS_PENDING) |
Request is pending. |
|
10 or 11 (USBD_STATUS_ERROR) |
Request was completed with an error. |
The least significant 28 bits of USB status values are defined in the following table.
| Value | Code | Meaning |
|---|---|---|
|
USBD_STATUS_CRC |
0xC0000001 |
CRC error (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_BTSTUFF |
0xC0000002 |
BTS error (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_DATA_TOGGLE_MISMATCH |
0xC0000003 |
Data toggle mismatch. |
|
USBD_STATUS_STALL_PID |
0xC0000004 |
The device returned a stall packet identifier (defined for backward compatibility with the USB 1.0) |
|
USBD_STATUS_DEV_NOT_RESPONDING |
0xC0000005 |
The device is not responding (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_PID_CHECK_FAILURE |
0xC0000006 |
The device returned a packet identifier check failure (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_UNEXPECTED_PID |
0xC0000007 |
The device returned an unexpected packet identifier error (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_DATA_OVERRUN |
0xC0000008 |
The device returned a data overrun error (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_DATA_UNDERRUN |
0xC0000009 |
The device returned a data underrun error (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_RESERVED1 |
0xC000000A |
Reserved. |
|
USBD_STATUS_RESERVED2 |
0xC000000B |
Reserved. |
|
USBD_STATUS_BUFFER_OVERRUN |
0xC000000C |
The device returned a buffer overrun error (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_BUFFER_UNDERRUN |
0xC000000D |
The device returned a buffer underrun error (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_NOT_ACCESSED |
0xC000000F |
The USB stack could not access the device (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_FIFO |
0xC0000010 |
The device returned a FIFO error (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_XACT_ERROR |
0xC0000011 |
The device returned a transaction error (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_BABBLE_DETECTED |
0xC0000012 |
The device returned a babble detected error (defined for backward compatibility with the USB 1.0). |
|
USBD_STATUS_DATA_BUFFER_ERROR |
0xC0000013 |
Hardware status codes that range from 0x00000001 to 0x000000FF (defined for backward compatibility with the USB 1.0 stack). |
|
USBD_STATUS_NO_PING_RESPONSE |
0xC0000014 | No response was received from the device for a ping packet sent by the host. |
|
USBD_STATUS_INVALID_STREAM_TYPE |
0xC0000015 | The stream type is invalid for the endpoint. |
|
USBD_STATUS_INVALID_STREAM_ID |
0xC0000016 | The stream identifier is invalid. |
|
USBD_STATUS_ENDPOINT_HALTED |
0xC0000030 |
A transfer was submitted to an endpoint that is stalled. |
|
USBD_STATUS_INVALID_URB_FUNCTION |
0x80000200 |
Invalid URB function. |
|
USBD_STATUS_INVALID_PARAMETER |
0x80000300 |
Invalid parameter. |
|
USBD_STATUS_ERROR_BUSY |
0x80000400 |
The client driver caused an error by attempting to close an endpoint, interface, or configuration handle with outstanding transfers. |
|
USBD_STATUS_REQUEST_FAILED |
0x80000500 |
The hub driver cannot complete a URB request. |
|
USBD_STATUS_INVALID_PIPE_HANDLE |
0x80000600 |
Invalid pipe handle. |
|
USBD_STATUS_NO_BANDWIDTH |
0x80000700 |
There was not enough bandwidth to open a requested endpoint. |
|
USBD_STATUS_INTERNAL_HC_ERROR |
0x80000900 |
Unspecified host controller error. |
|
USBD_STATUS_ERROR_SHORT_TRANSFER |
0x80000900 |
The transfer ended with a short packet, but the USBD_SHORT_TRANSFER_OK bit is not set for the pipe. |
|
USBD_STATUS_BAD_START_FRAME |
0xC0000A00 |
The requested start frame is not within a range of USBD_ISO_START_FRAME_RANGE frames of the current USB frame. Whenever this error occurs, the system sets the stall bit on the pipe. |
|
USBD_STATUS_ISOCH_REQUEST_FAILED |
0xC0000B00 |
The host controller returns this error whenever all packets in an isochronous transfer complete with an error. |
|
USBD_STATUS_FRAME_CONTROL_OWNED |
0xC0000C00 |
The hub driver returns this error whenever the frame length control for the host controller is being used by a driver other than the host controller driver. |
|
USBD_STATUS_FRAME_CONTROL_NOT_OWNED |
0xC0000D00 |
The hub driver returns this error if the caller does not own frame length control and attempts to release or modify the host controller frame length. |
|
USBD_STATUS_NOT_SUPPORTED |
0xC0000E00 |
The request was not supported. |
|
USBD_STATUS_INAVLID_CONFIGURATION_DESCRIPTOR |
0xC0000F00 |
Invalid configuration descriptor. |
|
USBD_STATUS_INSUFFICIENT_RESOURCES |
0xC0001000 |
Insufficient resources. |
|
USBD_STATUS_SET_CONFIG_FAILED |
0xC0002000 |
An attempt to change the device configuration failed. |
|
USBD_STATUS_BUFFER_TOO_SMALL |
0xC0003000 |
The buffer is too small. |
|
USBD_STATUS_INTERFACE_NOT_FOUND |
0xC0004000 |
The interface was not found. |
|
USBD_STATUS_INAVLID_PIPE_FLAGS |
0xC0005000 |
Invalid pipe flags. |
|
USBD_STATUS_TIMEOUT |
0xC0006000 |
The request timed out. |
|
USBD_STATUS_DEVICE_GONE |
0xC0007000 |
The device is no longer present in the system. |
|
USBD_STATUS_STATUS_NOT_MAPPED |
0xC0008000 |
The device bus address is not mapped to system memory. |
|
USBD_STATUS_HUB_INTERNAL_ERROR |
0xC0009000 |
The hub driver returns this error whenever it intercepted a URB that was targeted at some other device. |
|
USBD_STATUS_CANCELED |
0xC0010000 |
The USB stack reports this error whenever it completed a transfer because of an AbortPipe request from the client driver. |
|
USBD_STATUS_ISO_NOT_ACCESSED_BY_HW |
0xC0020000 |
The host controller did not access the transfer descriptor (TD) that is associated with this packet. The USB stack reports this error in the packet status field of an isochronous transfer packet. |
|
USBD_STATUS_ISO_TD_ERROR |
0xC0030000 |
The host controller reported an error in the transfer descriptor (TD). The USB stack reports this error in the packet status field of an isochronous transfer packet. |
|
USBD_STATUS_ISO_NA_LATE_USBPORT |
0xC0040000 |
The client driver submitted the packet on time, but the packet failed to reach the miniport driver on time. The USB stack reports this error in the packet status field of an isochronous transfer packet. |
|
USBD_STATUS_ISO_NOT_ACCESSED_LATE |
0xC0050000 |
The client driver did not submit the packet on time. The USB stack reports this error in the packet status field of an isochronous transfer packet. |
|
USBD_STATUS_BAD_DESCRIPTOR |
0xC0100000 |
Invalid descriptor. |
|
USBD_STATUS_BAD_DESCRIPTOR_BLEN |
0xC0100001 |
Invalid descriptor length. |
|
USBD_STATUS_BAD_DESCRIPTOR_TYPE |
0xC0100002 |
Invalid descriptor type. |
|
USBD_STATUS_BAD_INTERFACE_DESCRIPTOR |
0xC0100003 |
Invalid interface descriptor. |
|
USBD_STATUS_BAD_ENDPOINT_DESCRIPTOR |
0xC0100004 |
Invalid endpoint descriptor. |
|
USBD_STATUS_BAD_INTERFACE_ASSOC_DESCRIPTOR |
0xC0100005 |
Invalid interface association descriptor. |
|
USBD_STATUS_BAD_CONFIG_DESC_LENGTH |
0xC0100006 |
Invalid configuration descriptor length. |
|
USBD_STATUS_BAD_NUMBER_OF_INTERFACES |
0xC0100007 |
Invalid number of interfaces. |
|
USBD_STATUS_BAD_NUMBER_OF_ENDPOINTS |
0xC0100008 |
Invalid number of endpoints. |
|
USBD_STATUS_BAD_ENDPOINT_ADDRESS |
0xC0100009 |
Invalid endpoint address. |
Related topics
USB Constants and Enumerations http://msdn.microsoft.com/zh-cn/subscriptions/ff539136
USB状态错误原因的更多相关文章
- coreseek常见错误原因及解决方法
coreseek常见错误原因及解决方法 Coreseek 中文全文检索引擎 Coreseek 是一款中文全文检索/搜索软件,以GPLv2许可协议开源发布,基于Sphinx研发并独立发布,专攻中文搜索和 ...
- /etc/rc.d/init.d/iptables: No such file or directory 错误原因
注:本文转载自cnblogs:一天学点的文章</etc/rc.d/init.d/iptables: No such file or directory 错误原因> RedHat Enter ...
- 安装VisualSVN Server 报"Service 'VisualSVN Server' failed to start. Please check VisualSVN Server log in Event Viewer for more details"错误.原因是启动"VisualSVN Server"失败
安装VisualSVN Server 报"Service 'VisualSVN Server' failed to start. Please check VisualSVN Server ...
- sc start service 1063 1053 错误原因
在进入点函数里面要完成ServiceMain的初始化,准确点说是初始化一个SERVICE_TABLE_ENTRY结构数组,这个结构记录了这个服务程序里面所包含的所有服务的名称和服务的进入点函数,下面是 ...
- http 报错码对应的错误原因
转:http://blog.csdn.net/cutbug/article/details/4024818 1xx - 信息提示这些状态代码表示临时的响应.客户端在收到常规响应之前,应准备接收一个或多 ...
- 微信的redirect_uri参数错误原因分析
我们可以根据微信的开发者文档 http://mp.weixin.qq.com/wiki/17/c0f37d5704f0b64713d5d2c37b468d75.html 网页授权获取用户验证这一章来 ...
- TCP/IP 某些最常见的错误原因码 (errno)列表
对于在基于 UNIX 的环境中的 TCP/IP 用户,下表列出了某些最常见的错误原因码 (errno).它不是完整的错误列表.可以在文件 /usr/include/sys/errno.h 中找到 Er ...
- [转]PLS-S-00201, identifier 'CALLDEMO.GET_EMPLOYEES' must be declared 预编译错误原因及解决办法
$ proc sample9.pc SQLCHECK=SEMANTICS Pro*C/C++: Release 11.2.0.1.0 - Production on Tue Jan 8 15:18:4 ...
- ORA-04091错误原因与解决方法
最近工作中写了一触发器报错:ORA-04091:table XX is mutating, trigger/function may not see it. 下面通过官方文档及网友提供资料分析一下错 ...
随机推荐
- oracle for update和for update nowait
原文地址:http://www.cnblogs.com/quanweiru/archive/2012/11/09/2762223.html 1.for update 和 for update nowa ...
- 数据库 —— 使用JDBC操作数据库
[Link] http://www.developer.com/java/data/manipulating-a-database-with-jdbc.html Manipulating a Data ...
- JS~js里实现队列与堆栈
在面向对象的程序设计里,一般都提供了实现队列(queue)和堆栈(stack)的方法,而对于JS来说,我们可以实现数组的相关操作,来实现队列和堆栈的功能,看下面的相关介绍. 一 看一下它们的性质,这种 ...
- Linux shell 之 提取文件名和目录名的一些方法
很多时候在使用Linux的shell时,我们都需要对文件名或目录名进行处理,通常的操作是由路径中提取出文件名,从路径中提取出目录名,提取文件后缀名等等.例如,从路径/dir1/dir2/file.tx ...
- android获得屏幕高度和宽度
获取屏幕的宽度与高度有以下几种方法: .WindowManager wm = (WindowManager) getContext() .getSystemSe ...
- android style 退出动画 解决退出动画无效问题
在AndroidMenifest.xml文件里面的Activity声明中,增加自己的Theme声明,如下: <activity android:name=".MyOrderListSe ...
- ScrollView与ListView合用(正确计算Listview的高度)的问题解决
最近做项目中用到ScrollView和ListView一起使用的问题,显示的时候ListView不能完全正确的显示,查了好多资料终于成功解决: 首先,ListView不能直接用,要自定义一个,然后 ...
- Android Monkey具体解释
Monkey是一个执行在Android设备或者虚拟机上的程序,它能随机模拟一系列用户的操作.点击,滑动,能够用它来做压力測试. 在Monkey执行的过程中,它会产生并发送一系列的事件给系统,而且监听系 ...
- 打勾显示输入的密码 --EditText与setTransformationMethod
实现目标: 实现原理: 为CheckBox添加一个监听器事件; 实现的源码: package edu.cquptzx.showPassword; import android.app.Activity ...
- LA 6449 IQ Test
[题目] 给出一个长度为n的数组(8<n<12),告诉你规律 (1<=d<=3)要求d尽量小 现在求第n+1项 [题解] 水题 不知道怎么求a1~ad? 用克拉默法则 [代码 ...