ANSI INCITS 375-2004 Information Technology Serial Bus Protocol (SBP-3).pdf

《ANSI INCITS 375-2004 Information Technology Serial Bus Protocol (SBP-3).pdf》由会员分享，可在线阅读，更多相关《ANSI INCITS 375-2004 Information Technology Serial Bus Protocol (SBP-3).pdf（161页珍藏版）》请在麦多课文档分享上搜索。

1、American National StandardDeveloped byfor Information Technology Serial Bus Protocol (SBP-3)ANSI INCITS 375-2004ANSIINCITS375-2004ANSIINCITS 375-2004American National Standardfor Information Technology Serial Bus Protocol 3 (SBP-3)SecretariatInformation Technology Industry CouncilApproved May 13, 20

2、04 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 for a High Performance Serial Bus, as amen

3、ded by ANSI/IEEE 1394a-2000 and ANSI/IEEE 1394b-2002.Approval of an American National Standard 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

4、Board ofStandards Review, substantial agreement has been reached by directly andmaterially 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 mad

5、etowards their resolution.The use of American National Standards is completely voluntary; 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 s

6、tandards.The American National Standards Institute does not develop standards andwill in no 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 Ameri

7、canNational Standards Institute. Requests for interpretations should beaddressed to the secretariat 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 Standard

8、sInstitute require that action be taken periodically to reaffirm, revise, orwithdraw this standard. Purchasers of American National Standards mayreceive current information on all standards by calling or writing the AmericanNational Standards Institute.American National StandardPublished byAmerican

9、National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2004 by 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

10、, 1250 Eye Street NW, Washington, DC 20005. Printed in the United States of AmericaCAUTION: 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

11、 the publisher have undertaken a patent search in order to identify which, ifany, patents 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 suc

12、h claims has been received. By publication of this standard, no positionis taken with respect 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

13、 nondiscriminatory terms and conditions to applicants desiring to ob-tain such a license. 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 onl

14、y license that may be required to avoid infringement in the use ofthis standard.iContentsPageForeword vii1 Scope and purpose 11.1 Scope. 11.2 Purpose 12 Normative references. 32.1 Reference scope 32.2 Approved references 32.3 References under development. 33 Definitions and notation . 53.1 Definitio

15、ns 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.1 Model overview 134.2 Unit architecture. 134.3 Logical units. 134.4 Requests a

16、nd 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 request blocks (ORBs) 245.2.1 Generic ORB 245.2.2 Dummy ORB 255.2.3 Command block ORBs

17、 265.2.4 Management ORBs . 305.3 Page tables 405.3.1 Overview 405.3.2 Unrestricted page tables 41iiPage5.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 4

18、86 Control and status registers. 496.1 Control and 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.

19、6.3 AGENT_RESET register . 546.6.4 ORB_POINTER register 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 informat

