USB Mass Storage Class Bulk Only Transport

更新时间:2023-06-26 15:37:03 阅读: 评论:0

Universal Serial Bus Mass Storage Class Bulk-Only Transport
Revision 1.0
September 31, 1999
Change History
Revision Issue Date Comments
0.7September 23, 1998Initial draft, pre-relea
0.8October 6, 1998Revisions made at the Mass Storage DWG review – Irvine, CA
0.9October 21, 1998Revisions made at the Mass Storage DWG review – Plano, TX
0.9a January 5, 1999Revisions made at the Mass Storage DWG review –  Tigard, OR
0.9b February 1, 1999Additions of LUN support - Milpitas, CA
1.0[RC1]March 5, 1999RR review - Midway, UT
1.0[RC2]March 23, 1999Revisions from reflector review comments
1.0[RC3]March 29, 1999Specification line by line review – Milpitas, CA
1.0[RC4]June 21, 1999Specification line by line review – RR21 – Milpitas, CA
1.0September 31, 1999Final Revision edits for Relead Document – SLC, UT
USB Device Class Definition for Mass Storage Devices
Copyright © 1998, 1999, USB Implementers Forum.
All rights rerved.
INTELLECTUAL PROPERTY DISCLAIMER
白日梦英文THIS SPECIFICATION IS PROVIDED “AS IS” WITH NO WARRANTIES WHATSOEVER INCLUDING ANY WARRANTY OF MERCHANTABILITY, FITNESS FOR ANY PARTICULAR PURPOSE, OR ANY WARRANTY OTHERWISE ARISING OUT OF ANY PROPOSAL, SPECIFICATION, OR SAMPLE.
A LICENSE IS HEREBY GRANTED TO REPRODUCE AND DISTRIBUTE THIS SPECIFICATION FOR INTERNAL USE ONLY.  NO OTHER LICENSE, EXPRESS OR IMPLIED, BY ESTOPPEL OR OTHERWISE, TO ANY OTHER INTELLECTUAL PROPERTY RIGHTS IS GRANTED OR INTENDED HEREBY.
AUTHORS OF THIS SPECIFICATION DISCLAIM ALL LIABILITY, INCLUDING LIABILITY FOR INFRINGEMENT OF PROPRIETARY RIGHTS, RELATING TO IMPLEMENTATION OF INFORMATION IN THIS SPECIFICATION.  AUTHORS OF THIS SPECIFICATION ALSO DO NOT WARRANT OR REPRESENT THAT SUCH IMPLEMENTATION(S) WILL NOT INFRINGE SUCH RIGHTS.
Contributors
Al Rickey, Phoenix Technologies
Alan Haffner, Lexar Media
Bill Stanley, Adaptec
Calaimany Bhoopathi, Shuttle Technology
Curtis E. Stevens, Phoenix Technologies
Darrell Redford , Iomega Corporation
Dave Gilbert, In-System Design
David G. Lawrence, Global Technology Development David L. Jolley, Iomega Corporation
美丽心境David Luke, In-System Design
Eric Luttman, In-System Design
Glen Slick, Microsoft Corporation
Hiromichi Oribe, Hagiwara Sys-ComCo
Jan Matejica, PIMC/Philips
Jim Blackson, Y-E Data, Inc
Jim Quigley, Iomega Corporation
Johan Craeybeckk, PIMC/Philips
Jordan Brown, Sun Microsystems
Kenny Chu, Hagiwara Sys-ComCo
Kenichi Hamada, Y-E Data, Inc
Mark Williams, Microsoft Corporation
Masayuki Kitagawa, Mitsumi
Mike Chen, CMD Technology Mike Glass, Microsoft Corporation Mike Liebow, eTEK Labs
Mike Nguyen, TEAC
Mike Pouln, Iomega Corporation Moto Watanabe, Hagiwara冬天泡温泉
N.R. Devanathan, Shuttle Technology Paramita Das, Sun Microsystems
Pat LaVarre, Iomega Corporation Peter S'Heeren, PIMC/Philips
Ryota Okazaki, NEC Corporation Sadao Yabuki, TEAC
Shigeyoshi Hashi, NEC Corporation Shing F. Lin, Adaptec
Steve Bayless, Hewlett-Packard Steve Kolokowsky, Anchor Chips Steven Smith, eTEK Labs
Terry Moore, MCCI
Tim Bradshaw, Iomega Corp Toyoko Shimizu, Y-E Data, Inc Trenton Henry, SMSC
Troy Davidson, Iomega Corporation Tsuyoshi Osawa, TEAC
Yuji Oishi, Hagiwara Sys-Com Co Ltd
Table of Contents
1Specification Overview and Scope (5)
1.1Scope (5)
2Terms and Abbreviations (6)
2.1Conventions (6)
2.2Definitions (6)
3Functional Characteristics (7)
3.1Bulk-Only Mass Storage Ret (class-specific request) (7)
3.2Get Max LUN (class-specific request) (7)
3.3Host/Device Packet Transfer Order (8)
3.4Command Queuing (8)
3.5Bi-Directional Command Protocol (8)
4Standard Descriptors (9)
倔是什么意思4.1Device Descriptor (9)
4.1.1Serial Number (9)
4.1.2Valid Serial Number Characters (10)
4.2Configuration Descriptor (10)
4.3Interface Descriptors (11)
4.4Endpoint Descriptors (11)
4.4.1Bulk-In Endpoint (11)
4.4.2Bulk-Out Endpoint (12)
5Command/Data/Status Protocol (13)
5.1Command Block Wrapper (CBW) (13)
感情洁癖5.2Command Status Wrapper (CSW) (14)
5.3Data Transfer Conditions (15)
5.3.1Command Transport (15)
5.3.2Data Transport (15)
5.3.3Status Transport (16)
5.3.4Ret Recovery (16)
6Host/Device Data Transfers (17)
6.1Overview (17)
6.2Valid and Meaningful CBW (17)
6.2.1Valid CBW (17)
6.2.2Meaningful CBW (17)
6.3Valid and Meaningful CSW (17)
6.3.1Valid CSW (17)
6.3.2Meaningful CSW (17)
6.4Device Error Handling (17)
6.5Host Error Handling (18)
6.6Error Class (18)
6.6.1CBW Not Valid (18)
6.6.2Internal Device Error (18)
6.6.3Host/Device Disagreements (18)
6.6.4Command Failure (18)
6.7The Thirteen Cas (18)
6.7.1H n - Host expects no data transfers (19)
6.7.2H i - Host expects to receive data from the device (20)
6.7.3H o - Host expects to nd data to the device (21)
List of Tables
Table 3.1 – Bulk-Only Mass Storage Ret (7)
Table 3.2 –Get Max LUN (7)
Table 4.1 - Device Descriptor (9)
Table 4.2 - Example Serial Number Format (10)
Table 4.3 - Valid Serial Number Characters (10)
Table 4.4 - Configuration Descriptor (10)
递名片Table 4.5 – Bulk-Only Data Interface Descriptor (11)
Table 4.6 - Bulk-In Endpoint Descriptor (11)
Table 4.7 – Bulk-Out Endpoint Descriptor (12)
Table 5.1 - Command Block Wrapper (13)
Table 5.2 - Command Status Wrapper (14)
电脑黑屏开不了机怎么办
Table 5.3 - Command Block Status Values (15)
Table 6.1 - Host/Device Data Transfer Matrix (19)
List of Figures
Figure 1 - Command/Data/Status Flow (13)
Figure 2 - Status Transport Flow (15)
1 Specification Overview and Scope
南航经管学院
1.1Scope
A familiarity with the USB1.0 and 1.1Specifications and the US
B Mass Storage Class Specification Overview is assumed.
This specification address Bulk-Only Transport, or in other words, transport of command, data, an
d status occurring solely via Bulk endpoints (not via Interrupt or Control endpoints).  This specification only us the default pipe to clear a STALL condition on the Bulk endpoints and to issue class-specific requests as defined below.  This specification does not require the u of an Interrupt endpoint.
This specification defines support for logical units that share common device characteristics.  Although this feature provides the support necessary to allow like mass storage devices to share a common USB interface descriptor, it is not intended to be ud to implement interface bridge devices.

本文发布于:2023-06-26 15:37:03,感谢您对本站的认可!

本文链接:https://www.wtabcd.cn/fanwen/fan/82/1044703.html

版权声明:本站内容均来自互联网,仅供演示用,请勿用于商业和其他非法用途。如果侵犯了您的权益请与我们联系,我们将在24小时内删除。

标签:洁癖   电脑   经管   感情
相关文章
留言与评论(共有 0 条评论)
   
验证码:
推荐文章
排行榜
Copyright ©2019-2022 Comsenz Inc.Powered by © 专利检索| 网站地图