ANSI INCITS375-2004 Information technology - Serial Bus Protocol - 3 (SBP-3)《信息技术.串行总线协议.3(SBP-3)》.pdf

《ANSI INCITS375-2004 Information technology - Serial Bus Protocol - 3 (SBP-3)《信息技术.串行总线协议.3(SBP-3)》.pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS375-2004 Information technology - Serial Bus Protocol - 3 (SBP-3)《信息技术.串行总线协议.3(SBP-3)》.pdf（161页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byfor Information Technology Serial Bus Protocol (SBP-3)ANSI INCITS 375-2004ANSIINCITS375-2004Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-

2、Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-ANSIINCITS 375-2004American National Standardfor Information Technology Serial Bus Protocol 3 (SBP-3)SecretariatInformation Techno

3、logy Industry CouncilApproved May 13, 2004 American National Standards Institute, Inc.AbstractThis standard specifies a protocol for the transport of commands, data and status between devices con-nected by Serial Bus, a memory-mapped split-transaction bus defined by ANSI/IEEE 1394-1995, Stan-dard fo

4、r a High Performance Serial Bus, as amended by ANSI/IEEE 1394a-2000 and ANSI/IEEE 1394b-2002.Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-Approval of an American National Stan

5、dard requires review by ANSI that therequirements for due process, consensus, and other criteria for approval havebeen met by the standards developer.Consensus is established when, in the judgement of the ANSI Board ofStandards Review, substantial agreement has been reached by directly andmaterially

6、 affected interests. Substantial agreement means much more thana simple majority, but not necessarily unanimity. Consensus requires that allviews and objections be considered, and that a concerted effort be madetowards their resolution.The use of American National Standards is completely voluntary;

7、theirexistence does not in any respect preclude anyone, whether he has approvedthe standards or not, from manufacturing, marketing, purchasing, or usingproducts, processes, or procedures not conforming to the standards.The American National Standards Institute does not develop standards andwill in n

8、o circumstances give an interpretation of any American NationalStandard. Moreover, no person shall have the right or authority to issue aninterpretation of an American National Standard in the name of the AmericanNational Standards Institute. Requests for interpretations should beaddressed to the se

9、cretariat or sponsor whose name appears on the titlepage of this standard.CAUTION NOTICE: This American National Standard may be revised orwithdrawn at any time. The procedures of the American National StandardsInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this

10、standard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2004 by

11、 Information Technology Industry Council (ITI)All rights reserved.No part of this publication may be reproduced in anyform, in an electronic retrieval system or otherwise,without prior written permission of ITI, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of AmericaCAUTION

12、: The developers of this standard have requested that holders of patents that may be re-quired for the implementation of the standard disclose such patents to the publisher. However, nei-ther the developers nor the publisher have undertaken a patent search in order to identify which, ifany, patents

13、may apply to this standard. As of the date of publication of this standard, followingcalls for the identification of patents that may be required for the implementation of the standard,notice of one or more such claims has been received. By publication of this standard, no positionis taken with resp

14、ect to the validity of this claim or of any rights in connection therewith. The knownpatent holder(s) has (have), however, filed a statement of willingness to grant a license underthese rights on reasonable and nondiscriminatory terms and conditions to applicants desiring to ob-tain such a license.

15、Details may be obtained from the publisher. No further patent search is con-ducted by the developer or publisher in respect to any standard it processes. No representation ismade or implied that this is the only license that may be required to avoid infringement in the use ofthis standard.Copyright

16、American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-iContentsPageForeword vii1 Scope and purpose 11.1 Scope. 11.2 Purpose 12 Normative references. 32.1 Reference scope 32.2 Approved references

17、 32.3 References under development. 33 Definitions and notation . 53.1 Definitions 53.1.1 Conformance . 53.1.2 Glossary. 53.1.3 Abbreviations . 83.2 Notation 93.2.1 Numeric values 93.2.2 Bit, byte and quadlet ordering 93.2.3 Register specifications. 103.2.4 State machines 124 Model (informative) 134

18、.1 Model overview 134.2 Unit architecture. 134.3 Logical units. 134.4 Requests and responses . 134.5 Data buffers . 144.6 Target agents. 164.7 Ordered and unordered execution. 174.8 Bridge-awareness 174.9 Streams 195 Data structures. 235.1 Data structure types and components . 235.2 Operation reques

19、t blocks (ORBs) 245.2.1 Generic ORB 245.2.2 Dummy ORB 255.2.3 Command block ORBs 265.2.4 Management ORBs . 305.3 Page tables 405.3.1 Overview 405.3.2 Unrestricted page tables 41Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or net