20、ion block 627.4 Root directory 647.4.1 Root directory (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 Dir

21、ectory entries. 677.8.1 Directory entries summary. 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 69iiiPage7.8.7 Command_Set_Revision entry 697.8.8 Firmware_Revision entry 707.8.9 Management_Agent entry 707.8.10 Uni

22、t_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_Number entry 737.8.16 Unit_Unique_ID entry. 747.9 Unit unique ID leaf 748 Access 758.1 Access overview 758.2 Access prot

23、ocols 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 788.4.4 Node handle update after bus reset. 798.4.5 Node handle validation after net update 798.5 Heartbeat . 808.6 Reco

24、nnection . 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 initialization (informative). 839.2.3 Dynamic appends to request lists (informative) . 849.2.4 Fetch agent use by the B

25、IOS (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 Asynchronous data transfer . 909.5 Isochronous data transfer 919.6 Interim and completion status 929.7 Unsolicited status. 931

26、0 Task management . 9510.1 Task management overview 95ivPage10.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 matri

27、x 9911 Isochronous 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

28、 115D AV/C 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 reques

29、t functions . 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 14vPage7 Directly addressed data buffer .

30、 158 Indirectly addressed data buffer (via page table). 169 Components of an isochronous stream (direct-access logical unit). 2010 Address pointer 2311 ORB pointer . 2412 ORB family tree 2413 ORB format 2414 Dummy ORB 2515 Command block ORB (single, non-isochronous buffer descriptor) 2616 Command bl

31、ock ORB (single, isochronous buffer descriptor) . 2817 Command block ORB (dual, non-isochronous buffer descriptors). 2918 Management ORB . 3019 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 Reconne

32、ct ORB . 3726 Node handle ORB 3827 Node handle response. 3928 Logout ORB . 3929 Task management ORB. 4030 Page table element (unrestricted page table) 4131 Page table element (when page_size equals four) 4232 Node selector. 4333 Basic status block format . 4334 Extended status block format. 4435 TRA

33、NSPORT FAILURE format for sbp_status 4636 BUSY_TIMEOUT format 5137 MANAGEMENT_AGENT format 5238 AGENT_STATE format 5439 AGENT_RESET format 5440 ORB_POINTER format 5541 DOORBELL format 56viPage42 UNSOLICITED_STATUS_ENABLE format . 5643 HEARTBEAT_MONITOR format . 5744 FAST_START format. 5845 Configura

34、tion 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 6653 Specifier_ID entry forma

35、t . 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 format 7162 Reconnect_Timeout

36、 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 dummy ORB 8470 Fetch agent state

37、 machine 88viiForeword (This foreword is not part of American National Standard ANSI INCITS 375-2004.)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

38、.) by upper layer protocols such as operating sys-tems or embedded applications. Vendors that wish to 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 sta

39、ndard. Annexes A, B, C, D and E are normative andpart of this standard. Annexes F through J, inclusive, 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 INCIT

40、S Secretariat, Information Tech-nology Industry Council, 1250 I Street NW, Suite 200, Washington, DC 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

41、necessarily imply that all committee members voted forapproval. At the time it approved this standard, INCITS had the following members:Karen Higginbottom, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeApple Computer, Inc. David MichaelFarance, Inc Frank FaranceHewlet

42、t-Packard Company. Karen HigginbottomScott Jameson (Alt.)Steve Mills (Alt.)EIA Edward Mikoski, Jr.Suan Hoyler (Alt.)IBM Corporation . Ronald F. SillettiInstitute for Certification of Computer Professionals. Kenneth M. ZemrowskiThomas Kurihara (Alt.)IEEE . Judith GormanRichard Holleman (Alt.)Robert P

43、ritchard (Alt.)Intel Corporation . Philip WennblomDave Thewlis (Alt.)Microsoft Corporation . Mike KsarFrank 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 i

44、nitiators 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, with particular attention to data interchange formats that permit the use of removable media; definition of a new ORB type to p

45、ermit bi-directional data transfer in the context of a single task; revisions necessary to utilize new Serial Bus features specified by ANSI/IEEE 1394a-2000 and ANSI/IEEE1394b-2002; and clarifications and corrigenda applicable to ANSI INCITS 325-1998. Although SBP-3 has been designed for Serial Bus

46、as currently specified by IEEE 1394, the Technical Committee anticipates that it will be appropriate for use with future extensions to Serial Bus as they are standardized. ANSI INCITS 375-2004 3 2 Normative references 2.1 Reference scope The standards named in this section contain provisions which,

47、through reference in this text, constitute provisions of this American National Standard. At the time of publication, the editions indicated were valid. All standards are subject to revision; parties to agreements based on this American National Standard are encouraged to investigate the possibility

48、 of applying the most recent editions of the standards indicated below. Copies of the following documents can be obtained from ANSI: Approved ANSI standards; Approved and draft regional and international standards (ISO, IEC, CEN/CENELEC and ITUT); and Approved and draft foreign standards (including

49、BIS, JIS and DIN). For further information, contact the ANSI Customer Service Department by telephone at (212) 642-4900, by FAX at (212) 302-1286 or via the world wide web at http:/www.ansi.org. Additional contact information for document availability is provided below as needed. 2.2 Approved references The following approved ANSI, international and regional standards (ISO, IEC, CEN/CENELEC and ITUT) may be obtained from the international and regional organizations that control them. IEC 61883-1 (1998-02), Consumer audio/video equipmentDigital interfacePart 1: General IE