1、American National StandardDeveloped byfor Information Technology AT Attachment 8 ATA/ATAPI Serial Transport(ATA8-AST)INCITS 493-2012INCITS 493-2012INCITS 493-2012American National Standardfor Information Technology AT Attachment 8 ATA/ATAPI Serial Transport(ATA8-AST)SecretariatInformation Technology
2、 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 interface for systems manufacturers, system int
3、egrators, software suppliers, and suppliers of intelligent storage devices.This standard is not intended to require changes to presently installed devices or existing software.Approval of an American National Standard requires review by ANSI that therequirements for due process, consensus, and other
4、 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 affected interests. Substantial agreement means much more thana simple majority, but n
5、ot 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; theirexistence does not in any respect preclude anyone, whether he has approvedthe stan
6、dards 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 no circumstances give an interpretation of any American NationalStandard. Moreover, no p
7、erson 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 secretariat or sponsor whose name appears on the titlepage of this standard.CAUTION NOTIC
8、E: 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 standard. Purchasers of American National Standards mayreceive current information on a
9、ll 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 2012 by Information Technology Industry Council (ITI)All rights reserved.No part of this publi
10、cation 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: The developers of this standard have requested that holders of patents that may bereq
11、uired for the implementation of the standard disclose such patents to the publisher. However,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 cal
12、ls for the identification of patents that may be required for the implementation ofthe 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 requ
13、ired to avoid infringement in the use of this standard.iContentsPage1 Scope . 12 Normative references . 32.1 General . 32.2 Approved references 32.3 References under development . 32.4 Other references . 33 Definitions, abbreviations, and conventions . 53.1 Definitions and abbreviations . 53.2 Symbo
14、ls 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 93.3.9 Byte, word, DWord, and QWord Relationships . 114 Mapping AAM and ACS-2 to AST
15、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 PIO Setup FIS mapping 144.2.4 ACS-2 Normal Output and Error Output to SDB FIS mappi
16、ng 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 bit . 174.4.5 SLEEP command and PM3:Sleep state . 174.5 ATA8-AAM Command Events 174.5
17、.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 data and ACS-2 IDENTIFY PACKET DEVICE data . 194.8.1 Differences in IDENTIFY DEVICE dat
18、a 194.8.2 Differences in IDENTIFY PACKET DEVICE data . 19iiTablesPageTable 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 4
19、8-Bit Normal/Error Mapping for RDH FIS 14Table 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-AA
20、M protocols to SATA protocols 18Table 13 IDENTIFY DEVICE data definitions and recommendation 19Table 14 IDENTIFY PACKET DEVICE data definitions and recommendation 19iiiFiguresPageFigure 1 ATA document relationships . 2Figure 2 State diagram convention . 9Figure 3 Byte, word, DWord and QWord relation
21、ships 11ivForeword (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.Re
22、quests 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 submitt
23、al 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 RepresentativeAd
24、obe 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 Schoec
25、hle (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 (Al
26、t.)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.)vOrganization Represented Name of RepresentativeNational Institute of Sta
27、ndards andb) documenting the transport dependent components found in the ATA8 family of standards. SATA 2.6 and SATA 3.0 specify the 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), incl
28、uding connectors and cables;c) the electrical characteristics of the interconnecting signals; andd) the logical characteristics of the interconnecting signals. This standard specifies relationships between this standard and multiple versions of SATA. This standard specifies:a) the mapping of ACS-2 c
29、ommand fields, normal returns, and error returns to SATA 2.6 and SATA 3.0 FIS fields;b) ACS-2 transport specific fields; andc) ATA8-AAM transport specific components.INCITS 493-20122Figure 1 shows the relationship of this standard to the other standards and related projects in the ATA and SCSI famil
30、ies 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 Transport(ATA8-APT)AT Attachment 8Serial
31、Transport(ATA8-AST)ATA/ATAPI Command Set 2 (ACS-2)Related host standardsand specificationsOther relateddevicespecificationsINCITS 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
32、 standard. At the time of publication, the editions indicated were valid. All standards are 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 l
33、isted in this subclause may be obtained from ANSI: a) Approved ANSI standards; b) approved 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
34、(phone), 212-302-1286 (fax), or via the World Wide Web at http:/www.ansi.org.Additional availability 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 subclas
35、s were in development at the time of this publication. For information on the current status 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 regar
36、ding availability, contact the indicated organization.Serial ATA Revision 2.6 (SATA 2.6)Copies 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-86
37、1AT Attachment-8 ATA Command Set (ATA8-ACS) ANSI INCITS 452-2008AT Attachment with Packet 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 Transpor
38、t (ATA8-APT) INCITS 1698DINCITS 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.orgINCITS 493-201253 Definitions, abbreviations, and conventions3.1 Definitions and abbreviations3.1.1 28-bit command: A
39、command which uses Features (7:0), Count (7:0), 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 imp
40、lementing the ATA General feature set.3.1.4 ATA8-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
41、that is not a device management function (e.g., 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
42、 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 data transfer between a host port and the device port which does not i
43、nvolve application client intervention.3.1.13 DWord: A sequence of four contiguous bytes considered as a unit. See 3.3.9.3.1.14 Frame Information Structure: The frame information structure for the serial ATA interface. See SATA.3.1.15 hardware reset: The routines performed by the device server and t
44、he device port in a device after a hardware reset event occurs. See ATA8-AAM.3.1.16 host: Originator of commands and device management functions. See ATA8-AAM.3.1.17 Nexus Loss Event: A transport specific event where the host port is no longer in communication with a device port (e.g., a device was
45、removed). See 4.6.3.1.18 power-on reset: The host specific routines performed by the application client and the host port or the routine performed by a device server and the device port after detecting a power-on event. See ATA8-AAM.3.1.19 QWord: A sequence of eight contiguous bytes considered as a
46、unit. See 3.3.9.3.1.20 Register Device to Host FIS: A FIS used to transfer register information from the device to the host. See SATA.3.1.21 Register Host to Device FIS: A FIS used to transfer register information from the host to the device. See SATA.INCITS 493-201263.1.22 PIO Setup FIS: A FIS used
47、 to transfer PIO setup information from the device to the host. See SATA.3.1.23 SATA: SATA 2.6 or SATA 3.0.3.1.24 Set Device Bits FIS: A FIS used to transfer information from the device to the host to set device bits in the host. See SATA.3.1.25 software reset: The routines performed by the device s
48、erver and the device port in a device after a soft-ware reset event. See ATA8-AAM. 3.1.26 transport: A serial transport or a parallel transport.3.1.27 word: A sequence of two contiguous bytes considered as a unit. See 3.3.9.3.2 Symbols and abbreviations3.3 Conventions3.3.1 OverviewLowercase is used
49、for words having the normal English language meaning. Certain words and terms used in this standard have a specific meaning beyond the normal English language meaning. These words and terms are defined either in clause 3 or in the text where they first appear.The names of abbreviations, commands, fields, and acronyms used as signal names are in all uppercase (e.g., IDENTIFY DEVICE). Fields containing only one bit are usually referred to as the “name” bit instead of the “name” field. (See 3.3.6 for the naming conven
