《ANSI-INCITS-325-1998-R2003.pdf》由会员分享，可在线阅读，更多相关《ANSI-INCITS-325-1998-R2003.pdf（99页珍藏版）》请在三一文库上搜索。
1、ANSI INCITS 325-1998 (R2003) (formerly ANSI NCITS 325-1998) for Information Technology Serial Bus Protocol 2 (SBP-2) ANSI NCITS 325-1998 American National Standard for Information Technology Serial Bus Protocol 2 (SBP-2) Secretariat Information Technology Industry Council Approved November 20, 1998
2、American National Standards Institute, Inc. Abstract This 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, Ameri- can National Standard for a High Performance
3、Serial Bus. Approval of an American National Standard requires review by ANSI that the requirements for due process, consensus, and other criteria for approval have been met by the standards developer. Consensus is established when, in the judgement of the ANSI Board of Standards Review, substantial
4、 agreement has been reached by directly and materially affected interests. Substantial agreement means much more than a simple majority, but not necessarily unanimity. Consensus requires that all views and objections be considered, and that a concerted effort be made towards their resolution. The us
5、e of American National Standards is completely voluntary; their existence does not in any respect preclude anyone, whether he has approved the standards or not, from manufacturing, marketing, purchasing, or using products, processes, or procedures not conforming to the standards. The American Nation
6、al Standards Institute does not develop standards and will in no circumstances give an interpretation of any American National Standard. Moreover, no person shall have the right or authority to issue an interpretation of an American National Standard in the name of the American National Standards In
7、stitute. Requests for interpretations should be addressed to the secretariat or sponsor whose name appears on the title page of this standard. CAUTION NOTICE: This American National Standard may be revised or withdrawn at any time. The procedures of the American National Standards Institute require
8、that action be taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American National Standards may receive current information on all standards by calling or writing the American National Standards Institute. American National Standard Published by American National Stan
9、dards Institute, Inc. 11 West 42nd Street, New York, NY 10036 Copyright 1999 by Information Technology Industry Council (ITI) All rights reserved. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without prior written permission of ITI, 1250
10、Eye Street NW, Washington, DC 20005. Printed in the United States of America CAUTION: 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
11、 publisher have undertaken a patent search in order to identify which, if any, patents may apply to this standard. As of the date of publication of this standard, following calls for the identification of patents that may be required for the implementation of the standard, notice of one or more such
12、 claims has been received. By publication of this standard, no position is taken with respect to the validity of this claim or of any rights in connection therewith. The known patent holder(s) has (have), however, filed a statement of willingness to grant a license under these rights on reasonable a
13、nd 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 is made or implied that this is th
14、e only license that may be required to avoid infringement in the use of this standard. i Contents Page Forewordv 1Scope and purpose. 1 1.1Scope 1 1.2Purpose 1 2Normative references . 2 2.1Approved references 2 2.2References under development 2 3Definitions and notation 3 3.1Definitions. 3 3.1.1 Conf
15、ormance 3 3.1.2 Glossary 3 3.1.3 Abbreviations 6 3.2Notation 6 3.2.1 Numeric values. 6 3.2.2 Bit, byte and quadlet ordering. 6 3.2.3 Register specifications 7 3.2.4 State machines. 9 4Model (informative). 11 4.1Unit architecture . 11 4.2Logical units 11 4.3Requests and responses 11 4.4Data buffers 1
16、2 4.5Target agents 14 4.6Ordered and unordered execution 15 5Data structures. 16 5.1Operation request blocks (ORBs) 17 5.1.1 Dummy ORB. 18 5.1.2 Command block ORBs. 18 5.1.3 Management ORBs 20 5.2Page tables. 27 5.2.1 Unrestricted page tables. 28 5.2.2 Normalized page tables 28 5.3Status block 29 5.
17、3.1 Request status 31 5.3.2 Unsolicited device status 33 6Control and status registers 34 6.1Core registers . 34 6.2Serial Bus-dependent registers 34 6.3MANAGEMENT_AGENT register. 35 6.4Command block agent registers. 35 6.4.1 AGENT_STATE register. 36 6.4.2 AGENT_RESET register 37 6.4.3 ORB_POINTER r
18、egister. 37 6.4.4 DOORBELL register . 38 6.4.5 UNSOLICITED_STATUS_ENABLE register 39 ii Page 7Configuration ROM. 40 7.1Power reset initialization. 40 7.2Bus information block . 41 7.3Root directory . 42 7.3.1 Module_Vendor_ID entry 42 7.3.2 Node_Capabilities entry 42 7.3.3 Unit_Directory entry 42 7.
19、4Unit directory. 43 7.4.1 Unit_Spec_ID entry. 43 7.4.2 Unit_SW_Version entry 43 7.4.3 Command_Set_Spec_ID entry. 44 7.4.4 Command_Set entry. 44 7.4.5 Command_Set_Revision entry. 44 7.4.6 Firmware_Revision entry 45 7.4.7 Management_Agent entry 45 7.4.8 Unit_Characteristics entry. 45 7.4.9 Reconnect_T
20、imeout entry. 46 7.4.10Logical_Unit_Directory entry. 46 7.4.11Logical_Unit_Number entry 46 7.4.12Unit_Unique_ID entry . 47 7.5Logical unit directory. 47 7.5.1 Command_Set_Spec_ID entry. 48 7.5.2 Command_Set entry. 48 7.5.3 Command_Set_Revision entry. 48 7.5.4 Logical_Unit_Number entry 48 7.6Unit uni
21、que ID leaf 48 8Access 50 8.1Access protocols. 50 8.2Login. 50 8.3Reconnection 51 8.4Logout. 52 9Command execution. 53 9.1Requests and request lists . 53 9.1.1 Fetch agent initialization (informative) 53 9.1.2 Dynamic appends to request lists (informative) 54 9.1.3 Fetch agent use by the BIOS (infor
22、mative). 55 9.1.4 Fetch agent state machine . 55 9.2Data transfer. 58 9.3Completion status. 58 9.4Unsolicited status 59 10Task management 60 10.1Task sets 60 10.2Basic task management model. 60 10.3Error conditions. 61 10.4Task management requests. 61 10.4.1Abort task 61 10.4.2Abort task set 62 10.4
23、.3Logical unit reset. 63 10.4.4Target reset 63 10.5Task management event matrix . 64 iii Page Tables 1Data transfer speeds.20 2Management request functions.21 F.1SAM-2 Service responses.83 Figures 1Bit ordering within a byte.7 2Byte ordering within a quadlet.7 3Quadlet ordering within an octlet.7 4C
24、SR specification example.8 5State machine example.10 6Linked list of ORBs.12 7Directly addressed data buffer13 8Indirectly addressed data buffer (via page table)13 9Address pointer.16 10ORB pointer 16 11ORB family tree.17 12ORB format.17 13Dummy ORB.18 14Command block ORB .19 15Management ORB 21 16L
25、ogin ORB.22 17Login response23 18Query logins ORB.24 19Query logins response format.24 20Reconnect ORB25 21Logout ORB 26 22Task management ORB27 23Page table element (unrestricted page table).28 24Page table element (when page_size equals four).28 25Status block format .30 26TRANSPORT FAILURE format
26、 for sbp_status.32 27MANAGEMENT_AGENT format.35 28AGENT_STATE format.36 29AGENT_RESET format.37 30ORB_POINTER format.38 iv Page 31DOORBELL format. 39 32UNSOLICITED_STATUS_ENABLE format 39 33Configuration ROM hierarchy. 40 34Bus information block format 41 35Module_Vendor_ID entry format. 42 36Node_C
27、apabilities entry format 42 37Unit_Directory entry format. 43 38Unit_Spec_ID entry format . 43 39Unit_SW_Version entry format. 43 40Command_Set_Spec_ID entry format 44 41Command_Set entry format 44 42Command_Set_Revision entry format 44 43Firmware_Revision entry format. 45 44Management_Agent entry f
28、ormat. 45 45Unit_Characteristics entry format . 45 46Reconnect_Timeout entry format . 46 47Logical_Unit_Directory entry format . 46 48Logical_Unit_Number entry format. 46 49Unit_Unique_ID entry format 47 50Unit unique ID leaf format. 48 51Fetch agent initialization with a dummy ORB . 54 52Fetch agen
29、t state machine . 56 B.1SCSI command block ORB 67 B.2SCSI control byte 67 B.3Status block format for SCSI sense data 68 C.1Set password ORB. 73 D.1Basic configuration ROM 75 D.2SCSI configuration ROM 77 Annexes AMinimum Serial Bus node capabilities 65 BSCSI command and status encapsulation 67 CSecur
30、ity extensions. 72 DSample configuration ROM. 75 ESerial Bus transaction error recovery . 79 FSCSI Architecture Model conformance. 81 v Foreword (This foreword is not part of American National Standard ANSI NCITS 325-1998.) This standard defines a transport protocol within the domain of Serial Bus,
31、as de- scribed in ANSI/IEEE 1394-1995, that is designed to permit efficient, peer-to-peer operation of input output devices (disks, tapes, printers, etc.) by upper-layer proto- cols such as operating systems or embedded applications. Vendors that wish to im- plement devices that connect to Serial Bu
32、s may follow the requirements of this and other normatively referenced standards to manufacture an SBP-2 compliant device. This standard was developed by T10 during 1996 and through early 1998. Although some early SBP mock-up devices were demonstrated in 1993, significant proof-of- concept, in the f
33、orm of prototype implementations, has proceeded contemporane- ously with the development of this standard. This standard bears the name SBP-2 because there was an ancestral standard, Seri- al Bus Protocol (SBP), which has since been withdrawn by ANSI. SBP was extant during most of the development of
34、 this standard, which was consequently called SBP-2 to avoid confusion. There are six annexes in this standard. Annexes A, B and C are normative and part of this standard. Annexes D, E and F are informative and are not considered part of this standard. Requests for interpretation, suggestions for im
35、provement and addenda, or defect re- ports are welcome. They should be sent to the NCITS Secretariat, Information Tech- nology Industry Council, 1250 Eye Street, NW, Suite 200, Washington, DC 20005- 3922. This standard was processed and approved for submittal to ANSI by National Com- mittee for Info
36、rmation Technology Standardization (NCITS). Committee approval of this standard does not necessarily imply that all committee members voted for ap- proval. At the time it approved this standard, NCITS had the following members: Karen Higginbottom, Chair David Michael, Vice-Chair Monica Vago, Secreta
37、ry Organization RepresentedName of Representative AMP, Inc.John Hill Charles Brill (Alt.) Apple Computer, Inc.David Michael Jerry Kellenbenz (Alt.) AT The protocol should enable the initiator to form an arbitrarily large set of tasks without consideration of implementation limits in the target; The
38、protocol should allow the initiator to dynamically add tasks to this set while the target is active in execution of earlier tasks. The addition of new tasks should not interfere with the targets processing of tasks currently active; Although the protocol should enable varying levels of features and
39、performance in target implemen- tations, strong focus should be kept on a minimal set deemed adequate for entry-level environ- ments; Within the constraints posed by the preceding goal, the hardware and software design of the initiator should not be unduly affected by variations in target capabiliti
40、es; In order to promote the scalability of aggregate system performance, the protocol should distribute the DMA context from the initiator adapter to the target devices. Although SBP-2 has been designed for Serial Bus as currently specified by ANSI/IEEE 1394, the Techni- cal Committee anticipates th
41、at it will be appropriate for use with future extensions to Serial Bus as they are standardized. ANSI NCITS 325-1998 2 2 Normative references The standards named in this clause contain provisions which, through reference in this text, constitute provisions of this American National Standard. At the
42、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 of applying the most recent editions of the standards indicated below. Copies of the following d
43、ocuments can be obtained from ANSI: Approved ANSI standards; Approved and draft regional and international standards (ISO, IEC, CEN/CENELEC and ITU-T); and Approved foreign standards (including BIS, JIS and DIN). For further information, contact the ANSI Customer Service Department by telephone at (
44、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.1 Approved references ANSI/IEEE 1394-1995, High Performance Serial Bus ANSI/ISO/IEC 9899-1990 (R1997), Programming Language
45、s - C ISO/IEC 13213:1994, Control and Status Register (CSR) Architecture for Microcomputer Buses1) 2.2 References under development At the time of publication, the following referenced standards were still under development. IEEE P1394a, Draft Standard for a High Performance Serial Bus (Supplement)2
46、) BSR X3 PN 1157-D, Information Technology - SCSI Architecture Model 2 (SAM-2)3) BSR NCITS PN 1236-D, Information Technology - SCSI Primary Commands 2 (SPC-2)3) _ _ _ _ _ _ 1)Available from the American National Standards Institute, 11 West 42nd Street, New York, NY 10036. 2)Available from the Insti
47、tute of Electrical and Electronics Engineers, 445 Hoes Lane, P.O. Box 1331, Piscataway, NJ 08855-1331. 3)Available from the National Committee for Information Technology Standards, 1250 Eye Street, NW, Suite 200, Washington, DC 20005-3922. ANSI NCITS 325-1998 3 3 Definitions and notation 3.1 Definit
48、ions 3.1.1 Conformance Several keywords are used to differentiate levels of requirements and optionality, as follows: 3.1.1.1 expected: A keyword used to describe the behavior of the hardware or software in the design models assumed by this standard. Other hardware and software design models may als
49、o be imple- mented. 3.1.1.2 ignored: A keyword that describes bits, bytes, quadlets, octlets or fields whose values are not checked by the recipient. 3.1.1.3 may: A keyword that indicates flexibility of choice with no implied preference. 3.1.1.4 reserved: A keyword used to describe objectsbits, bytes, quadlets, octlets and fieldsor the code values assigned to these objects in cases where either the object or the code value is set aside for future standardization. Usage and interpretation may be specified by future extensions to this or other standards. A reserved obj