20、working permitted without license from IHS-,-,-iiPage5.3.3 Normalized page tables . 415.3.4 Node selectors. 425.4 Status block . 435.4.1 Status block formats 435.4.2 Request status. 455.4.3 Unsolicited device status . 475.4.4 Interim request status 486 Control and status registers. 496.1 Control and

21、 status registers overview 496.2 Core registers 496.3 Serial Bus-dependent registers . 506.4 BUSY_TIMEOUT register 506.5 MANAGEMENT_AGENT register 526.6 Command block registers 536.6.1 Command block registers summary 536.6.2 AGENT_STATE register 536.6.3 AGENT_RESET register . 546.6.4 ORB_POINTER reg

22、ister 556.6.5 DOORBELL register 566.6.6 UNSOLICITED_STATUS_ENABLE register . 566.6.7 HEARTBEAT_MONITOR register . 576.6.8 FAST_START register. 577 Configuration ROM 617.1 Configuration ROM hierarchy 617.2 Power reset initialization 627.3 Bus information block 627.4 Root directory 647.4.1 Root direct

23、ory (general) . 647.4.2 Vendor_ID entry. 647.4.3 Node_Capabilities entry. 647.4.4 Keyword_Leaf entry. 657.4.5 Instance_Directory entry 657.4.6 Unit_Directory entry . 657.5 Instance directory 667.6 Unit directory 667.7 Logical unit directory 667.8 Directory entries. 677.8.1 Directory entries summary.

24、 677.8.2 Specifier_ID entry 687.8.3 Version entry 687.8.4 Revision entry 687.8.5 Command_Set_Spec_ID entry 697.8.6 Command_Set entry 69Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS

25、-,-,-iiiPage7.8.7 Command_Set_Revision entry 697.8.8 Firmware_Revision entry 707.8.9 Management_Agent entry 707.8.10 Unit_Characteristics entry 707.8.11 Reconnect_Timeout entry 717.8.12 Fast_Start entry 717.8.13 Plug_Control_Register entry 727.8.14 Logical_Unit_Directory entry 727.8.15 Logical_Unit_

26、Number entry 737.8.16 Unit_Unique_ID entry. 747.9 Unit unique ID leaf 748 Access 758.1 Access overview 758.2 Access protocols 758.3 Access requests. 768.3.1 Login 768.3.2 Create task set . 778.4 Node handles. 778.4.1 Node handles (general) 778.4.2 Node handle allocation. 788.4.3 Node handle release

27、788.4.4 Node handle update after bus reset. 798.4.5 Node handle validation after net update 798.5 Heartbeat . 808.6 Reconnection . 808.7 Logout 819 Command execution 839.1 Command execution overview. 839.2 Requests and request lists. 839.2.1 Requests and request lists (general) . 839.2.2 Fetch agent

28、 initialization (informative). 839.2.3 Dynamic appends to request lists (informative) . 849.2.4 Fetch agent use by the BIOS (informative) 859.2.5 Use of the FAST_START register (informative). 859.2.6 Fetch agent parse of ORB and page tables (informative) 869.3 Fetch agent state machine. 879.4 Asynch

29、ronous data transfer . 909.5 Isochronous data transfer 919.6 Interim and completion status 929.7 Unsolicited status. 9310 Task management . 9510.1 Task management overview 95Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networ

30、king permitted without license from IHS-,-,-ivPage10.2 Task sets . 9510.3 Basic task management model 9510.4 Error conditions 9610.5 Task management requests 9610.5.1 Abort task. 9610.5.2 Abort task set. 9710.5.3 Logical unit reset 9810.5.4 Target reset . 9910.6 Task management event matrix 9911 Iso

31、chronous operations . 10311.1 Isochronous operations overview 10311.2 Talker operations . 10311.3 Listener operations 10511.4 Implementation recommendations (informative) 106AnnexesA Minimum Serial Bus node capabilities . 107B SCSI command and status encapsulation. 109C Security extensions 115D AV/C

32、 Encapsulation. 119E Isochronous data interchange format 123F Sample configuration ROM 127G Serial Bus transaction error recovery 133H SCSI Architecture Model conformance 135I Common isochronous packet (CIP) format 143J Bibliography . 147Tables1 Data transfer speeds . 272 Management request function

33、s . 313 Maximum payload for isochronous subactions 104Figures1 Bit ordering within a byte . 92 Byte ordering within a quadlet . 93 Quadlet ordering within an octlet . 104 CSR specification example 105 State machine example . 126 Linked list of ORBs 14Copyright American National Standards Institute P

34、rovided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-vPage7 Directly addressed data buffer . 158 Indirectly addressed data buffer (via page table). 169 Components of an isochronous stream (direct-access logical unit). 2010 Address p

