1、American National StandardDeveloped byfor Information Technology AT Attachment 8 ATA/ATAPI Serial Transport(ATA8-AST)INCITS 493-2012INCITS 493-2012Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without lic
2、ense from IHS-,-,-Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS 493-2012American National Standardfor Information Technology AT Attachment 8 ATA/ATAPI Serial Transport(
3、ATA8-AST)SecretariatInformation Technology Industry CouncilApproved April 23, 2012American National Standards Institute, Inc.AbstractThis standard specifies the AT Attachment Interface between host systems and storage devices using a serial electrical interface. It provides a common attachment inter
4、face for systems manufacturers, system integrators, software suppliers, and suppliers of intelligent storage devices.This standard is not intended to require changes to presently installed devices or existing software.Copyright American National Standards Institute Provided by IHS under license with
5、 ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-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
6、 when, in the judgement of the ANSI 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
7、, and that a concerted effort be madetowards 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, o
8、r procedures not conforming to the standards.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 Nation
9、al Standard in the name of the AmericanNational 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 procedur
10、es of the American National StandardsInstitute 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 Na
11、tional StandardPublished byAmerican National Standards Institute, Inc.25 West 43rd Street, New York, NY 10036Copyright 2012 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,wit
12、hout prior written permission of ITI, 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 berequired for the implementation of the standard disclose such patents to the publisher. Ho
13、wever,neither the developers nor the publisher have undertaken a patent search in order to identifywhich, if any, patents may apply to this standard. As of the date of publication of this standardand following calls for the identification of patents that may be required for the implementation ofthe
14、standard, no such claims have been made. No further patent search is conducted by the de-veloper or publisher in respect to any standard it processes. No representation is made or impliedthat licenses are not required to avoid infringement in the use of this standard.Copyright American National Stan
15、dards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iContentsPage1 Scope . 12 Normative references . 32.1 General . 32.2 Approved references 32.3 References under development . 32.4 Other references . 33 Definitio
16、ns, abbreviations, and conventions . 53.1 Definitions and abbreviations . 53.2 Symbols and abbreviations 63.3 Conventions 63.3.1 Overview . 63.3.2 Precedence . 73.3.3 Lists . 73.3.4 Keywords 73.3.5 Numbering . 83.3.6 Bit conventions 93.3.7 Number range convention . 93.3.8 State diagram conventions 9
17、3.3.9 Byte, word, DWord, and QWord Relationships . 114 Mapping AAM and ACS-2 to AST 124.1 Mapping Overview 124.2 SATA field mappings 124.2.1 ACS-2 command field to SATA RHD FIS mapping . 124.2.2 ACS-2 Normal Output and Error Output to RDH FIS mapping . 134.2.3 ACS-2 Normal Output and Error Output to
18、 PIO Setup FIS mapping 144.2.4 ACS-2 Normal Output and Error Output to SDB FIS mapping 154.3 Parallel ATA Emulation . 154.4 ACS-2 Transport Specific Fields 164.4.1 Status field bits 164.4.2 Transport specific Error field bit 164.4.3 Device Control field bits 174.4.4 Transport specific Device field b
19、it . 174.4.5 SLEEP command and PM3:Sleep state . 174.5 ATA8-AAM Command Events 174.5.1 Command aborted 174.5.2 Command acceptance 174.5.3 Command completion . 174.6 ATA8-AAM Protocols 184.7 ATA8-AAM Resets . 184.7.1 Software reset . 184.7.2 Transport Specific Resets . 184.8 ACS-2 IDENTIFY DEVICE dat
20、a and ACS-2 IDENTIFY PACKET DEVICE data . 194.8.1 Differences in IDENTIFY DEVICE data 194.8.2 Differences in IDENTIFY PACKET DEVICE data . 19Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license f
21、rom IHS-,-,-iiTablesPageTable 1 Numbering conventions . 9Table 2 28-Bit Command Mapping for SATA RHD FIS 12Table 4 28-Bit Normal/Error Mapping for RDH FIS 13Table 3 48-Bit Command Mapping for SATA RHD FIS 13Table 6 28-bit PIO Setup FIS mapping 14Table 5 48-Bit Normal/Error Mapping for RDH FIS 14Tabl
22、e 8 48-Bit Normal/Error Mapping for SDB FIS . 15Table 7 48-bit PIO Setup FIS mapping 15Table 9 Transport specific Status field bits . 16Table 10 Transport specific Error field bit . 16Table 11 Transport specific Device field bit 17Table 12 Mapping ATA8-AAM protocols to SATA protocols 18Table 13 IDEN
23、TIFY DEVICE data definitions and recommendation 19Table 14 IDENTIFY PACKET DEVICE data definitions and recommendation 19Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-iiiFigure
24、sPageFigure 1 ATA document relationships . 2Figure 2 State diagram convention . 9Figure 3 Byte, word, DWord and QWord relationships 11Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS
25、-,-,-ivForeword (This foreword is not part of American National Standard INCITS 493-2012.)This standard documents the transport-specific components of the ATA Serial Transport in the ATA technologies referenced by the ATA/ATAPI Architecture Model standard and the ATA/ATAPI Command Set standard.Reque
26、sts for interpretation, suggestions for improvement or addenda, or defect reports are welcome. They should be sent to InterNational Committee for Information Technology Standards (INCITS), ITI, 1101 K Street, NW, Suite 610, Washington, DC 20005.This standard was processed and approved for submittal
27、to ANSI by INCITS. Committee approval of this standard does not necessarily imply that all committee members voted for its approval. At the time it approved this standard, INCITS had the following members:Don Wright, ChairJennifer Garner, SecretaryOrganization Represented Name of RepresentativeAdobe
28、 Systems, Inc. Scott Foshee Steve Zilles (Alt.)AIM Global, Inc. . Steve HallidayApple Computer, Inc. . Helene WorkmanDavid Singer (Alt.)Distributed Management Task Force John Crandall Jeff Hilland (Alt.)EMC Corporation . Gary RobinsonStephen Diamond (Alt.)Farance, Inc. Frank FaranceTimothy Schoechle
29、 (Alt.)GS1 US . Frank SharkeyCharles Biss (Alt.)Hewlett-Packard Company Karen Higginbottom Paul Jeran (Alt.)IBM Corporation Alexander TarpinianRobert Weir (Alt.)Arnaud Le Hors (Alt.)Debra Boland (Alt.)Steve Holbrook (Alt.)Gerald Lane (Alt.)IEEE . Jodie HaaszTerry deCourcelle (Alt.)Bob Labelle (Alt.)
30、Intel Philip Wennblom Grace Wei (Alt.)Stephen Balogh (Alt.)Lexmark International. Don WrightDwight Lewis (Alt.)Paul Menard (Alt.)Jerry Thrasher (Alt.)Microsoft Corporation . Jim Hughes Dick Brackney (Alt.)John Calhoun (Alt.)Copyright American National Standards Institute Provided by IHS under licens
31、e with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-vOrganization Represented Name of RepresentativeNational Institute of Standards andb) documenting the transport dependent components found in the ATA8 family of standards. SATA 2.6 and SATA 3.0 specify the
32、 following: a) the mapping of ACS-2 command blocks to SATA 3.0 FIS fields;b) the physical interconnection between Serial ATA host and Serial ATA storage device(s), including connectors and cables;c) the electrical characteristics of the interconnecting signals; andd) the logical characteristics of t
33、he interconnecting signals. This standard specifies relationships between this standard and multiple versions of SATA. This standard specifies:a) the mapping of ACS-2 command fields, normal returns, and error returns to SATA 2.6 and SATA 3.0 FIS fields;b) ACS-2 transport specific fields; andc) ATA8-
34、AAM transport specific components.Copyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS 493-20122Figure 1 shows the relationship of this standard to the other standards and rel
35、ated projects in the ATA and SCSI families of standards and specifications. SATA 2.6 and SATA 3.0 specifications are not defined within the framework of this standard. Figure 1 ATA document relationships ATAttachment 8Architecture Model(ATA8-AAM)Packet deliveredcommand setsAT Attachment 8Parallel Tr
36、ansport(ATA8-APT)AT Attachment 8Serial Transport(ATA8-AST)ATA/ATAPI Command Set 2 (ACS-2)Related host standardsand specificationsOther relateddevicespecificationsCopyright American National Standards Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permit
37、ted without license from IHS-,-,-INCITS 493-201232 Normative references 2.1 GeneralThe standards listed in 2.2, 2.3, and 2.4 contain provisions that, through reference in the text, constitute provisions of this standard. At the time of publication, the editions indicated were valid. All standards ar
38、e subject to revision, and parties to agreements based on this standard are encouraged to investigate the possibility of applying the most recent editions of the standards listed in this clause. The standards listed in this subclause may be obtained from ANSI: a) Approved ANSI standards; b) approved
39、 and draft international and regional standards (ISO and IEC); and c) approved and draft foreign standards (e.g., JIS and DIN). For further information, contact ANSI Customer Service Department at 212-642-4900 (phone), 212-302-1286 (fax), or via the World Wide Web at http:/www.ansi.org.Additional av
40、ailability contact information is provided below as needed.2.2 Approved referencesAdditional information may be available at http:/www.t13.org2.3 References under developmentThe standards listed in this subclass were in development at the time of this publication. For information on the current stat
41、us of the draft standards, or regarding availability, contact INCITS.2.4 Other referencesThe following specifications are also referenced. For information on the current status of the listed documents, or regarding availability, contact the indicated organization.Serial ATA Revision 2.6 (SATA 2.6)Co
42、pies of the SATA Revision 2.6 specification published by SATA-IO may be obtained at http:/www.sata-io.orgName ReferenceAT Attachment-8 ATA/ATAPI Architecture Model (ATA8-AAM)ANSI INCITS 451-2008ISO/IEC 14776-861AT Attachment-8 ATA Command Set (ATA8-ACS) ANSI INCITS 452-2008AT Attachment with Packet
43、Interface - 6 (ATA/ATAPI 6) ANSI INCITS 361-2002ATA Host Adapter Standards (HBA) ANSI INCITS 370-2004Name ReferenceAT Attachment-8 ATA Command Set 2 (ACS-2) INCITS 482AT Attachment 8 ATA/ATAPI Parallel Transport (ATA8-APT) INCITS 1698DCopyright American National Standards Institute Provided by IHS u
44、nder license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS 493-20124Serial ATA Revision 3.0 (SATA 3.0)Copies of the SATA Revision 3.0 specification published by SATA-IO may be obtained at http:/www.sata-io.orgCopyright American National Standards
45、 Institute Provided by IHS under license with ANSI Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-INCITS 493-201253 Definitions, abbreviations, and conventions3.1 Definitions and abbreviations3.1.1 28-bit command: A command which uses Features (7:0), Count (7:0),
46、LBA (27:0), Device (7:0), and Command (7:0) to specify arguments. See 4.1.3.1.2 48-bit command: A command which uses Features (15:0), Count (15:0), LBA (47:0), Device (7:0), and Command (7:0) to specify arguments. See 4.1.3.1.3 ATA device: A device implementing the ATA General feature set.3.1.4 ATA8
47、-AST device: A device that complies with this standard.3.1.5 ATAPI device: A device implementing the PACKET feature set.3.1.6 byte: A sequence of eight contiguous bits considered as a unit. See 3.3.9.3.1.7 command: A unit of work performed by a device that is not a device management function (e.g.,
48、a data transfer operation). See ATA8-AAM.3.1.8 command aborted: A response by a device reporting that a command has aborted. See 4.5.1.3.1.9 command acceptance: A response by a device reporting that a command has been accepted. See 4.5.2.3.1.10 command completion: A response by a device reporting that a command has completed. See 4.5.3.3.1.11 device: A storage peripheral that processes commands and device management functions. See ATA8-AAM.3.1.12 DMA data transfer: A method of d