35、ointer 2311 ORB pointer . 2412 ORB family tree 2413 ORB format 2414 Dummy ORB 2515 Command block ORB (single, non-isochronous buffer descriptor) 2616 Command block ORB (single, isochronous buffer descriptor) . 2817 Command block ORB (dual, non-isochronous buffer descriptors). 2918 Management ORB . 3

36、019 Login ORB 3220 Login response. 3321 Query logins ORB 3422 Query logins response format 3523 Create task set ORB 3624 Create task set response . 3625 Reconnect ORB . 3726 Node handle ORB 3827 Node handle response. 3928 Logout ORB . 3929 Task management ORB. 4030 Page table element (unrestricted p

37、age table) 4131 Page table element (when page_size equals four) 4232 Node selector. 4333 Basic status block format . 4334 Extended status block format. 4435 TRANSPORT FAILURE format for sbp_status 4636 BUSY_TIMEOUT format 5137 MANAGEMENT_AGENT format 5238 AGENT_STATE format 5439 AGENT_RESET format 5

38、440 ORB_POINTER format 5541 DOORBELL format 56Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-viPage42 UNSOLICITED_STATUS_ENABLE format . 5643 HEARTBEAT_MONITOR format . 5744 FAS

39、T_START format. 5845 Configuration ROM hierarchy 6146 Bus information block format . 6247 Bus information block capabilities field 6348 Vendor_ID entry format . 6449 Node_Capabilities entry format . 6450 Keyword_Leaf entry format 6551 Instance_Directory entry format. 6552 Unit_Directory entry format

40、 6653 Specifier_ID entry format . 6854 Version entry format 6855 Revision entry format. 6856 Command_Set_Spec_ID entry format. 6957 Command_Set entry format. 6958 Command_Set_Revision entry format. 6959 Firmware_Revision entry format 7060 Management_Agent entry format 7061 Unit_Characteristics entry

41、 format 7162 Reconnect_Timeout entry format 7163 Fast_Start entry format 7264 Plug_Control_Register entry format 7265 Logical_Unit_Directory entry format 7366 Logical_Unit_Number entry format 7367 Unit_Unique_ID entry format . 7468 Unit unique ID leaf format 7469 Fetch agent initialization with a du

42、mmy ORB 8470 Fetch agent state machine 88Copyright American National Standards Institute Provided by IHS under license with ANSINot for ResaleNo reproduction or networking permitted without license from IHS-,-,-viiForeword (This foreword is not part of American National Standard ANSI INCITS 375-2004

43、.)This standard defines a transport protocol within the domain of Serial Bus, IEEE1394, that is designed to permit efficient, peer-to-peer operation of input/outputdevices (disks, tapes, printers, etc.) by upper layer protocols such as operating sys-tems or embedded applications. Vendors that wish t

44、o implement devices that con-nect to Serial Bus may follow the requirements of this and other normativelyreferenced standards to manufacture an SBP-3 compliant device.There are ten annexes in this standard. Annexes A, B, C, D and E are normative andpart of this standard. Annexes F through J, inclusi

45、ve, are informative and are not con-sidered part of this standard.Requests for interpretation, suggestions for improvement and addenda, or defect re-ports are welcome. They should be sent to the INCITS Secretariat, Information Tech-nology Industry Council, 1250 I Street NW, Suite 200, Washington, DC

46、 20005-3922.This standard was processed and approved for submittal to ANSI by InterNationalCommittee for Information Technology Standardization (INCITS). Committee approv-al of this standard does not necessarily imply that all committee members voted forapproval. At the time it approved this standar

47、d, INCITS had the following members:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeApple Computer, Inc. David MichaelFarance, Inc Frank FaranceHewlett-Packard Company. Karen HigginbottomScott Jameson (Alt.)Steve Mills (Alt.)EIA Edward Mikoski, Jr.Su

48、an Hoyler (Alt.)IBM Corporation . Ronald F. SillettiInstitute for Certification of Computer Professionals. Kenneth M. ZemrowskiThomas Kurihara (Alt.)IEEE . Judith GormanRichard Holleman (Alt.)Robert Pritchard (Alt.)Intel Corporation . Philip WennblomDave Thewlis (Alt.)Microsoft Corporation . Mike Ks

49、arFrank Camara (Alt.)National Institute of Standards explicit description of the methods used to encapsulate 16-byte or larger command descriptor blocks (CDBs) within SBP-3; extensions necessary for initiators and targets to successfully interoperate across one or more Serial Bus bridges as specified by draft standard IEEE P1394.1 B7; isochronous facilities and methods, wit