Working Draft Project American National T13/1699-D Standard: Revision 3f December 11, 2006
Working Draft Project American National T13/1699-D Standard: Revision 3f December 11, 2006
Working Draft Project American National T13/1699-D Standard: Revision 3f December 11, 2006
T13/1699-D
Revision 3f December 11, 2006
T13/1699-D Revision 3f
ii
T13/1699-D Revision 3f
Points of Contact
T13 Chair Dan Colgrove Hitachi Global Storage Technologies 2903 Carmelo Dr Henderson, NV 89502 Tel: 702-614-6119 Fax: 702-614-7955 INCITS Secretariat NCITS Secretariat 1250 Eye Street, NW Suite 200 Washington, DC 20005 Email: INCITS@ITIC.ORG T13 Reflector See the T13 Web Site at http://www.t13.org for reflector information. T13 Web Site http://www.t13.org T13 Anonymous FTP Site ftp.t13.org Document Distribution INCITS Online Store managed by Techstreet 1327 Jones Drive Ann Arbor, MI 48105 or Global Engineering 15 Inverness Way East Englewood, CO 80112-5704 American National Standard for Information Technology http://www.techstreet.com/incits.html Telephone: 1-734-302-7801 or 1-800-699-9277 Facsimile: 1-734-302-7811 T13 Vice chair Jim Hatfield Seagate Technology 389 Disc Drive Longmont CO 80503 Tel: 720-684-2120 Fax: 720-684-2711 Tel: 202-737-8888 Fax: 202-638-4922
iii
T13/1699-D Revision 3f
Draft
Secretariat
ABSTRACT
This standard specifies the AT Attachment command set between host systems and storage devices. It provides a common command set for systems manufacturers, system integrators, software suppliers, and suppliers of intelligent storage devices. It includes the PACKET feature set implemented by devices commonly known as ATAPI devices. This standard maintains a high degree of compatibility with the AT Attachment Interface with Packet Interface - 7 (ATA/ATAPI-7) volume 1, INCITS 397-2004, and while providing additional functions, is not intended to require changes to devices or software that comply with previous T13 standards.
Draft
iv Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS)
T13/1699-D Revision 3f
of an American National Standard requires verification by ANSI that the American Approval requirements for due process, consensus, and other criteria for approval have been met by standards developer. Consensus is established when, in the judgment of the ANSI Board National the of Standards Review, substantial agreement has been reached by directly and materially Standard 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 effort be made towards their resolution.
The use 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 National Standards Institute does not develop standards and will in no circumstances give interpretation on 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 Institute. 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 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.
The patent statement goes here. If no patents have been disclosed place the statement in 5.5.2 shall be used. If any patents have been disclosed place the statement in 5.5.3 shall be used.
Published by
American National Standards Institute 11 W. 42nd Street, New York, New York 10036
Copyright 2006 by Information Technology Industry Council (ITI). All rights reserved. No part of this publication may by reproduced in any form, in an electronic retrieval system or otherwise, without prior written permission of ITI, 1250 Eye Street NW, Suite 200, Washington, DC 20005. Printed in the United States of America
T13/1699-D Revision 3f
vi
T13/1699-D Revision 3f
Document Status
Document e06122 is the issues list for this draft. e06122 contains a list of the issues associated with the document, an issue number that remains assigned to the issue for the life of document development, a resolution to the issue, an owner for the issue, and a disposition for the issue. All major changes associated with this draft starting with Rev 3b are first documented in e06122 and given a number. This includes proposals which are targeted for inclusion into this draft. Rev 0 Date August 17, 2004 Revision History (part 1 of 16) Description Initial revision created from ATA/ATAPI-7 Volume 1 (1532D Rev 4b). Removed 3 volume structure and changed abstract to reflect a command set document Removed sections on signal, bit, and timing conventions Removed clause 5, I/O register descriptions Kept informative annexs A-C Restructured all commands to conform to format agreed to in e04139r4. Added a section defining status bits Added a section defining error bits Added a section describing protocols Added a section describing interrupt reason Incorporated single log table e04143r0 table. Did not add wording to status that host VS pages are common between SMART and GPL. Removed prohibited statements from command definitions. These reside in the feature set definitions. Replaced duplicate Normal Outputs tables with a see clause to the first usage. Replaced many Error Outputs with a see clause. Stripped unused informative references Changed the definition of ordered and unordered lists to make the numeric form ordered. Changed all the lists to conform to the changes in #2 Reserved 5Ch-5Fh for TCG. This was done by added command headers and a reserved statement in the command section. Also marked the commands with T in the command matrix table. Moved Normal and Error Outputs to their own section. Commands now have a hotlink to the tables. Moved IDENTIFY (PACKET) DATA to its own section (Input Data) Changed more of the titles to be consistent with the front cover. Deleted unused definitions Changed the General feature set to only apply to non-packet devices Changed the packet feature set to include all the commands in the packet feature set. The command prohibitions are now found in the feature set description and not with each command. Integrated e04127r0 This makes SATA signatures reserved with no description.
1) 2) 3) 4) 5) 1) 2) 3) 4) 5) 6) 7)
September 7, 2004
1a
October 6, 2004
1b
vii
T13/1699-D Revision 3f
December 11, 2006 Revision History (part 2 of 16) Description Added proposal e04143r1 Notes that the Host Vendor Specific pages are common to both SMART READ LOG and READ LOG EXTENDED Added e04130r2 Tightens the definition of SMART first polling time. Also adds a field that enables longer times. Added proposal e05103r0 Changes the features register to log page specific for read and write log commands Added e04153r1 Historical annex of command documentation to Annex B Added e05102r1 as amended Reserves some set features and DCO fields as vendor specific Added back in FEATURE SET Clause in front of the description Added code 1Dh to IDENTFY DEVICE for ATA/ATAPI-7 Table 14. Added placeholder for reporting alignment. Updated SET FEATURES table 41 to include reserved entries instead of just saying all other entries are reserved. Partially Incorporated e04129r5. Assigned Set Features 0Bh and 8Bh for the enable and disable capability. Had to make several modifications to the proposal to fill in missing pieces. Unable to fill in IDENTIFY DEVICE info, data is incomplete. Stopped incorporation Modified Selective self-test description last sentence to be more clear. Updated definition based on WG review. Integrated e05133r3. This conflicts with the definition of IDENTIFY DEVICE which is defined to not return an error. Incorporated e04129r6. Assigned IDENTIFY DEVICE words 210-213 and DCO word 7 bit 14.
Rev 1c
1) 2) 3) 4) 5) 6) 1) 2) 3) 4)
1d
1e
1) 2) 3) 4)
viii
T13/1699-D Revision 3f Revision History (part 3 of 16) Description Added several technical reports to the approved references. They need to be there since they are mentioned in the body of the document. Updated DCO to refer to TR-37 (TLC) for word 7 bit 10. Updated the Scope to match ATA8-AAM Replaced sector with logical sector in many places Replaced all references to the Features register with features field. Replaced all references to the Sector Count register with Count field. There are some places that use the count field in calculations. These places refer to the register. I have chosen to keep the word field although I think it may read better just saying count. Replaced archaic references to sector number register with references to the LBA field. Replaced references to LBA Low, LBA Mid, and LBA high to LBA field. Replaced all references to device/head or device register Deleted references to the device control register. Updated overview in clause 7. Updated security commands to have an output data structure where appropriate Updated SETMAX commands to have an output data structure where appropriate. Removed remaining hardware references from commands. Transport documents will have to reference 1e for notes on information that needs to move. This includes most references to BSY, RDY, DRQ, and bus. Implemented e04161r0 (obsoleted ATAPI overlap and queue) Moved host vendor specific log description into its own clause. Integrated e05130r0 Integrated e05131r1 Integrated e05120r2 Needed to add text to 4.21 to support the examples.
Rev 1f
1) 2) 3) 4) 5) 6)
ix
T13/1699-D Revision 3f
December 11, 2006 Revision History (part 4 of 16) Description Updated SET MAX ADDRESS to indicate that on drives with a capacity that is greater than 28 bits, that issues SET MAX ADDRESS to the NATIVE MAX address clears the HPA and returns the full capacity of the drive, not just 137GB. Added e04132r1 Defines sub-command 03 for download microcode Incorporated e04162r0 Obsolete Download Microcode Incorporated e05151r1 Reserve opcodes for e05106. The following resources were assigned: 1) CHECK POWER MODE normal returns 40h and 41h 2) IDENTIFY DEVICE data words 214-221 3) New opcode B6h NV CACHE (Sorry, B8h is reserved for CFA) 4) DCO data structure Word 21 bits 14 and 15 Incorporated e02126r6 WRITE UNCORRECTABLE. The following resources were assigned: 1) Opcode 45h 2) IDENTIFY DEVICE data words 119/120 bit 2 3) DCO Data word 21 bit 13 Modified DCO to indicate that the data is not an overly, it is just data that can be used to enable or disable reporting of features as well as responding to features. Incorporated e05127r2 Updated the definition of the DF bit. Incorporated e05129r1 READ/WRITE LOG DMA EXT. The following resources were assigned: 1) Opcodes 47h and 57h 2) IDENTIFY DEVICE data words 119/120 bit 2 Incorporated e05132r1 Report transport standard. IDENTIFY DEVICE words 222 and 223 were assigned for this purpose. Incorporated e05140r0 Media Serial Number Endianess Performed a major re-work of the IDENTIFY DEVICE table data. Added a column to indicate applicable transport. Received side-band E-Mail comments from yamini@medusalabs.com resulting in the following changes: 1) CFA Translate Sector Features and Count fields S/B N/A as in ATA7 2) Page number was deleted from the clause reference in 4.4.1 Marked bits 15:13 obsolete. This was accidently left out when e04161 was incorporated. Reformatted Table 117, Table 118, Table 119, Table 120. The command code table serves as the master. All of the command codes are now listed. I believe this will cause the table to be maintained better. I also discovered some inconsistencies in the table during the reformat. Performed consistency pass on command tables, several links have been corrupted.
HTU UTH
Rev 2
1)
2) 3) 4)
5)
6) 7) 8)
13) 14)
15)
T13/1699-D Revision 3f Revision History (part 5 of 16) Description Added cross reference to tables. This is required since several commands point to the same tables. Fixed command tables to match ATA7. e05141r2 was voted in however, no document has been posted. Incorporated e05162r0 Incorporated e05161r0 Incorporated e05167r0. Incorporated e05109r3 as modified by Mark Evans Addressed ATA/ATAPI-7 public review comment by inserting the statement If write cache is enabled unrecoverable errors may not be reliably reported as they may occur after the completion of the command. after the statement that says the first error block is returned in the response fields. Replaced Master password with Master password as per E-Mail review comment. Replaced is specified with is specified as per E-Mail review comment Made READ and WRITE LOG EXT optional for ATAPI devices Reincorporated SCT using e05109r4 Changed Long Segment Access to Write Same Incorporated e05170r1 Incorporated e05154r4 Incorporated e05150r2
Rev 2a
1) 2) 3) 4) 5) 6) 7) 8)
9) 10) 1) 2) 3) 4) 5) 6)
2b
xi
T13/1699-D Revision 3f
December 11, 2006 Revision History (part 6 of 16) Description Changed IDENTIFY DEVICE description that involve different behavior for serial and parallel to have separate paragraphs. Added change to support e04132r1. This proposal uses word 86 bit 15 to indicate support. Word 86 bit 15 has been used to indicate that words 119/120 have valid data. Support for segmented download microcode shall be indicated by words 119/120 bit 4. Removed unreferenced references. I checked AAM and the referenced were duplicated there Made editorial changes based on working group review Reworded all statements that included the word will. Reworded all statements that included the word can Was asked to reword statements with the word presently. I found none of these in the document. Removed the word clause from references that were actually subclauses. Fixed the case of the word clause, there were random Clause/clause in the text. Replaced all occurrences of space space with space. Then replaced all occurrences of period space with period space space. This will have the effect of making the document use the same convention for sentence completion. This was done with change bars off. Removed inappropriate references to LBA Low, Mid, and High in annex D. Scrubbed the word register Most of this was just changing the word register to field. There were some usages where more extensive wording changes were required. Fixed cut and paste error in WRITE STREAM DMA EXT during the incorporation of e05154. Added the description of WC and removed the description of CCTL in favor of a reference to the same description in the READ STREAM DMA EXT command. Normalized Not Applicable to N/A. Replaced all na with N/A. Changed Host Shall statements to Host Should. The device can not enforce a requirement on the host. The device can only respond to what it receives.
Rev 2c
1) 2)
3) 4) 5) 6) 7) 8) 9)
13) 14)
xii
T13/1699-D Revision 3f Revision History (part 7 of 16) Description 1) Changed Hosts the A Host. A drive only converses with a single host. 2) Reformatted the IDENTIFY PACKET DEVICE table and added notes regarding some of the inconsistencies. 3) Added an overview subclause to clause 4. The overview includes a table which lists all the feature sets and if each feature set is option mandatory or not a part of this standard. 4) Changed the name of clause 4 to Feature set definitions 5) Merged 4.1 command delivery with the overview 6) Removed the see 4.2 in ID words 60,61 because 4.2 has been removed from the document. 7) Updated Table 6 to include READ/WRITE LOG DMA EXT. Also reformatted table to match other table formatting 8) Added MMCA and CE-ATA references 9) Reformatted approved references and references under development to use tables instead of text and tabs 10) Updated Figure 3 to include Qword. 11) Replaced occurrences of logical sector and sector with 512-byte block of data. This introduces the concept of data block which is a 512 byte fixed unit. There was a previous pass through the document that replaced sector with logical sector. However, new proposals reintroduced the ambiguity. At this point, the doc should have consistent usage of Logical sector for a unit of measure that is reflected in IDENTIFY DEVICE words (118:117). 512-byte block of data refers to transfer units that are fixed at 512 bytes regardless of logical sector size. The phrase data blocks refers to 512 byte unitsModified Table 25 - Extended Self-test log data structure. The byte numbering indicates that there can be 19 log entries, but the description indicates 18 entries 12) Modified Table 26 - Extended Self-test log descriptor entry. The vendors specific values were obviously mis numbered. The Extended Self-test log data structure indicates that there should be 26 bytes. However, the descriptor entry is only 24 bytes long. It looks like the VS bytes were added later and the ending value was not properly updated. 13) Modified the text description of ID words 83 & 86 to read Removable Media Status Notification feature set. Previously they read Removable Media Feature Set. The correct entry was in the table. Words 82 and 85 bit 2 document the removable media feature set. 14) Made minor corrections to Annex C as requested in E-Mail by Rob Elliott 1) Modified C.1 to reference ATA standards prior to ATA/ATAPI-7. The previous statement was a bit strong 2) Softened C.2 to reference Logical Sectors instead of 512-byte sectors. 3) Changed C.3 to reference the logical sector size instead of 512-byte sectors 4) Corrected an inaccuracy in C.3 figure which skipped LBA7 15) Implemented responses to Rob Elliot comments for e06105. 16) Changed IDENTIFY DEIVCE words 85-87 to read supported instead of enabled for features that can not be disabled 17) Updated the definition of N/A 18) In 7.17.6 removed the statement that an ICRC error can occur in IDENTIFY DEVICE. ICRC for SATA has no provision to report a CRC error on one block commands or the last block of the command. 19) Made changes requested at meeting held 21-24 Feb. 20) Added minor revision for ATA8-ACSr2d. xiii
Rev 2d
2d
February 9, 2006
T13/1699-D Revision 3f
December 11, 2006 Revision History (part 8 of 16) Description Converted document from Word to Frame Restored N/A designations to the Normal and Error Outputs. This had the effect of changing WRITE UNCORRECTABLE Sector and LBA field return values from Reserved to N/A Added a table with a list of all the documents incorporated into ATA8-ACS. The purpose of this is to provide a summary of changes and to provide an easy way for the reader to identify new features. Obsoleted DMA Ready as an addition to e04161. This bit is only used for ATAPI overlap and queueing Moved most of the editors notes into e06122 (ATA8-ACS open issues list) Merged the Overlap and Queue feature sets to be the Tagged Command Queuing feature set. This now means that a drive can not implement just overlap Changed Feature Set to feature set everywhere accept in table headings and in the command headings Updated 7.1.1 (Introduction to command structure) to indicate that a mapping shall be supplied by transport documents that reference ATA8-ACS Marked the Tag field obsolete to support e04161 in 7.26.3 PACKET command inputs Added the Device field to all the commands and their associated outputs Modified clause 8 so that all the READ/WRITE LOG EXT command reference also include READ/WRITE LOG DMA EXT Changed log pages E0 and E1 to indicate SCT in table 30 Log address definition Modified 7.56.6 Off-line data collection capabilities to have the bit definitions in a table instead of a list. Modified 7.70.3 WRITE LOG EXT Inputs so the Log Address definition is in a subclause. Modified 7.17.7 IDENTIFY DEVICE data word descriptions to have the form For PATA devices... followed by For SATA devices... for fields that are set differently between PATA and SATA Modified Table 82 Absolute HDA Temperature to reference a circular buffer instead of a queue Incorporated e05178r0. This makes WWN Mandatory Incorporated e05160r0. This clarifies that a flush cache is always successful when write cache is disabled. Incorporated e05162r2. This enhanced DM Mode 3 by allowing the drive to report minimum and maximum transfer sizes. Assigned IDENTIFY DEVICE data words 234 & 235 to this capability Incorporated e05137r7. This adds 4 commands to be used by the Trusted Computing Group. Assigned ID Device word 48 and DCO word 21 bit 12. Added entries to table 6 block size by command and table and table 4 security protocol command actions. The proposal did not provide guidance on these tables. Also updated tables in Annex A Command Set History Incorporated e05109r7. This adds the ability to manipulate non-volatile cache. Assigned IDENTIFY DEVICE data words 214-219, DCO IDENTIFY word 21 bits 15:14, DCO SET word 21 bits 15:14, and opcode B6h. Spell checked the document. Found sooo many spelling errors going back all the way to ATA4.
Rev 3a 3b
20)
21)
xiv
T13/1699-D Revision 3f Revision History (part 9 of 16) Description In Rev 3b most of the editors notes were removed from the doc and placed in the ATA8-ACS Open Issues List, doc #e06122. This document will be used from now on to track the work items remaining on ATA8-ACS. From this point forward, the revision history will reference a work item # when ever possible. Fixed a variety of line issues with the tables. Closed open issue #62 by deleting the sentences that contained the TBDs in TRUSTED RECEIVE Closed open issue #63, the entry for ISO/IEC FDIS 9594-8 in references under development is correct. Marked TRUSTED SEND PROTOCOL EFh as reserved for T10. This is required to keep the assignment values synchronized. Did a substitute to replace Times New Roman font with Arial font. There were over 180 replacements. Did a replacement to remove body paragraph type. This may have some formatting effects on the doc, but I did not see any on my first glance. I believe that this change removed all of the strange formatting that was brought across as a result of the import from word. Changed several references to overlap to be TCQ. This also caused a slight rework of the Tag field definition. Deleted the definition of overlap since overlap is not used. Fixed opcode for WRITE LOG DMA EXT. It was listed in 7.71 as 47h when it should have been 57h Implemented open issue #1 to make HPA prohibited for PACKET devices. The prohibition was inserted into clause 4.10.1. Also modified table 24 (IPD Data) to indicate that word 82 bit 10 shall be cleared to zero. Implemented open issue #3 to clarify resets. e06133r0.pdf contians the comments that are the basis for changes. e06133r1 marks comments as completed if the suggested change was made. Implemented issue #8: what constitutes all error logs in 4.19.7. Removed last paragraph which required firmware to clear all error logs. Implemented issue #18: the diagnostics results field should be reserved for DEVICE RESET. see table 85 for changes. Implemented issue #20. In 7.12.2 changed and all previously downloaded microcode is discarded to and all previously downloaded microcode may be discarded Implemented issue #23. In IPD (table 24) word 2 (table only), the word is titled unique configuration. This was changed to specific configuration to match the ATA version. Implemented issue #24. In IPD (table 24) words 83 & 86 bit 0, the device was allowed to report support for DOWNLOAD MICROCODE. This has been change to Shall be cleared to zero to indicate ... Implemented issue #26. In 7.22.5 and 7.22.6.2, changed the lists from ordered to unordered. Implemented issue #27. In 7.23.2 removed the host requirement to send WRITE BUFFER before READ BUFFER. Replaced the requirements with the consequences of such an action. Implemented issue #30. In table 33 SET FEATUREs subcommands 09 and 89 were only listed for TR-37. CFA also uses this capability. Changed the definition to allow for the CFA usage as well.
Rev 3c
1)
1) 2) 3) 4) 5) 6)
7) 8) 9) 10)
xv
T13/1699-D Revision 3f
December 11, 2006 Revision History (part 10 of 16) Description 20) Implemented issue #31. In table 33 SET FEATUREs subcommands 69 was marked reserved. This has a definition in CFA that has not been ported to ATA8 21) Implemented issue #32. In 7.47.18 there is a statement that says see subcommands for normal outputs. Since there are no normal outputs in the subcommands, this statement was deleted. 22) Implemented issue #33. Added subclause 4.10.4 to explain how IDENTIFY DEVICE data words are set after SETMAX is issued. Updated 7.48.2.2 and 7.48.5.2 to reference the new text. 23) Implemented issue #39. Removed the title from word 0 in 7.75.3. 24) Implemented issue #42. The CHK bit was removed from normal and error outputs in Rev 3b when the tables were reorganized. This issue was created after the fact. As a result of this activity, the CHK bit is no longer used. The definition of CHK was deleted from clause 6. 25) Implemented issue #45. This issue was created because a fix was implemented in table B.2 where opcodes 87 and C0 were missing, the opcodes were in the VS area. 26) Implemented issue #46. Each SMART operation is listed in table B.2 although they have the same opcode. SMART now has a single entry. This change will be spawned in table B.3 before publication. 27) Implemented issue #47. Each DCO operation is listed in table B.2 although they have the same opcode. DCO now has a single entry. This change will be spawned in table B.3 before publication. 28) Implemented issue #74. In subclause 8.1 paragraphs 4 and 5 created host requirements. Since the relavent material is already covered in clause 7, paragraphs 4 and 5 were deleted. 29) Implemented issue #73. Deleted the definition of LBA Range Entry since this is only used in one place. Modified 7.21.3.1 where the only reference to LBA Range Entry exists to have a see 7.21.3.5 where the LBA Range Entry is defined. 30) Implemented issue #71. Deleted the list of devices from 7.17.6.2. but kept the reference to SPC. The list of devices changes with time and should be maintained in SPC. 31) Implemented issue #68. Added kept the abort bit added to table 126. 32) Implemented issue #78. There was an error made when implementing e05170r1, in subclause 8.3.3 function codes 0003h and 0004h were used when 0101h and 0102h should have been used... 33) Implemented issue #79. In table 55 the definition of error code 13h was unclear. Changed the definition to reference SCT data. 34) Implemented issue #67. Change title of table 126 to Generic NV Cache Abort. This reflects the fact that several of the NV Cache Commands use this error output. Retained the changes made to e05106r7 during its incorporation. 35) Implemented issue #65. Added abort bit to table 124. This keeps the NV Cache add lba(s) command consistent with other commands.
Rev 3c
xvi
T13/1699-D Revision 3f Revision History (part 11 of 16) Description 36) Implemented issue #66. Added abort bit to table 125. This keeping the NC Cache remove lba(s) command consistent with other commands. Also clarified bit 0 by referencing the pinned set. During the implementation of this issue, in 7.21.7.4 a cut and paste error was corrected. The statement added to pinned set was changed to removed from pinned set. 37) Implemented issue #77. Modified 4.8 paragraph #5 to more clearly state the operation of DCO Freeze Lock. 38) Implemented issue #89. This incorporates e06127r0 which assigns a security protocol to IEEE P1667. 39) Implemented issue #81. This incorporates e06125r0 which updates IDENTIFY PACKET DEVICE (IPD). 40) Marked IPD word 82 bits 7 and 8 obsolete. These should have been marked obsolete when ATAPI overlap and queue (e04161) were obsoleted. 41) Implemented issue #80. This incorporates e06116r0 which obsoleted both the removable media and media status notification feature sets. This had the effect of obsoleting 3 status bits (MC,MCR,and NM) in all of the read/write commands. 42) Implemented issue #90. This incorporates e06128r1 which deals with issues surrounding resets. 43) Implemented issue #91. This incorporates e06121r1 which clarifies operation of Write-Read-Verify. Although there is 1 mention of IPD in the Write-Read-Verify feature set description, there are no ATAPI commands listed in the affected commands. Assigned word 200 bits 7:0 to the current mode. 44) Implemented issue #86. This incorporates e06123r0 which allows READ LOG EXT to succeed when the device is security locked. 45) Implemented issue #82. Alphebatized the feature sets in clause 4. This will have the effect of causing all current proposals that reference 4.xx to need an update. 46) Implemented issue #83. Added description of how SETMAX affects IDENTIFY DEVICE data to the description of the HPA featureset in 4.10.4 47) Changed Note: paragraphs to conform with the rest of the document and say Note ## - with indented text. Also changed punctuation on ICRC notes for better english grammar. 48) Updated Trusted Send/Receive Security Protocol assignments to show that T10 has assigned protocol 20h 49) Assigned minor revision code 0027h to rev 3c. This code was assigned due to the number of new proposals integrated in this rev. 1) Alphebetized DCO, NV-Cache, SETMAX subcommands in clause 7 2) Moved log pages into a normative annex and added a reference in the description of READ LOG EXT and SMART READ LOG to table 127 and Annex A. 3) Previous Annex A, B, and C have been bumped to B, C, and D
Rev 3c
3d
xvii
T13/1699-D Revision 3f
December 11, 2006 Revision History (part 12 of 16) Description 1) Implemented issue #19, Added the e.g. statement to paragraph 6 of 7.12.2 2) Implemented issue #22. Modified 7.16.7.35 word 85 bit 10 to have a more clear definition of how the HPA bit works. 3) The text in IDENTIFY PACKET DEVICE did not show words 71-72 which should have been marked obsolete in e05161. 4) Implemented issue #70. Modified text in IDENTIFY DEVICE and IDENTIFY PACKET DEVICE to use x-y instead of (x:y) for word offset ranges. 5) Implemented issue #75. Added a definition of BIOS to the definition of terms. 6) Implemented issue #87. Inserted text into 4.1 and 7.16.2 to require that commands reported as not supported be aborted. 7) Implemented issue #94. Added note back in from ATA/ATAPI-7 in table 131 and table 132 8) The footnote in table 132 is only relavent to the parallel transport, so it was deleted. The same is true of table 131. This was caught during a pass to remove the word register. This is why the footnotes were originally removed from the tables. 9) Added the Device field back into table 142, table 131, table 132, and table 143. This was overlooked when the device field was reintroduced. 10) Implemented issue #86. Once again scrubbed the word register. 11) Implemented issue #100. Modified 7.10.3 and 7.10.5 to redefine the term is allowed. 12) Implemented issue #101. Modified trusted send/receive commands (7.55.3, 7.56.3, 7.57.3, and 7.58.3) to properly use LBA (7:0) as transfer length (15:8). 13) Implemented issue #102. In A.3.3 the number of pages was listed instead of the last page number. 14) Implemented issue #104. In 6.1.8 changed lba (7:0) to properly read (47:0) 15) Implemented issue #105. Added a description of SCT extended status code 0015h to table 55 and 8.3.4. 16) Implemented issue #106. Added WRITE LOG DMA EXT to table 8. 17) Implemented issue #108. Marked NV Cache commands in table 3 prohibited. Also marked Media Card pass-through as prohibited. 18) Implemented issue #115. Updated the definition of command released in 3.1.18. 19) Implemented issue #112. Removed other reference in 2.3 to PC-Card. 20) Implemented issue #117. Modified A.5 (Read Stream Error Log) and A.6 (Write Stream Error Log) to use value range notation (x through y) instead of bit field notation (y:x). Also fixed the range in A.6 to properly be 1 though 31 instead of 0 through 31. 21) Implemented issue #121. Made a global change on the word offset range 101-103 to 100-103. This is the 48 bit device capacity range. Only the signifcant 48 bits were included when the range was inserted. 22) Implemented issue #114. Added a definition of TCQ to 3.1. Globally changed all references from command queuing to the TCQ feature set.
Rev 3e
xviii
T13/1699-D Revision 3f Revision History (part 13 of 16) Description 23) Implemented issue #109. Globally changes referenes from packet devices to ATAPI devices. 24) Implemented issue #113. Globally changed PACKET Command feature set to PACKET feature set. This removed an inconsistency in referencing the feature set. 25) Implemented issue #118. Globally removed the phased Changed to:. This was found in only one place, A.5. It looks like the change to was left over from a cut and paste error. 26) Implemented issue #123. Globally changed Volatile Value to Volatile_Value and globally changed the abbreviation VV to V_V. 27) Implemented issue #111. Provided hotlink to subclauses referenced by table 33. 28) Implemented issue #124. Globally changed comply with subclause x.y.z to comply with x.y.z. 29) Implemented issue #126. Fixed a typo in 7.75.3. In the Features field change 5:8 to 15:8. 30) Implemented issue #129. Modified the description column of table 66 (write same command description) to only capitalize the first word of each sentence. 31) Implemented issue #130. In 8.3.4 changed LBA might to LBA may. 32) Implemented issue #135. Added an editors note before table B.3 to warn people that the table is not being maintained. This table is a duplicate of table B.2 with the exception that it is sorted in alphabetical order. 33) Implemented issue #133. Modified the Error field in table 85 to be more clear in stating that DEVICE RESET does not provide diagnostic results and all other commands do. 34) Implemented issue #107. It turns out that e05162r0 was already implemented in a previous revision, but a not was not made in the revision history. This proposal added wording to 7.42.2 (SECURITY ERASE UNIT) to explicitly state that a password could be set prior to issuing the command if a password had not been previously set. 35) Implemented issue #119. Created a definition of log address for read log and placed it in READ LOG EXT. Modified READ LOG EXT and SMART READ LOG to point to this definition. Created a subclause defintion of Host Vendor Specific logs in READ LOG EXT and referenced this from the READ LOG EXT/SMART READ LOG address definition and WRITE LOG EXT/SMART WRITE LOG address defintion. Placed a definition of write log address is SMART WRITE LOG and referenced this from SMART WRITE LOG and WRITE LOG EXT. 36) Implemented issue #132. Added the bit positions to the bit descriptions in clause 6. 37) Implemented issue #131. Normal output tables generic normal outputs w/LBA and Normal output tables generic normal outputs wo/LBA were identical. Changed clause 7 to reference only 1 normal outputs table. Deleted the redundant table from clause 9. 38) The error outputs for SMART WRITE LOG and WRITE LOG EXT were listed incorrectly. Split setmax and write log error outputs so they use different tables. Everything now reads the same as ATA/ATAPI-7 for these commands 39) After this revision was archived, clause 7 was split into 2 files. This was kept locally as rev 3e so changebars could be more easily generated
Rev 3e
xix
T13/1699-D Revision 3f
December 11, 2006 Revision History (part 14 of 16) Description 1) Assigned minor revision 0033h to ATA8-ACS rev 3e 2) Implemented issue #9. Removed Allocation Unit from the glossary, changed the field in configure stream to reference a subclause that describes allocation unit. Change the description of the flush cache bit to reference the new Allocation Unit subclause. 3) Implemented issue #28. Modified 7.26.5 and 7.27.5, the error outputs for the read DMA queued commands to remove the reference to Overlapped interrupt. The overlapped interrupt is not defined anywhere. Also remove the redundant statement about the command being aborted if it is not support. This material is contained in the definition of the abort bit. 4) Implemented issue #43. The definitions of DF and DRQ should be N/A for normal outputs (table 89 and table 93) and defined for error outputs (table 108 and table 121). 5) Implemented issue #44. Updated the definition of the DCO SET Error, table 113, to be more clear. 6) Implemented issue #95. Changed the definition of words 100-103 in the IDENTIFY DEVICE table (table 21) to read Total Number of User Addressable Sectors for the 48-bit Address feature set. Also changed to heading in the text to match. 7) Implemented issue #97. Changed TF Data in 8.3.3 paragraph 6 to input data structure. 8) Implemented issue #98. Inserted a statement requiring the device to abort commands which are reported as not supported by IDENTIFY PACKET DEVICE. Also removed (See 0) statement that were left over from a conversion from word. 9) Implemented issue #103. Added verbage to indicate that a block count of zero is illegal to the Inputs and Error Outputs for WRITE LOG EXT (DMA), READ LOG EXT (DMA), SMART READ LOG and SMART WRITE LOG. 10) Implemented issue #120. Modified the unorderd list in 4.10.4 to make it more clear. 11) Implemented issue #128. Changed SCT Long Sector Access to SCT Read/Write Long. 12) Revisited issue #22. Word 85 bit 10 in the IDENTIFY DEVICE data table had not been updated as described in the issue. 13) Implemented issue #127. Inserted the fact that SMART DISABLE OPERATIONS does not disable SCT. 14) Implemented issue #138. The definition of ASCII string from ATA/ATAPI-7 did not seem appropriate for inclusion into IDENTIFY DEVICE. Reworked the definition of ASCII string and included it into 7.16.2. Also move the field data type descriptions from 7.17.2 to 7.16.2 and added a reference in 7.17.2 to 7.16.2. 15) Implemented issue #139. Clarified the definition of uncorrectable options. 16) Implemented issue #140. Changed IDENTIFY DEVICE data word 86 bit 8 from fixed to variable. 17) Implemented issue #141. Clarified SET MAX ADDRESS (7.48.2.2) to remove the requirement on the host that READ NATIVE MAX shall precede SET MAX ADDRESS. Instead the cosequences of not issueing the READ NATIVE MAX are listed. 18) Implemented issue #142. Documented Option/Mandatory,Fixed/Vaariable, and Serial/Parallel for IDENTIFY DEVICE data words 219 and 220.
Rev 3f
xx
T13/1699-D Revision 3f Revision History (part 15 of 16) Description 19) Implemented issue #143. Globally changed ID Field was not found to sector was not found. This only affected the error outputs of several SMART caommands. 20) Implemented issue #144. Changed maximum values in A.3.1, A.3.3 and A.4.1. 21) Implemented issue #145. Globally changed vendor unique to vendor specific. Several of these had krept in during proposal integration to the Annexes. 22) Implemented issue #149. Fixed DOWNLOAD MICROCODE Normal Outputs (7.12.4)to reference the correct IDENTIFY DEVICE data words. 23) Implemented issue #150. In DOWNLOAD MICROCODE Inputs, labelled mode 3 as optional. 24) Implemented issue #152. Wordsmithed the option byte in DOWNLOAD MICROCODE inputs. 25) Implemented issue #153. Fixed a typo in HPA Security Extensions (4.10.2). 26) Implemented issue #163. The Count Field in IDLE IMMEDIATE UNLOAD (7.19.4) was incorrectly documented as 44h when it should have been reserved. 27) Implemented issue #159. Added WWN to IDENITFY PACKET DEVICE and made it mandatory. Also ported the reserved words for the extension to 128 bits. 28) Implemented issue #136. Moved Host and Device vendor specific log page descriptions along with table 127 to Annex A 29) Implemented issue #134. Changed table 90 (Normal Output for SMART Offline Immediate), table 91 (Normal Output for SMART Return Status), and table 110 (Error Output for SMART Execute Offline Immediate) to remove the N/As that were indistinguishable from the key values supplied 30) Integrated e06153r1. This reserves SCT Action Code 0007h, Extended Status Codes BF00h-BFFFh, SCT Feature Control feature codes 0004h-0005h, and SCT Data Table IDs 0003h-0004h for use by SATA-IO. 31) Integrated e06152r3. This adds session and lifetime temperature reporting to SCT status in table 60. Also adds interval count since last over and under temperature conditions 32) Changed byte offsets throughout clause 8 from : notation to - notation. This brings the clause inline with the rest of the document. Unfortunatly, some of the tables have formulas in the offset column. It my be difficult to tell the range from the formula. 33) Integrated e06102r2. Added a new log page at the end of Annex A called device statistics. Modified the proposal during incorporation to allow for definitions by page. 34) Bit 4 of words 119 and 120 (Segmented feature of download Microcode) was documented in the table, but not in the text. Added the description to the text. 35) Implement issue #146. Marked SET Features subcommands 41h, 83h, and C1h, DCO SET/IDNETIFY Word 21 bit 11, IDENITFY DEVICE data words 119/120 bit 5, and IDENTIFY DEVICE data word 53 bits 8-15 as reserved for e06144. 36) Integrated e05179r8. This removes some of the vagueness from the Security feature set. One Editors Note needs resolution in 4.18.10.
Rev 3f
xxi
T13/1699-D Revision 3f
December 11, 2006 Revision History (part 16 of 16) Description 37) Added a paragraph at the beginning of this subclause to describe the issues list. (added based on line-by-line review) 38) Changed formatting of IDENTIFY DEVICE data word 222. (added based on line-byline review) 39) Added (i.e., HPA enabled/disabled) to IDENTIFY DEVICE data word 85 bit 10. (added based on line-by-line review) 40) Assigned minor revision code 0042h to this rev (3f)
Rev 3f
xxii
T13/1699-D Revision 3f
32 33 34 35 36 37 38
43 44
Doc Description e06123r0 New Feature: Allows READ LOG EXT to succeed even when the drive is locked. e05162r0 Clarifies SECURITY ERASE UNIT to add the explicit statement that a password can be set prior to issuing SECURITY ERASE UNIT if a password had not been previously set e06153r1 Reserves SCT resources for use by SATA-IO e06152r3 New Feature: Adds session and lifetime min and max temperature reporting to SCT Status. Also provides some concept of time since last temperature beyond operating limits. e06102r2 New Feature: Creates a Device Statistics Log for documenting counters. The first counter defined documents lifetime power-on resets. e05179r8 Clarifies the operation of the Security feature set without changing operation relative to ATA/ATAPI-7. There is a second proposal that will be integrated into ACS-2 to close some of the security holes.
45 46 47 48 49 50
xxiv
T13/1699-D Revision 3f
Contents
Page Points of Contact................................................................................................................................................... iii Document Status ................................................................................................................................................. vii New Capabilities added to ATA8-ACS.............................................................................................................. xxiii Contents.............................................................................................................................................................. xiii Tables ................................................................................................................................................................. xix Figures .............................................................................................................................................................. xxiii Foreword ............................................................................................................................................................ xxv Introduction ........................................................................................................................................................ xxv 1 Scope ................................................................................................................................................................. 1 2 Normative references ......................................................................................................................................... 2 2.1 Approved references ................................................................................................................................ 2 2.2 References under development ............................................................................................................... 2 2.3 Other references ....................................................................................................................................... 3 3 Definitions, abbreviations, and conventions ....................................................................................................... 4 3.1 Definitions and abbreviations ................................................................................................................... 4 3.2 Conventions .............................................................................................................................................. 7 3.2.1 Overview ......................................................................................................................................... 7 3.2.2 Precedence ..................................................................................................................................... 7 3.2.3 Lists ................................................................................................................................................. 7 3.2.4 Keywords ........................................................................................................................................ 7 3.2.5 Numbering ....................................................................................................................................... 8 3.2.6 Bit conventions ................................................................................................................................ 8 3.2.7 State diagram conventions .............................................................................................................. 8 3.2.8 Byte, word, DWord, and QWord Relationships ............................................................................... 8 4 Feature set definitions ...................................................................................................................................... 11 4.1 Overview ................................................................................................................................................. 11 4.2 General feature set ................................................................................................................................. 11 4.3 The PACKET feature set ........................................................................................................................ 12 4.3.1 Overview ....................................................................................................................................... 12 4.3.2 Identification of PACKET feature set devices ............................................................................... 13 4.3.3 Processing resets for the PACKET feature set ............................................................................. 13 4.3.4 The PACKET command ................................................................................................................ 13 4.4 48-bit Address feature set ...................................................................................................................... 13 4.5 Advanced Power Management feature set ............................................................................................ 14 4.6 Automatic Acoustic Management feature set ......................................................................................... 15 4.7 CompactFlash Association (CFA) feature set ..................................................................................... 15 4.8 Device Configuration Overlay (DCO) feature set ................................................................................... 15 4.9 General Purpose Logging feature set ..................................................................................................... 18 4.10 Host Protected Area (HPA) feature set ................................................................................................ 19 4.10.1 HPA overview .............................................................................................................................. 19 4.10.2 HPA security extensions ............................................................................................................. 19 4.10.3 48-Bit extensions ......................................................................................................................... 19 4.10.4 IDENTIFY DEVICE data ............................................................................................................. 20 Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) xiii
T13/1699-D Revision 3f
4.10.5 BIOS determination of SET MAX security extension status ........................................................ 20 4.10.6 BIOS locking SET MAX ............................................................................................................... 21 4.11 Long Logical Sector feature set ............................................................................................................ 22 4.11.1 Overview ..................................................................................................................................... 22 4.12 Long Physical Sector feature set .......................................................................................................... 25 4.13 Media Card Pass Through Command feature set ................................................................................ 26 4.14 NV Cache feature set ........................................................................................................................... 27 4.15 NV Cache Power Management feature set .......................................................................................... 29 4.16 Power Management feature set ........................................................................................................... 30 4.16.1 Power management commands ................................................................................................. 30 4.16.2 Standby timer .............................................................................................................................. 30 4.16.3 Power modes .............................................................................................................................. 31 4.17 Power-Up In Standby feature set ......................................................................................................... 32 4.18 Security feature set ............................................................................................................................... 33 4.18.11 Security mode states ................................................................................................................. 39 4.19 SMART (Self-monitoring, analysis, and reporting technology) feature set ........................................... 44 4.19.1 Device SMART data structure ..................................................................................................... 45 4.19.2 Background data collection ......................................................................................................... 45 4.19.3 Off-line/Captive mode data collection ......................................................................................... 45 4.19.4 Threshold exceeded condition .................................................................................................... 45 4.19.5 SMART feature set commands ................................................................................................... 45 4.19.6 SMART operation with power management modes .................................................................... 45 4.19.7 SMART device error log reporting ............................................................................................... 46 4.20 Streaming feature set ........................................................................................................................... 46 4.20.1 Streaming feature set overview ................................................................................................... 46 4.20.2 Streaming commands ................................................................................................................. 46 4.21 Tagged Command Queuing (TCQ) feature set .................................................................................... 47 4.21.1 Overview ..................................................................................................................................... 47 4.21.2 Queueing ..................................................................................................................................... 48 4.22 Trusted Computing feature set ............................................................................................................. 48 4.23 Write-Read-Verify feature set ............................................................................................................... 49 5 ATA Protocols .................................................................................................................................................. 51 6 Status and Error bits ........................................................................................................................................ 53 6.1 Status Bits .............................................................................................................................................. 53 6.2 Error Bits ................................................................................................................................................. 53 6.3 Interrupt Reason Bits .............................................................................................................................. 54 7 Command Descriptions .................................................................................................................................... 57 7.1 Overview ................................................................................................................................................. 57 7.2 CFA ERASE SECTORS - C0h, non-data ............................................................................................... 61 7.3 CFA REQUEST EXTENDED ERROR CODE - 03h, non-data ............................................................... 62 7.4 CFA TRANSLATE SECTOR - 87h, PIO data-in ..................................................................................... 64 7.5 CFA WRITE MULTIPLE WITHOUT ERASE - CDh, PIO data-out ......................................................... 65 7.6 CFA WRITE SECTORS WITHOUT ERASE - 38h, PIO data-out ........................................................... 66 7.7 CHECK MEDIA CARD TYPE - D1h, Non-data ...................................................................................... 67 7.8 CHECK POWER MODE - E5h, Non-data .............................................................................................. 68 7.9 CONFIGURE STREAM - 51h, Non-data ................................................................................................ 69 7.10 Device Configuration Overlay (DCO) ................................................................................................... 71 7.10.1 DCO Overview ............................................................................................................................ 71 7.10.2 DEVICE CONFIGURATION FREEZE LOCK - B1h/C1h, Non-data............................................. 72 7.10.3 DEVICE CONFIGURATION IDENTIFY - B1h/C2h, PIO Data-in ................................................. 73 7.10.4 DEVICE CONFIGURATION RESTORE - B1h/C0h, Non-data .................................................... 77 7.10.5 DEVICE CONFIGURATION SET - B1h/C3h, PIO Data Out........................................................ 78 7.11 DEVICE RESET - 08h, Device reset .................................................................................................... 83 7.12 DOWNLOAD MICROCODE - 92h, PIO Data-out ................................................................................. 84 xiv Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS)
T13/1699-D Revision 3f
7.13 EXECUTE DEVICE DIAGNOSTIC - 90h, Device diagnostic ............................................................... 87 7.14 FLUSH CACHE - E7h, Non-data .......................................................................................................... 88 7.15 FLUSH CACHE EXT - EAh, Non-data ................................................................................................. 89 7.16 IDENTIFY DEVICE - ECh, PIO Data-in ................................................................................................ 90 7.17 IDENTIFY PACKET DEVICE - A1h, PIO Data-in ............................................................................... 117 7.18 IDLE - E3h, Non-data ......................................................................................................................... 130 7.19 IDLE IMMEDIATE - E1h, Non-data .................................................................................................... 131 7.20 NOP - 00h, Non-data .......................................................................................................................... 133 7.21 Non Volatile Cache ............................................................................................................................. 134 7.21.1 NV Cache Overview .................................................................................................................. 134 7.21.2 NV Cache Power Management Overview ................................................................................. 134 7.21.3 ADD LBA(S) TO NV CACHE PINNED SET - B6h/10h, DMA .................................................... 136 7.21.4 FLUSH NV CACHE - B6h/14h, Non-data .................................................................................. 137 7.21.5 QUERY NV CACHE MISSES - B6h/13h, DMA.......................................................................... 138 7.21.6 QUERY NV CACHE PINNED SET - B6h/12h, DMA.................................................................. 139 7.21.7 REMOVE LBA(S) FROM NV CACHE PINNED SET - B6h/11h, DMA....................................... 140 7.21.8 RETURN FROM NV CACHE POWER MODE - B6h/01h, Non-data ......................................... 141 7.21.9 SET NV CACHE POWER MODE - B6h/00h, Non-data............................................................. 142 7.22 PACKET - A0h, Packet ....................................................................................................................... 143 7.23 READ BUFFER - E4, PIO data-in ...................................................................................................... 145 7.24 READ DMA - C8h, DMA ..................................................................................................................... 146 7.25 READ DMA EXT - 25h, DMA ............................................................................................................. 147 7.26 READ DMA QUEUED - C7h, DMA Queued ....................................................................................... 148 7.27 READ DMA QUEUED EXT- 26h, DMA Queued ................................................................................ 150 7.28 READ LOG EXT - 2Fh, PIO data-in ................................................................................................... 152 7.29 READ LOG DMA EXT - 47h, DMA ..................................................................................................... 154 7.30 READ MULTIPLE - C4h, PIO data-in ................................................................................................. 155 7.31 READ MULTIPLE EXT - 29h, PIO data-in .......................................................................................... 157 7.32 READ NATIVE MAX ADDRESS - F8h, Non-data .............................................................................. 159 7.33 READ NATIVE MAX ADDRESS EXT - 27h, Non-data ...................................................................... 160 7.34 READ SECTOR(S) - 20h, PIO data-in ............................................................................................... 161 7.35 READ SECTOR(S) EXT - 24h, PIO data-in ....................................................................................... 162 7.36 READ STREAM DMA EXT - 2Ah, DMA ............................................................................................. 163 7.37 READ STREAM EXT - 2Bh, PIO data-in ............................................................................................ 166 7.38 READ VERIFY SECTOR(S) - 40h, Non-data ..................................................................................... 167 7.39 READ VERIFY SECTOR(S) EXT - 42h, Non-data ............................................................................. 168 7.40 SECURITY DISABLE PASSWORD - F6h, PIO data-out ................................................................... 169 7.41 SECURITY ERASE PREPARE - F3h, Non-data ................................................................................ 171 7.42 SECURITY ERASE UNIT - F4h, PIO data-out ................................................................................... 172 7.43 SECURITY FREEZE LOCK - F5h, Non-data ..................................................................................... 174 7.44 SECURITY SET PASSWORD - F1h, PIO data-out ............................................................................ 175 7.45 SECURITY UNLOCK - F2h, PIO data-out .......................................................................................... 177 7.46 SERVICE - A2h, Packet or DMA Queued .......................................................................................... 179 7.47 SET FEATURES - EFh, Non-data ...................................................................................................... 180 7.47.3 Enable/disable 8-bit PIO data transfer ...................................................................................... 182 7.47.4 Enable/disable write cache ....................................................................................................... 182 7.47.5 Set transfer mode ...................................................................................................................... 182 7.47.6 Enable/disable advanced power management ......................................................................... 182 7.47.7 Enable/disable Power-Up In Standby feature set ..................................................................... 183 7.47.8 Power-Up In Standby feature set device spin-up ...................................................................... 183 7.47.9 Enable/disable CFA power mode 1 ........................................................................................... 183 7.47.10 Enable/Disable Write-Read-Verify feature set ........................................................................ 184 7.47.11 Enable/disable Automatic Acoustic Management ................................................................... 184 7.47.12 Set Maximum Host Interface Sector Times ............................................................................. 185 7.47.13 Enable/disable read look-ahead .............................................................................................. 185 7.47.14 Enable/disable release interrupt .............................................................................................. 186 7.47.15 Enable/disable SERVICE interrupt .......................................................................................... 186 Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) xv
T13/1699-D Revision 3f
7.47.16 Enable/disable reverting to defaults ........................................................................................ 186 7.48 SET MAX ............................................................................................................................................ 187 7.48.2 SET MAX ADDRESS - F9h........................................................................................................ 188 7.48.3 SET MAX FREEZE LOCK F9h/04h, Non-data ....................................................................... 190 7.48.4 SET MAX LOCK - F9h/02h, Non-data ....................................................................................... 191 7.48.5 SET MAX SET PASSWORD - F9h/01h, PIO data-out............................................................... 192 7.48.6 SET MAX UNLOCK - F9h/03h, PIO data-out............................................................................. 193 7.49 SET MAX ADDRESS EXT - 37h, Non-data ....................................................................................... 194 7.50 SET MULTIPLE MODE - C6h, Non-data ............................................................................................ 196 7.51 SLEEP - E6h, Non-data ...................................................................................................................... 197 7.52 SMART ............................................................................................................................................... 198 7.52.2 SMART DISABLE OPERATIONS - B0h/D9h, Non-data............................................................ 199 7.52.3 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE - B0h/D2h, Non-data............................ 200 7.52.4 SMART ENABLE OPERATIONS - B0h/D8h, Non-data............................................................. 202 7.52.5 SMART EXECUTE OFF-LINE IMMEDIATE - B0h/D4h, Non-data ............................................ 203 7.52.6 SMART READ DATA - B0h/D0h, PIO data-in............................................................................ 207 7.52.7 SMART READ LOG - B0h/D5h.................................................................................................. 211 7.52.8 SMART RETURN STATUS - B0h/DAh, Non-data ..................................................................... 212 7.52.9 SMART WRITE LOG - D6h, PIO data-out ................................................................................. 213 7.53 STANDBY - E2h, Non-data ................................................................................................................ 214 7.54 STANDBY IMMEDIATE - E0h, Non-data ........................................................................................... 215 7.55 TRUSTED RECEIVE 5Ch ............................................................................................................... 216 7.56 TRUSTED RECEIVE DMA 5Dh ...................................................................................................... 221 7.57 TRUSTED SEND 5Eh ..................................................................................................................... 222 7.58 TRUSTED SEND DMA 5Fh ............................................................................................................ 225 7.59 WRITE BUFFER - E8h, PIO data-out ................................................................................................. 226 7.60 WRITE DMA - CAh, DMA ................................................................................................................... 227 7.61 WRITE DMA EXT - 35h, DMA ............................................................................................................ 228 7.62 WRITE DMA FUA EXT - 3Dh, DMA ................................................................................................... 229 7.63 WRITE DMA QUEUED - CCh, DMA Queued .................................................................................... 230 7.64 WRITE DMA QUEUED EXT - 36h, DMA Queued .............................................................................. 232 7.65 WRITE DMA QUEUED FUA EXT - 3Eh, DMA Queued ..................................................................... 234 7.66 WRITE LOG EXT - 3Fh, PIO data-out ................................................................................................ 235 7.67 WRITE LOG DMA EXT - 57h, DMA ................................................................................................... 236 7.68 WRITE MULTIPLE - C3h, PIO data-out ............................................................................................. 237 7.69 WRITE MULTIPLE EXT - 39h, PIO data-out ...................................................................................... 239 7.70 WRITE MULTIPLE FUA EXT - CEh, PIO data-out ............................................................................. 241 7.71 WRITE SECTOR(S) - 30h, PIO data-out ............................................................................................ 242 7.72 WRITE SECTOR(S) EXT - 34h, PIO data-out .................................................................................... 243 7.73 WRITE STREAM DMA EXT - 3Ah, DMA ........................................................................................... 244 7.74 WRITE STREAM EXT - 3Bh, PIO data-out ........................................................................................ 247 7.75 WRITE UNCORRECTABLE EXT - 45h, Non-data ............................................................................. 248 8 SCT Command Transport .............................................................................................................................. 251 8.1 Overview ............................................................................................................................................... 251 8.1.1 Device addressing methods ........................................................................................................ 251 8.1.2 SCT command nesting and interspersing with standard commands .......................................... 251 8.1.3 Resets ......................................................................................................................................... 252 8.2 Processing SCT commands ................................................................................................................. 253 8.2.1 Processing SCT commands overview ........................................................................................ 253 8.2.2 SCT capability identification ........................................................................................................ 253 8.2.3 SCT command transfer ............................................................................................................... 253 8.2.4 SCT data transfer ........................................................................................................................ 256 8.2.5 SCT status .................................................................................................................................. 258 8.3 SCT Command Set .............................................................................................................................. 262 8.3.1 Overview ..................................................................................................................................... 262 8.3.2 SCT Read/Write Long .................................................................................................................. 263 xvi Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS)
T13/1699-D Revision 3f
8.3.3 Write Same .................................................................................................................................. 266 8.3.4 Error Recovery Control command................................................................................................ 269 8.3.5 Feature Control command ........................................................................................................... 271 8.3.6 SCT Data Table command........................................................................................................... 274 9 Normal and Error Outputs .............................................................................................................................. 277 9.1 Overview ............................................................................................................................................... 277 9.2 Normal Outputs .................................................................................................................................... 277 9.3 Error Outputs ........................................................................................................................................ 295 Annex A (Normative) Log Page Definitions ....................................................................................................... 327 A.1 Overview .............................................................................................................................................. 327 A.2 General Purpose Log Directory ............................................................................................................ 328 A.3 Extended Comprehensive SMART Error log ....................................................................................... 328 A.3.1 Overview ........................................................................................................................................... 328 A.3.2 Error log version ................................................................................................................................ 329 A.3.3 Error log index ................................................................................................................................... 329 A.3.4 Extended Error log data structure ..................................................................................................... 329 A.3.5 Device error count ............................................................................................................................. 332 A.3.6 Data structure checksum .................................................................................................................. 332 A.4 Extended Self-test log .......................................................................................................................... 332 A.4.1 Overview ........................................................................................................................................... 332 A.4.2 Self-test descriptor index ................................................................................................................... 333 A.4.3 Self-test log data structure revision number ...................................................................................... 333 A.4.4 Extended Self-test log descriptor entry ............................................................................................. 333 A.4.5 Data structure checksum .................................................................................................................. 333 A.5 Read Stream Error Log ........................................................................................................................ 333 A.6 Write Stream Error Log ........................................................................................................................ 335 A.7 SMART Log Directory .......................................................................................................................... 336 A.8 Host Vendor Specific Logs ................................................................................................................... 336 A.9 Device Vendor Specific Logs ............................................................................................................... 336 A.10 Summary error log ............................................................................................................................. 336 A.10.1 Overview ......................................................................................................................................... 336 A.10.2 Error log version .............................................................................................................................. 337 A.10.3 Error log index ................................................................................................................................. 337 A.10.4 Error log data structure ................................................................................................................... 337 A.10.5 Device error count ........................................................................................................................... 339 A.10.6 Data structure checksum ................................................................................................................ 339 A.11 Comprehensive error log .................................................................................................................... 339 A.11.1 Overview ......................................................................................................................................... 339 A.11.2 Error log version .............................................................................................................................. 340 A.11.3 Error log index ................................................................................................................................. 340 A.11.4 Error log data structure ................................................................................................................... 340 A.11.5 Device error count ........................................................................................................................... 340 A.11.6 Data structure checksum ................................................................................................................ 340 A.12 Self-test log ........................................................................................................................................ 341 A.12.1 Overview ......................................................................................................................................... 341 A.12.2 Self-test log data structure revision number .................................................................................... 341 A.12.3 Self-test log descriptor entry ........................................................................................................... 341 A.12.4 Self-test index ................................................................................................................................. 342 A.12.5 Data structure checksum ................................................................................................................ 342 A.13 Selective self-test log ......................................................................................................................... 342 A.13.1 Overview ......................................................................................................................................... 342 A.13.2 Data structure revision number ....................................................................................................... 343 A.13.3 Test span definition ......................................................................................................................... 343 A.13.4 Current LBA under test ................................................................................................................... 343 A.13.5 Current span under test .................................................................................................................. 343 Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) xvii
T13/1699-D Revision 3f
A.13.6 Feature flags ................................................................................................................................... 343 A.13.7 Selective self-test pending time ...................................................................................................... 343 A.13.8 Data structure checksum ................................................................................................................ 343 A.14 Device Statistics ................................................................................................................................. 344 A.14.1 Overview ......................................................................................................................................... 344 A.14.2 General Statistics (Page 0) ............................................................................................................. 344 Annex B (Informative) Command Set summary................................................................................................. 345 Annex C (Informative) Design and programming considerations for large physical sector devices .................. 361 C.1 Introduction .......................................................................................................................................... 361 C.2 Physical sectors ................................................................................................................................... 361 C.3 Unaligned write .................................................................................................................................... 361 C.4 SET MAX ............................................................................................................................................. 362 C.5 Software compatibility .......................................................................................................................... 362 Annex D (Informative) How to use SCT commands .......................................................................................... 363 D.1 How to use SCT commands overview ................................................................................................. 363 D.2 Examples of Log page command sequences ...................................................................................... 365 D.3 Issuing an SCT command to a device ................................................................................................. 369 D.3.1 Step 1 - Build a Key Sector ............................................................................................................... 369 D.3.2 Step 2 - Issue the SCT command ..................................................................................................... 370 D.3.3 Step 3 - Transfer Data if Required .................................................................................................... 370 D.3.4 Step 4 - Final Status/SCT Command Completion ............................................................................ 371
xviii
T13/1699-D Revision 3f
Tables
Page Table 1 - Approved ANSI References.................................................................................................................... 2 Table 2 - References Under Development ............................................................................................................ 3 Table 3 - Feature Set Summary........................................................................................................................... 11 Table 4 - Block Size By Command ...................................................................................................................... 22 Table 5 - Media Card type references ................................................................................................................. 27 Table 6 - Interaction of Master Password Capability and Passwords (when Security is not frozen) .................. 34 Table 7 - Summary of Security States and Characteristics.................................................................................. 35 Table 8 - Security Mode Command Actions ........................................................................................................ 36 Table 9 - IDENTIFY settings for Security state SEC1.......................................................................................... 40 Table 10 - IDENTIFY settings for Security state SEC2........................................................................................ 41 Table 11 - IDENTIFY settings for Security state SEC4........................................................................................ 42 Table 12 - IDENTIFY settings for Security state SEC5........................................................................................ 43 Table 13 - IDENTIFY settings for Security state SEC6........................................................................................ 44 Table 14 - Extended error codes ......................................................................................................................... 62 Table 15 - CFA TRANSLATE SECTOR data....................................................................................................... 64 Table 16 - Device Configuration Overlay Feature field values............................................................................. 71 Table 17 - Device Configuration Identify data structure ....................................................................................... 74 Table 18 - Device Configuration Overlay (DCO) data structure........................................................................... 79 Table 19 - DOWNLOAD MICROCODE Mode 3 return options ........................................................................... 85 Table 20 - Diagnostic codes ................................................................................................................................ 87 Table 21 - IDENTIFY DEVICE data ..................................................................................................................... 91 Table 22 - Minor revision number ...................................................................................................................... 105 Table 23 - Transport minor version number....................................................................................................... 116 Table 24 - IDENTIFY PACKET DEVICE data.................................................................................................... 118 Table 25 - Automatic Standby timer periods ...................................................................................................... 130 Table 26 - NOP Subcommand Code ................................................................................................................. 133 Table 27 - NV Cache Commands ...................................................................................................................... 134 Table 28 - NV Cache Power Managements Commands ................................................................................... 135 Table 29 - SECURITY DISABLE PASSWORD data content............................................................................. 170 Table 30 - SECURITY ERASE UNIT data content ............................................................................................ 173 Table 31 - SECURITY SET PASSWORD data content ..................................................................................... 176 Table 32 - SECURITY UNLOCK data content ................................................................................................... 178 Table 33 - SET FEATURES Feature field definitions......................................................................................... 180 Table 34 - Transfer mode values ....................................................................................................................... 182 Table 35 - Advanced power management levels ............................................................................................... 183 Table 36 - Write-Read-Verify Sector Counts...................................................................................................... 184 Table 37 - Automatic acoustic management levels ........................................................................................... 185 Table 38 - SET MAX Feature field values.......................................................................................................... 187 Table 39 - SET MAX SET PASSWORD data content ....................................................................................... 192 Table 40 - SMART Feature field values ............................................................................................................. 198 Table 41 - SMART EXECUTE OFF-LINE IMMEDIATE Subcommands ............................................................ 203 Table 42 - Device SMART data structure .......................................................................................................... 207 Table 43 - Off-line data collection status byte values ........................................................................................ 208 Table 44 - Self-test execution status values ...................................................................................................... 208 Table 45 - Offline Data Collection Capabilities .................................................................................................. 209 Table 46 - TRUSTED RECEIVE Security_Protocol field description ................................................................. 217 Table 47 - Security_Protocol 00h - SP_Specific field descriptions for Protocol 00h .......................................... 218 Table 48 - TRUSTED RECEIVE parameter data for SP_Specific=0000h ......................................................... 219 Table 49 - TRUSTED RECEIVE parameter data for SP_Specific=0001h ......................................................... 219 Table 50 - TRUSTED SEND - Security_Protocol field description..................................................................... 223 Table 51 - Fields to issue an SCT command using SMART WRITE LOG......................................................... 253 Table 52 - Fields to issue an SCT command using WRITE LOG (DMA) EXT................................................... 254 Table 53 - Successful SCT command response................................................................................................ 254 Table 54 - SCT command error response ......................................................................................................... 255 Table 55 - Extended Status codes ..................................................................................................................... 256 Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) xix
T13/1699-D Revision 3f
Table 56 - SCT data transfer using SMART READ LOG or SMART WRITE LOG............................................ 257 Table 57 - SCT data transfer using READ LOG (DMA) EXT or WRITE LOG (DMA) EXT ................................ 258 Table 58 - SCT status request using SMART READ LOG ................................................................................ 259 Table 59 - SCT status request using READ LOG (DMA) EXT........................................................................... 259 Table 60 - Format of SCT status response ........................................................................................................ 260 Table 61 - SCT command format....................................................................................................................... 262 Table 62 - SCT Action Codes ............................................................................................................................ 262 Table 63 - SCT Read/Write Long command ...................................................................................................... 263 Table 64 - SCT Read/Write Long command status response............................................................................ 264 Table 65 - SCT Read/Write Long Format .......................................................................................................... 265 Table 66 - Write Same command ...................................................................................................................... 267 Table 67 - Write Same command status response ............................................................................................ 268 Table 68 - Error Recovery Control command .................................................................................................... 269 Table 69 - Error Recovery Control command status response .......................................................................... 270 Table 70 - Feature Control command ................................................................................................................ 271 Table 71 - Feature Code List ............................................................................................................................. 272 Table 72 - Feature Control command status response...................................................................................... 273 Table 73 - SCT Data Table command ............................................................................................................... 274 Table 74 - SCT Data Tables (by Table Identifier) .............................................................................................. 274 Table 75 - Absolute HDA Temperature.............................................................................................................. 274 Table 76 - Feature Control command status response...................................................................................... 276 Table 77 - Extended Error Code ........................................................................................................................ 277 Table 78 - Error Bit Defined For Normal Output................................................................................................. 278 Table 79 - Generic Normal Output (No LBA Return Value) ............................................................................... 279 Table 80 - CFA Normal Output .......................................................................................................................... 279 Table 81 - Media Card Type Normal Output ...................................................................................................... 280 Table 82 - Check Power Mode Normal Output .................................................................................................. 281 Table 83 - Configure Stream Normal ................................................................................................................. 282 Table 84 - Stream Normal.................................................................................................................................. 283 Table 85 - Device Reset and Execute Diagnostics ............................................................................................ 284 Table 86 - IDLE Unload ..................................................................................................................................... 285 Table 87 - ATAPI Normal Output ....................................................................................................................... 286 Table 88 - Queued Normal Output..................................................................................................................... 287 Table 89 - SETMAX Normal Output................................................................................................................... 288 Table 90 - SMART Off-Line Immediate Normal Output ..................................................................................... 289 Table 91 - SMART Return Status Normal Output .............................................................................................. 290 Table 92 - Generic Extended Normal Output..................................................................................................... 291 Table 93 - SETMAX Extended Normal Output .................................................................................................. 292 Table 94 - Queued Extended Normal Output .................................................................................................... 293 Table 95 - NV Cache Normal Output ................................................................................................................. 294 Table 96 - NV Cache Flush Normal Output ....................................................................................................... 294 Table 97 - CFA Erase Error Status .................................................................................................................... 295 Table 98 - CFA Write Error Status ..................................................................................................................... 296 Table 99 - CFA Abort Error ................................................................................................................................ 297 Table 100 - Generic Abort.................................................................................................................................. 298 Table 101 - Generic Abort w/o Device Fault ...................................................................................................... 299 Table 102 - Configure Stream Error................................................................................................................... 300 Table 103 - Flush Cache Error........................................................................................................................... 301 Table 104 - Read DMA Error ............................................................................................................................. 302 Table 105 - Read Log Ext Error ......................................................................................................................... 303 Table 106 - Read PIO Error ............................................................................................................................... 304 Table 107 - Read Stream Error.......................................................................................................................... 305 Table 108 - Setmax Error.................................................................................................................................. 306 Table 109 - Write Log Error .............................................................................................................................. 307 Table 110 - SMART Error .................................................................................................................................. 309 Table 111 - Write Extended Error ...................................................................................................................... 310 Table 112 - Write Stream Error .......................................................................................................................... 311 xx Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS)
T13/1699-D Revision 3f
Table 113 - DCO Set Error ................................................................................................................................ 312 Table 114 - NOP Error ....................................................................................................................................... 314 Table 115 - PACKET Command Error ............................................................................................................... 315 Table 116 - Read DMA Queued Error ............................................................................................................... 316 Table 117 - Read DMA Queued Extended Error ............................................................................................... 317 Table 118 - SMART Read Log/SMART Read Data Error ................................................................................. 318 Table 119 - Read PIO Extended Error ............................................................................................................... 319 Table 120 - Read Native Max Extended Error ................................................................................................... 320 Table 121 - SETMAX Extended Error ................................................................................................................ 321 Table 122 - Write Error ..................................................................................................................................... 322 Table 123 - Write DMA Queued Error................................................................................................................ 323 Table 124 - NV Cache Add Abort ...................................................................................................................... 324 Table 125 - NV Cache Remove Abort ............................................................................................................... 325 Table 126 - Generic NV Cache Abort ................................................................................................................ 326 Table 127 - Log address definition..................................................................................................................... 327 Table 128 - General Purpose Log Directory ...................................................................................................... 328 Table 129 - Extended Comprehensive SMART error log................................................................................... 329 Table 130 - Extended Error log data structure ................................................................................................... 329 Table 131 - Command data structure ................................................................................................................ 330 Table 132 - Error data structure ......................................................................................................................... 331 Table 133 - State field values ............................................................................................................................ 331 Table 134 - Extended Self-test log data structure.............................................................................................. 332 Table 135 - Extended Self-test log descriptor entry ........................................................................................... 333 Table 136 - Read Stream Error Log................................................................................................................... 334 Table 137 - Error Log Entry ............................................................................................................................... 334 Table 138 - Write Stream Error Log ................................................................................................................... 335 Table 139 - SMART Log Directory ..................................................................................................................... 336 Table 140 - SMART summary error log ............................................................................................................. 337 Table 141 - Error log data structure ................................................................................................................... 337 Table 142 - Command data structure ................................................................................................................ 338 Table 143 - Error data structure ......................................................................................................................... 338 Table 144 - State field values ............................................................................................................................ 339 Table 145 - Comprehensive error log ................................................................................................................ 340 Table 146 - Self-test log data structure .............................................................................................................. 341 Table 147 - Self-test log descriptor entry ........................................................................................................... 341 Table 148 - Selective self-test log ...................................................................................................................... 342 Table 149 - Selective self-test feature flags ....................................................................................................... 343 Table 150 - General Statistics............................................................................................................................ 344 Table B.1 - Command Matrix ............................................................................................................................. 345 Table B.2 - Command codes (sorted by command code).................................................................................. 346 Table B.3 - Command codes (sorted by command name) ................................................................................ 349 Table B.4 - Historical Command Assignments................................................................................................... 352 Table B.5 - Historical SET FEATURE Code Assignments................................................................................. 358 Table 151 - SCT command using SMART WRITE LOG command................................................................... 370 Table 152 - SCT command using WRITE LOG EXT command ........................................................................ 370
xxi
T13/1699-D Revision 3f
xxii
T13/1699-D Revision 3f
Figures
Page Figure 1 - ATA document relationships................................................................................................................ 1 Figure 2 - State diagram convention .................................................................................................................... 8 Figure 3 - Byte, word, DWord and QWord relationships ...................................................................................... 9 Figure 4 - Device Configuration Overlay state diagram ..................................................................................... 17 Figure 5 - SET MAX security state diagram....................................................................................................... 21 Figure 6 - Long Logical and long Physical Sector Example............................................................................... 26 Figure 7 - Power management state diagram.................................................................................................... 31 Figure 8 - Security mode state diagram ............................................................................................................. 39 Figure 9 - Selective self-test span example ..................................................................................................... 205 Figure C.1 - Unaligned Write Example ............................................................................................................ 361 Figure D.1 - Example flowchart for SCT commands........................................................................................ 364 Figure D.2 - Example sequence for foreground write same with a repeating pattern ...................................... 365 Figure D.3 - Example sequence for foreground write same with a repeating sector ....................................... 365 Figure D.4 - Example sequence for writing data using an SCT command with no background activity .......... 366 Figure D.5 - Example sequence for reading data using an SCT command with no background activity......... 366 Figure D.6 - Example Sequence for a non-data SCT command with no background activity ......................... 367 Figure D.7 - Example sequence for writing data using an SCT command with background activity ............... 368 Figure D.8 - Example sequence for a non-data SCT command with background activity ............................... 369
xxiii
T13/1699-D Revision 3f
xxiv
T13/1699-D Revision 3f
Foreword
(This foreword is not part of this standard.) Requests for interpretation, suggestions for improvement and addenda, or defect reports are welcome. They should be sent to the INCITS Secretariat, ITI, 1250 Eye Street, NW, Suite 200, Washington, DC 20005-3922. This standard was processed and approved for submittal to ANSI by InterNational Committee for Information Technology Standards (INCITS). Committee approval of this standard does not necessarily imply that all committee members voted for approval. At the time it approved this standard, INCITS had the following members: Karen Higginbottom, Chair David Michael, Vice-chair Monica Vago, Secretary
Technical Committee T13 on ATA Interfaces, that reviewed this standard, had the following members and additional participants: Dan Colegrove, Chairman Jim Hatfield, Vice-Chairman Mark Overby, Secretary
Introduction
This standard encompasses the following: Clause 1 describes the scope. Clause 2 provides normative references for the entire standard. Clause 3 provides definitions, abbreviations, and conventions used within the entire standard. Clause 4 describes the general operating requirements of the command layer. Clause 5 describes the ATA protocols used by the commands in this standard Clause 6 describes status and error bits Clause 7 describes commands Clause 8 describes the SCT Command Transport Clause 9 describes command normal and error outputs Annex A provides command summaries Annex B describes considerations for using devices with non-512 byte sectors Annex C provides a tutorial on how to use SCT
xxv
T13/1699-D Revision 3f
xxvi
Packet delivered command sets Other related device specifications AT Attachment 8 Architecture Model (ATA8-AAM)
Figure 1 ATA document relationships ATA8-ACS maintains compatibility with the AT Attachment with Packet Interface - 7 standard (ATA/ATAPI-7), INCITS 397-2005 volume 1, and while providing additional functions. ATA8-ACS is not intended to require changes to devices or software that comply with previous ATA standards.
T13/1699-D Revision 3f
2 Normative references
The following standards 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 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 below. Copies of the following documents may be obtained from ANSI: Approved ANSI standards, approved and draft international and regional standards (ISO, IEC, CEN/CENELEC, ITUT), and approved and draft foreign standards (including BSI, 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 availability contact information is provided below as needed.
T13/1699-D Revision 3f
Table 2 References Under Development Name AT Attachment-8 - Parallel Transport (ATA8-APT) AT Attachment-8 ATA/ATAPI Architecture Model (ATA8-AAM) Method to Disable Data Transfer after Error Technical Report AT Attachment-8 ATA Serial Transport (ATA8-AST) ATA/ATAPI-7 Amendment 1 Project Number INCITS 1698D ISO/IEC 14776-881 INCITS 1700D ISO/IEC 14776-861 INCITS 1825DT INCITS 1697D ISO/IEC 14776-860 ANSI INCITS.397-2005/AM 1-2006 ISO/IEC 14776-971? INCITS T13/e05108 INCITS 2014D ISO/IEC FDIS 9594-8
Host Bus Adapter 2 (HBA-2) Information Technology - Open Systems Interconnection - The Directory: Public-key and attribute certificate frameworks, ITU, 2000
For more information on the current status of the T10 documents, contact INCITS. To obtain copies of T10 or SFF documents, contact Global Engineering.
T13/1699-D Revision 3f
3.1.7 3.1.8
3.1.16
T13/1699-D Revision 3f
hardware reset: the routine performed by a device after a hardware reset event as defined in ATA8-AAM. The hardware reset routine performed by the device includes the actions performed by the device for a software reset, and the actions defined in ATA8-AAM, this standard, and the applicable transport standards. host: The computer system executing the software BIOS and/or operating system device driver controlling the device and the adapter hardware for the ATA interface to the device. host adapter: The implementation of the host transport, link, and physical layers. LBA (logical block address): The value used to reference a logical sector. logical sector: A set of logical words accessed and referenced as a unit (see IDENTIFY DEVICE data words 118:117). These units are referenced by Logical Block Addresses. Master Password Capability: The Master Password Capability indicates whether or not the Master password may be used to unlock the device. This was formerly know as Security Level. native max address: The highest address a device accepts in the factory default condition, that is, the highest address that is accepted by the SET MAX ADDRESS command. NV Cache Pinned Set: The set of logical blocks that have been made un-removable from the NV Cache by the host. Writes to logical blocks represented in the NV Cache Pinned Set always results in valid data in the NV Cache Set. NV Cache Set: The set of logical blocks currently represented in the device's entire NV Cache. NV Cache Set Data: A data structure representing the standard format of transmitting logical blocks in the form of a list of LBA Range Entries. NV Cache Unpinned Set: The set of logical blocks that are represented in the NV Cache Set but not represented in the NV Cache Pinned Set. The NV Cache Pinned Set and the NV Cache Unpinned Set are mutually exclusive. NV Cache Unpinned Set is completely managed by the device and logical blocks represented in the NV Cache Unpinned Set can be added or removed from the NV Cache Set at any time. Password Attempt Counter Exceeded: There were too many attempts to unlock the device with an incorrect password. Further unlock attempts are denied until a power-on or hardware reset. This is a name associated with IDENTIFY DEVICE, word 128, bit 4. physical sector: One or more contiguous logical sectors that are read from or written to the device media in a single operation. PIO (programmed input/output) data transfer: PIO data transfers are performed using PIO commands and protocol. power cycle: the period from when power is removed from a host or device until the subsequent power-on event (see ATA8-AAM). power-on reset: the host specific routine performed by the host or the routine performed by a device after detecting a power-on event. The power-on reset routine performed by a device includes the actions performed by the device for a hardware reset and a software reset, and the actions defined in ATA8-AAM, this standard, and the applicable transport standards. queued: Command queuing allows the host to issue concurrent commands to the same device. Only commands included in the Tagged Command Queuing (TCQ) feature set may be queued. In this standard, the queue contains all commands for which command acceptance has occurred but command completion has not occurred. read command: A command that causes the device to transfer data from the device to the host (e.g., READ SECTOR(S), READ DMA, etc.). Release: The action by a device implementing the TCQ feature set that allows a host to select an alternate device or deliver another queued command. sector: See logical sector.
3.1.34
3.1.39
Security Is Disabled: The Security feature set is supported, but there is no valid User password. There is a Master password. Access to user data is not restricted by the Security feature set. The terms 'Security Is Locked' and 'Security Is Unlocked' are not applicable. (e.g., Security states SEC0, SEC1, SEC2). Security Is Enabled: The Security feature set is supported, and a valid User password has been set. (e.g., Security states SEC3, SEC4, SEC5, SEC6). Security Is Frozen: Security may be either enabled or disabled. Changes to Security states are not allowed until after the next power-on or hardware reset. (e.g., Security states SEC2, SEC6). Security Is Locked: Security is enabled. In addition, access to the device is restricted. (e.g., Security state SEC4). Security Is Not Frozen: Security may be either enabled or disabled. Changes to Security states are allowed (e.g., Security states SEC1, SEC4, SEC5). Security Is Not Supported: The Security feature set is not supported. The SECURITY commands (see 4.18.5) are not supported and shall be command aborted. IDENTIFY DEVICE reports that the Security feature set is 'not supported'. Security Is Unlocked: Security is enabled. A SECURITY UNLOCK command was successful, allowing access to the device. (e.g., Security state SEC5, SEC6). Security Level: See Master Password Capability. signature: A unique set of values placed in the return parameters used to distinguish command sets (e.g. General, ATAPI device, Port Multiplier) software reset: the routine performed by a device after a software reset event as defined in ATA8-AAM. The software reset routine includes the actions defined in ATA8-AAM, this standard, and the applicable transport standards. spin-down: the process of bringing a rotating media devices media to a stop. spin-up: the process of bringing a rotating media devices media to operational speed. Spindle State: The current state of the device's rotational media. There are 2possible states: spun up/spinning up and spun down/spinning down. Stream: a set of operating parameters specified by a host using the CONFIGURE STREAM command (see 7.9) to be used for subsequent READ STREAM commands and WRITE STREAM commands. TCG: Trusted Computing Group: An organization that develops and promotes open standards for hardware-enabled trusted computing and security technologies. See https://www.trustedcomputinggroup.org for more information. TCQ (Tagged Command Queuing): TCQ feature set (see 4.21). transport: The mechanism used to communicate with a device. See ATA8-APT and ATA8-AST. unaligned write: A write command that does not start at the first logical sector of a physical sector or does not end at the last logical sector of a physical sector. unrecoverable error: When the device sets either the ERR bit or the DF bit to one in the Status field at command completion. VS (vendor specific): Bits, bytes, fields, and code values that are reserved for vendor specific purposes. These bits, bytes, fields, and code values are not described in this standard, and implementations may vary among vendors. This term is also applied to levels of functionality whose definition is left to the vendor. write command: A command that causes the device to transfer data from the host to the device (e.g., WRITE SECTOR(S), WRITE DMA, etc.). WWN (world wide name): A 64-bit worldwide unique name based upon a companys IEEE identifier. (See IDENTIFY DEVICE data words (111:108), 7.16.7).
3.1.57
3.1.63 3.1.64
T13/1699-D Revision 3f
3.2 Conventions
3.2.1 Overview Lowercase is used 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.2.6 for the naming convention used for naming bits.) Names of device fields begin with a capital letter (e.g., Count). The expression word n or bit n shall be interpreted as indicating the content of word n or bit n. 3.2.2 Precedence If there is a conflict between text, figures, and tables, the precedence shall be tables, figures, then text. 3.2.3 Lists Unordered lists, those lists describing a sequence, are of the form: a) b) c) Ordered list are of the form: 1) 2) 3) 3.2.4 Keywords Several keywords are used to differentiate between different levels of requirements and options. 3.2.4.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 also be implemented. 3.2.4.2 mandatory: A keyword indicating items to be implemented as defined by this standard. 3.2.4.3 may: A keyword that indicates flexibility of choice with no implied preference. 3.2.4.4 N/A: A keyword that indicates a field is not applicable and has no defined value and should not be checked by the host or device. 3.2.4.5 obsolete: A keyword indicating that the designated bits, bytes, words, fields, and code values that may have been defined in previous standards are not defined in this standard and shall not be reclaimed for other uses in future standards. However, some degree of functionality may be required for items designated as obsolete to provide for backward compatibility. Obsolete commands should not be used by the host. Commands defined as obsolete may be command aborted by devices conforming to this standard. However, if a device does not command abort an obsolete command, the minimum that is required by the device in response to the command is command completion. 3.2.4.6 optional: A keyword that describes features that are not required by this standard. However, if any optional feature defined by the standard is implemented, the feature shall be implemented in the way defined by the standard. 3.2.4.7 prohibited: A keyword indicating that an item shall not be implemented by an implementation.
T13/1699-D Revision 3f
3.2.4.8 reserved: A keyword indicating reserved bits, bytes, words, fields, and code values that are set aside for future standardization. Their use and interpretation may be specified by future extensions to this or other standards. A reserved bit, byte, word, or field shall be cleared to zero, or in accordance with a future extension to this standard. The recipient shall not check reserved bits, bytes, words, or fields. Receipt of reserved code values in defined fields shall be treated as a command parameter error and reported by returning command aborted. 3.2.4.9 retired: A keyword indicating that the designated bits, bytes, words, fields, and code values that had been defined in previous standards are not defined in this standard and may be reclaimed for other uses in future standards. If retired bits, bytes, words, fields, or code values are used before they are reclaimed, they shall have the meaning or functionality as described in previous standards. 3.2.4.10 shall: A keyword indicating a mandatory requirement. Designers are required to implement all such mandatory requirements to ensure interoperability with other products that conform to this standard.
State designator: State_name State designator: State_name
3.2.4.11 should: A keyword indicating flexibility of choice with a Exit strongly preferred alternative. Equivalent to the Transition condition Entry condition condition phrase it is recommended. State_name Transition label Transition label Transition label 3.2.5 Numbering
Transition action Transition action Transition action
Numbers that are not immediately followed by a lowercase "b" or "h" are decimal values. Numbers that are Transition condition immediately followed by a lowercase "b" (e.g., 01b) are binary values. Numbers that are immediately followed by Transition label a lowercase "h" (e.g., 3Ah) are hexadecimal values. 3.2.6 Bit conventions 3.2.7 State diagram conventions State diagrams shall be as shown in Figure 2. Figure 2 State diagram convention Each state is identified by a state designator and a state name. The state designator is unique among all states in all state diagrams in this document. The state designator consists of a set of letters that are capitalized in the title of the figure containing the state diagram followed by a unique number. The state name is a brief description of the primary action taken during the state, and the same state name may appear in other state diagrams. If the same primary function occurs in other states in the same state diagram, they are designated with a unique letter at the end of the name. Additional actions may be taken while in a state and these actions are described in the state description text. Each transition is identified by a transition label and a transition condition. The transition label consists of the state designator of the state from which the transition is being made followed by the state designator of the state to which the transition is being made. In some cases, the transition to enter or exit a state diagram may come from or go to a number of state diagrams, depending on the command being executed. In this case, the state designator is labeled State_name. The transition condition is a brief description of the event or condition that causes the transition to occur and may include a transition action, indicated in italics, that is taken when the transition occurs. This action is described fully in the transition description text. Upon entry to a state, all actions to be executed in that state are executed. If a state is re-entered from itself, all actions to be executed in the state are executed again. Transitions from state to state shall be instantaneous. 3.2.8 Byte, word, DWord, and QWord Relationships Figure 3 illustrates the relationship between bytes, words DWords, and QWords.
Transition action State a re-entry Bit (n:m) denotes set of bits, for example, bits (7:0).
T13/1699-D Revision 3f
7 6 5 4 3 2 1 0
Byte
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
Word
Byte 1
Byte 0
31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0
DWord
Word 1
Word 0
Byte 3
Byte 2
Byte 1
Byte 0
Word 3
Word 2
Word 1
Word 0
QWord
Byte 7
Byte 6
Byte 5
Byte 4
Byte 3
Byte 2
Byte 1
Byte 0
T13/1699-D Revision 3f
10
T13/1699-D Revision 3f
Commands may be delivered in two forms. For devices that implement the General feature set, all commands and command parameters are delivered by transmitting a Command Block to the device. Devices that implement the PACKET feature set use DEVICE RESET and PACKET commands as well as a subset of the General feature set to control the device. The content of command packets delivered during execution of the PACKET command are not described in this standard. If the host issues a command that is indicated as not supported in the IDENTIFY DEVICE data, the device shall abort the command.
11
T13/1699-D Revision 3f h) i) j) k) l) SET FEATURES SET MULTIPLE MODE WRITE DMA WRITE MULTIPLE WRITE SECTOR(S)
The following General feature set commands are mandatory for all devices that are capable of only reading their media and do not implement the PACKET feature set: a) b) c) d) e) f) g) h) a) b) c) d) e) EXECUTE DEVICE DIAGNOSTIC IDENTIFY DEVICE READ DMA READ MULTIPLE READ SECTOR(S) READ VERIFY SECTOR(S) SET FEATURES SET MULTIPLE MODE DOWNLOAD MICROCODE NOP READ BUFFER WRITE BUFFER WRITE UNCORRECTABLE
The following General feature set commands are optional for devices not implementing the PACKET feature set:
The following Packet feature set command is prohibited for use by devices not implementing the PACKET feature set: a) DEVICE RESET
The following General feature set commands are optional for all devices implementing the PACKET feature set:
The following General feature set commands are prohibited for use by devices implementing the PACKET feature set. a) DOWNLOAD MICROCODE b) READ BUFFER c) READ DMA 12 Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS)
December 11, 2006 d) e) f) g) h) i) j) k) READ MULTIPLE READ VERIFY SET MULTIPLE MODE WRITE BUFFER WRITE DMA WRITE MULTIPLE WRITE SECTOR(S) WRITE UNCORRECTABLE
T13/1699-D Revision 3f
4.3.2 Identification of PACKET feature set devices The IDENTIFY DEVICE command shall be command aborted and shall return the signature unique to devices implementing the PACKET feature set. The IDENTIFY PACKET DEVICE command is used by the host to get identifying parameter information for a device implementing the PACKET feature set (See 7.16.5 and 7.17). 4.3.3 Processing resets for the PACKET feature set ATAPI devices process power-on resets, hardware resets, and software resets as described in this standard for ATA devices, except ATAPI devices return a unique signature when the reset is complete (see the appropriate transport standard for details). In addition, ATAPI devices implement the DEVICE RESET command (see 7.11) 4.3.4 The PACKET command The PACKET command allows a host to send a command to the device via a command packet. The command packet contains the command and command parameters that the device is to execute (See clause 1). The protocol for handling the transmission of the PACKET command and associated data is transport specific.
The 48-bit Address feature set operates in LBA only. Devices implementing the 48-bit Address feature set shall also implement commands that use 28-bit addressing. 28-bit and 48-bit commands may be intermixed. Support of the 48-bit Address feature set is indicated in the IDENTIFY DEVICE data. In a device implementing the 48-bit Address feature set, the Feature field, the Count field, the and LBA field are all 16 bits long.
13
T13/1699-D Revision 3f
The device shall indicate support of the 48-bit Address feature set in the IDENTIFY DEVICE data. In addition, IDENTIFY DEVICE data words (103:100) contain the maximum user LBA + 1 that is accessible by 48-bit addressable commands. If the value contained in IDENTIFY DEVICE data words (103:100) is equal to or less than 268,435,455, then the content of words (61:60) shall be as described in 4.10.4. If the value in contained IDENTIFY DEVICE data words (103:100) is greater than 268,435,455, then the maximum value in words (61:60) shall be 268,435,455. That is, if the device contains greater than the capacity addressable with 28-bit commands, words (61:60) shall describe the maximum capacity that is addressed by 28-bit commands. When the 48-bit Address feature set is implemented, the native maximum address is the highest address accepted by the device in the factory default condition using a 48-bit Address feature set command. The native maximum address is the value returned by a READ NATIVE MAX ADDRESS EXT command. If the native maximum address of a device is equal to or less than 268,435,455, a READ NATIVE MAX ADDRESS shall return the native maximum address. If the native maximum address is greater than 268,435,455, a READ NATIVE MAX ADDRESS command shall cause the device to return a maximum value of 268,435,454. When the 48-bit Address feature set is implemented, the SET MAX ADDRESS command shall execute as described in 7.48.2. However, in addition to modifying the content of words (61:60), the new content of (61:60) shall also be placed in words (103:100). When a SET MAX ADDRESS EXT command is issued and the address requested is greater than 268,435,455, words (103:100) shall be modified to reflect the requested value but words 60, and 61 shall not be modified. When a SET MAX ADDRESS EXT command is issued and the address requested is equal to or less than 268,435,455, words (103:100) shall be modified to reflect the requested value and words 60, and 61 shall be modified as described in 7.48.2.1. If a Host Protected Area has been created using the SET MAX ADDRESS command, all SET MAX ADDRESS EXT commands shall result in command aborted until the Host Protected Area is eliminated by use of the SET MAX ADDRESS command with the address value returned by the READ NATIVE MAX ADDRESS command. If a Host Protected Area has been created using the SET MAX ADDRESS EXT command, all SET MAX ADDRESS commands shall result in command aborted until the Host Protected Area is eliminated by use of the SET MAX ADDRESS EXT command with the address value returned by the READ NATIVE MAX ADDRESS EXT command. The WRITE DMA FUA EXT, WRITE DMA QUEUED FUA EXT, and WRITE MULTIPLE FUA EXT commands are unique in that regardless whether or not caching is enabled in the device, the user data shall be written to the media before ending status for the command is reported.
14
T13/1699-D Revision 3f
Devices reporting the value 848Ah in IDENTIFY DEVICE data word 0 or devices having bit 2 of IDENTIFY DEVICE data word 83 set to one shall support the CFA feature Set. If the CFA feature set is implemented, all the CFA commands and the Enable/Disable 8-Bit transfers shall be implemented. Support of DMA commands is optional for devices that support the CFA feature set. The CFA ERASE SECTORS command preconditions the logical sector for a subsequent CFA WRITE SECTORS WITHOUT ERASE or CFA WRITE MULTIPLE WITHOUT ERASE command to achieve higher performance during the write operation. The CFA TRANSLATE SECTOR command provides information about a logical sector such as the number of write cycles performed on that sector and an indication of the logical sectors erased precondition. The CFA REQUEST EXTENDED ERROR CODE command provides more detailed error information.
The Device Configuration Overlay feature set may affect words in IDENTIFY DEVICE data, IDENTIFY PACKET DEVICE data, and other commands. Certain bits in these words that indicate that a command, mode, capacity, or feature set is supported and enabled may be cleared by a DEVICE CONFIGURATION SET command. For a particular command, mode, capacity, or feature set, when a bit is cleared indicating that the device does not support the feature, the device shall not provide the feature. Also, the maximum capacity of the device may be Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) 15
T13/1699-D Revision 3f
reduced. Since a Host Protected Area may be lost if the capacity of the device is reduced, when a Host Protected Area is set the DEVICE CONFIGURATION SET command shall cause the device to return command aborted. The address value returned by a READ NATIVE MAX ADDRESS or READ NATIVE MAX ADDRESS EXT command is modified by the DEVICE CONFIGURATION SET command modifying the maximum capacity of the device. If a DEVICE CONFIGURATION FREEZE LOCK command has been completed by a device since the last power-on reset processed by the device, then the device shall return command aborted for any subsequent DEVICE CONFIGURATION SET command. During processing of a power-on reset or hardware reset, a device shall not change the settings made by a DEVICE CONFIGURATION SET command. A DEVICE CONFIGURATION IDENTIFY command specifies the selectable commands, modes, capacity, and feature sets that the device is capable of supporting. After the execution of a DEVICE CONFIGURATION SET command this information is no longer available from an IDENTIFY DEVICE or IDENTIFY PACKET DEVICE command. A DEVICE CONFIGURATION RESTORE command enables all capabilities that have been disabled by DEVICE CONFIGURATION SET command and returns the IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data to that indicated by the DEVICE CONFIGURATION IDENTIFY command. If the value returned in IDENTIFY DEVICE data words (103:100) is less than the native max address for a device (i.e., a host protected area has been established), then the device shall command abort a DEVICE CONFIGURATION RESTORE command. If a DEVICE CONFIGURATION FREEZE LOCK command has been completed by a device since the device processed a power-on reset, then the device shall abort any DEVICE CONFIGURATION RESTORE commands. A DEVICE CONFIGURATION FREEZE LOCK command prevents accidental modification of the state of the Device Configuration Overlay feature set. If a device has not completed a DEVICE CONFIGURATION SET command without error, then a device shall be in the DCO Factory_config state after processing a power-on reset. If a device has completed a DEVICE CONFIGURATION SET command without error, then a device shall be in the DCO Reduced_config state after processing a power-on reset. After completing a DEVICE CONFIGURATION FREEZE LOCK command without error, a device aborts all DEVICE CONFIGURATION SET, DEVICE CONFIGURATION IDENTIFY, and DEVICE CONFIGURATION RESTORE commands until after completing the subsequent power-on reset. If a device is in the DCO_locked state, then processing a hardware reset or software reset does not cause the device to change state.
16
T13/1699-D Revision 3f
Figure 4 and the text following the figure describe the operation of the Device Configuration Overlay feature set.
DCO1: DCO_locked DEVICE CONFIGURATION FREEZE LOCK, DEVICE CONFIGURATION IDENTIFY, DEVICE CONFIGURATION RESTORE, or DEVICE CONFIGURATION SET command DCO1:DCO1
DEVICE CONFIGURATION FREEZE LOCK command DCO0:DCO1 DEVICE CONFIGURATION RESTORE or Invalid DEVICE CONFIGURATION SET command (see text) DCO0:DCO0
DCO2: Reduced_config DEVICE CONFIGURATION FREEZE LOCK command DCO2:DCO1 DEVICE CONFIGURATION SET or Invalid DEVICE CONFIGURATION RESTORE command (see text) DCO2:DCO2
Valid DEVICE CONFIGURATION RESTORE command (see text) DCO2:DCO0 Power-up with reduced configuration set
DCO0: Factory_config State: This state is entered when the device powers-up with the factory
configuration set or a valid DEVICE CONFIGURATION RESTORE command is received. When in this state, the device shall support all commands, modes, features sets, and the capacity indicated by the response to a DEVICE CONFIGURATION IDENTIFY command. Transition DCO0:DCO1: When a DEVICE CONFIGURATION FREEZE LOCK command is received, the device shall return successful command completion and make a transition to the DCO1: DCO_locked state. Transition DCO0:DCO2: When a valid DEVICE CONFIGURATION SET command is received, the device shall return successful command completion and make a transition to the DCO2: Reduced_config state. See Transition DCO0:DCO0 for the definition of conditions that make a DEVICE CONFIGURATION SET command invalid. This transition is made even if the configuration described by the DEVICE SET CONFIGURATION SET command is the same as the factory configuration. Transition DCO0:DCO0: When a DEVICE CONFIGURATION RESTORE command is received, the device shall return command aborted and make a transition to the DCO0: Factory_config state. When an invalid DEVICE CONFIGURATION SET command is received, the device shall return command aborted and make a
17
T13/1699-D Revision 3f
transition to the DCO0: Factory_config state. A DEVICE CONFIGURATION SET command is invalid if the DEVICE CONFIGURATION SET command requests: a) a Host Protected Area has been established using the SET MAX ADDRESS command. b) the elimination of support of a Multiword or Ultra DMA mode if that mode is currently selected or a higher numbered mode is currently selected. c) the elimination of support of the Host Protected Area feature set if a Host Protected Area has been established using a SET MAX ADDRESS command. d) the elimination of support of the Power-up in Standby feature set if the feature set has been enabled by a jumper. e) the elimination of support of the Security feature set if the feature set has been enabled. f) the elimination of support of the SMART feature set if bits (2:1) of word 7 are not cleared to zero or if the SMART feature set has been enabled by use of the SMART ENABLE OPERATIONS command.
DCO1: DCO_locked State: This state is entered when a DEVICE CONFIGURATION RESTORE
command is received. When in this state, all DEVICE CONFIGURATION FREEZE LOCK, DEVICE CONFIGURATION IDENTIFY, DEVICE CONFIGURATION SET, or DEVICE CONFIGURATION RESTORE commands shall return command abort and shall remain in the locked state. Transition DCO1:DCO1: When a DEVICE CONFIGURATION FREEZE LOCK, DEVICE CONFIGURATION IDENTIFY, DEVICE CONFIGURATION SET, or DEVICE CONFIGURATION RESTORE command is received, the device shall return command aborted and make a transition to the DCO1: DCO_locked state.
DCO2: Reduced_config State: This state is entered when the device powers-up with a reduced configuration set or a valid DEVICE CONFIGURATION SET command is received.
When in this state, the device shall support all commands, modes, features sets, and the capacity specified by the DEVICE CONFIGURATION SET command that caused this state to be entered. Transition DCO2:DCO1: When a DEVICE CONFIGURATION FREEZE LOCK command is received, the device shall return successful command completion and make a transition to the DCO1: DCO_locked state. Transition DCO2:DCO0: When a valid DEVICE CONFIGURATION RESTORE command is received, the device shall return successful command completion and make a transition to the DCO0: Factory_config state. See Transition DCO2:DCO2 for the definition of conditions that make a DEVICE CONFIGURATION RESTORE command invalid. Transition DCO2:DCO2: When a DEVICE CONFIGURATION SET command is received, the device shall return command aborted and make a transition to the DCO2: Reduced_config state. When an invalid DEVICE CONFIGURATION RESTORE command is received, the device shall return command aborted and make a transition to the DCO2: Reduced_config state. A DEVICE CONFIGURATION RESTORE command is invalid if a Host Protected Area has been established using the SET MAX ADDRESS command.
T13/1699-D Revision 3f
Devices supporting these extensions shall set IDENTIFY DEVICE data word 82 bit 10 or IDENTIFY PACKET DEVICE data word 82 bit 10 to one, and shall set IDENTIFY DEVICE DATA word 83 bit 8 or IDENTIFY PACKET DEVICE data word 83 bit 8 to one. 4.10.3 48-Bit extensions The READ NATIVE MAX ADDRESS or READ NATIVE MAX ADDRESS EXT command allows the host to determine the maximum native address space of the device even when a protected area has been allocated. The SET MAX ADDRESS or SET MAX ADDRESS EXT command allows the host to redefine the maximum LBA of the user accessible address space. That is, when the SET MAX ADDRESS or SET MAX ADDRESS EXT command is issued with a maximum address less than the native maximum address, the device reduces the user accessible address space to the maximum specified by the command, providing a protected area above that maximum address. The SET MAX ADDRESS or SET MAX ADDRESS EXT command shall be immediately preceded by a READ NATIVE MAX ADDRESS or READ NATIVE MAX ADDRESS EXT command. After the SET MAX ADDRESS or SET MAX ADDRESS EXT command has been issued, the device shall report only the reduced user address space in IDENTIFY DEVICE data words (61:61) and IDENTIFY DEVICE data words (103:100). Any read or write command to an address above the maximum address specified by the SET MAX ADDRESS or SET MAX ADDRESS EXT command shall cause command completion with the IDNF bit set to one and ERR set to one, or command aborted. A Volatility bit in the Count field allows the host to specify if the maximum address set is preserved after a power-on reset or a hardware reset. During processing a power-on reset or hardware reset, the device sets the maximum address to the last non-volatile address setting regardless of subsequent volatile SET MAX ADDRESS or SET MAX ADDRESS EXT commands. If the SET MAX ADDRESS or SET MAX ADDRESS EXT command is issued with a value that exceeds the native maximum address command aborted shall be returned. Typical use of these commands would be: After a power-on reset or a hardware reset is processed: 1) BIOS receives control after the reset;
19
T13/1699-D Revision 3f
2) BIOS issues a READ NATIVE MAX ADDRESS or READ NATIVE MAX ADDRESS EXT command to find the max capacity of the device; 3) BIOS issues a SET MAX ADDRESS or SET MAX ADDRESS EXT command to the values returned by READ NATIVE MAX ADDRESS or READ NATIVE MAX ADDRESS EXT; 4) BIOS reads configuration data from the highest area on the disk; 5) BIOS issues a READ NATIVE MAX ADDRESS or READ NATIVE MAX ADDRESS EXT command followed by a SET MAX ADDRESS or SET MAX ADDRESS EXT command to reset the device to the size of the file system. On save to disk 1) BIOS receives control prior to shut down; 2) BIOS issues a READ NATIVE MAX ADDRESS or READ NATIVE MAX ADDRESS EXT command to find the max capacity of the device; 3) BIOS issues a volatile SET MAX ADDRESS or SET MAX ADDRESS EXT command to the values returned by READ NATIVE MAX ADDRESS or READ NATIVE MAX ADDRESS EXT; 4) Memory is copied to the reserved area; 5) Shut down completes; 6) During processing a power-on reset or hardware reset, the device sets the maximum address to the last non-volatile address setting regardless of subsequent volatile SET MAX ADDRESS or SET MAX ADDRESS EXT commands. These commands are intended for use only by system BIOS or other low-level boot time process. Using these commands outside BIOS controlled boot or shutdown may result in damage to file systems on the device. Devices should return command aborted if a subsequent non-volatile SET MAX ADDRESS or SET MAX ADDRESS EXT command is received after a power-on or hardware reset. The SET MAX SET PASSWORD command allows the host to define the password to be used during the current power cycle. The password does not persist after a power-on reset has been processed but does persist after a hardware reset or a software reset has been processed. This password is not related to the password used for the Security Mode Feature set. When the password is set the device is in the Set_Max_Unlocked mode. The SET MAX LOCK command provides a method for the host to disable the SET MAX commands (except SET MAX UNLOCK) until after the device has processed the next power-on reset or command completion of a SET MAX UNLOCK command. When the SET MAX LOCK command is completed the device is in the Set_Max_Locked mode. The SET MAX UNLOCK command changes the device from the Set_Max_Locked mode to the Set_Max_Unlocked mode. The SET MAX FREEZE LOCK command provides a method for the host to disable the SET MAX commands (including SET MAX UNLOCK) until after the device has processed the next power-on reset. When the SET MAX FREEZE LOCK command is completed the device is in the Set_Max_Frozen mode. 4.10.4 IDENTIFY DEVICE data When the host issues a SETMAX ADDRESS or SETMAX ADDRESS EXT, several IDENTIFY DEVICE data words may be affected. The following guidlines are used for setting IDENTIFY DEVICE data: a) if the 48 bit address feature set is not supported then words 61:60 shall contain the total number of user addressable sectors and words 103:100 shall be reserved; b) if the 48 bit address feature set is supported and the total number of user addressable sectors is less than or equal to 0FFF_FFFFh then Words 61:60 and 103:100 shall contain the total number of user addressable sectors; c) if the 48 bit address feature set is supported and the total number of user addressable sectors is greater than 0FFF_FFFFh then words 61:60 shall contain 0FFF_FFFFh and words 103:100 shall contain the total number of user addressable sectors. 4.10.5 BIOS determination of SET MAX security extension status When the device is locked IDENTIFY DEVICE data word 86 bit 8 or IDENTIFY PACKET DEVICE data word 86 bit 8 shall be set to one.
20
T13/1699-D Revision 3f
To allow for multiple BIOSs to gain access to the protected area the host BIOS should only lock the protected area immediately prior to booting the operating system. Figure 5 is the SET MAX state diagram.
SM0:Set_Max_Security_Inactive SET MAX ADDRESS command SM0a:SM0 SET MAX LOCK, SET MAX UNLOCK, or SET MAX FREEZE LOCK command SM0b:SM0 SET MAX SET PASSWORD command SM0:SM1 SET MAX ADDRESS command SM1a:SM1 SM1:Set_Max_Unlocked
SET MAX SET PASSWORD command SM1b:SM1 SET MAX UNLOCK command SM1c:SM1
Power on
SM2:Set_Max_Locked SET MAX ADDRESS or SET MAX SET PASSWORD command SM2a:SM2 SET MAX UNLOCK command SM2:SM1 SET MAX FREEZE LOCK command (optional) SM2:SM3 SET MAX LOCK command SM1:SM2
SM3:Set_Max_Frozen
SET MAX LOCK command SM2b:SM2 SET MAX ADDRESS, SET MAX SET PASSWORD, SET MAX UNLOCK, SET MAX FREEZE LOCK or SET MAX LOCK command SM3:SM3
Figure 5 SET MAX security state diagram SM0: Set_Max_Security_Inactive: This state shall be entered when the device is powered-on. When in this state, SET MAX security is disabled. Transition SM0a:SM0: When a SET MAX ADDRESS command is received, the command shall be executed and the device shall make a transition to the SM0: Set_MAX_Security_Inactive state. Transition SM0b:SM0: When a SET MAX LOCK, SET MAX UNLOCK, or SET MAX FREEZE LOCK command is received, the device shall abort the command and make a transition to the SM0: Set_MAX_Security_Inactive state. Transition SM0:SM1: When a SET MAX SET PASSWORD command is received, the device shall make a transition to the SM1: Set_Max_Unlocked state. SM1: Set_Max_Unlocked: This state is entered when a SET MAX SET PASSWORD or a SET MAX UNLOCK command is received. Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) 21
T13/1699-D Revision 3f
When in this state, a SET MAX security password has been established and the SET MAX security is unlocked. IDENTIFY DEVICE data word 86 bit 8 shall be set to one. Transition SM1a:SM1: When a SET MAX ADDRESS command is received, the command shall be executed and the device shall make a transition to the SM1: Set_MAX_Unlocked state. Transition SM1b:SM1: When a SET MAX SET PASSWORD is received, the password stored by the device shall be changed to the new value and the device shall make a transition to the SM1: Set_MAX_Unlocked state. Transition SM1c:SM1: When a SET MAX UNLOCK command is received, the command shall not be executed and the device shall make a transition to the SM1: Set_MAX_Unlocked state. Transition SM1:SM2: When a SET MAX LOCK command is received, the device shall make a transition to the SM2: Set_Max_Locked state. Transition SM1:SM3: When a SET MAX FREEZE LOCK command is received, the device shall make a transition to the SM3: Set_Max_Frozen state. SM2: Set_Max_Locked: This state is entered when a SET MAX LOCK command is received. When in this state, a SET MAX security password has been established and the SET MAX security is locked. IDENTIFY DEVICE data word 86 bit 8 shall be set to one. Transition SM2a:SM2: When a SET MAX ADDRESS or SET MAX SET PASSWORD command is received, the command shall be aborted and the device shall make a transition to the SM2: Set_Max_Locked state. Transition SM2b:SM2: When a SET MAX LOCK command is received, the command shall be executed and the device shall make a transition to the SM2: Set_Max_Locked state. Transition SM2:SM1: When a SET MAX UNLOCK command is received, the device shall make a transition to the SM1: Set Max Unlocked state. Transition SM2:SM3: When a SET MAX FREEZE LOCK command is received, the device may make a transition to the SM3: Set_Max_Frozen state. SM3: Set_Max_Frozen: This state is entered when a SET MAX FREEZE LOCK command is received. In this state, the device may not transition to any other state except by a power cycling. When in this mode IDENTIFY DEVICE data word 86 bit 8 or IDENTIFY PACKET DEVICE data word 86 bit 8 shall be set to one. Transition SM3:SM3: When a SET MAX ADDRESS, SET MAX SET PASSWORD, SET MAX UNLOCK, SET MAX FREEZE LOCK, or SET MAX LOCK command is received, the command shall be aborted and the device shall make a transition to the SM3: Set_Max_Frozen state.
Table 4 Block Size By Command (part 1 of 4) Command ADD LBA(S) TO NV CACHE PINNED SET CFA ERASE SECTORS CFA REQUEST EXTENDED ERROR CODE 22 Words Transferred 256 -
December 11, 2006 Table 4 Block Size By Command (part 2 of 4) Command CFA TRANSLATE SECTOR CFA WRITE MULTIPLE WITHOUT ERASE CFA WRITE SECTORS WITHOUT ERASE CHECK MEDIA CARD TYPE CHECK POWER MODE CONFIGURE STREAM DEVICE CONFIGURATION DEVICE RESET DOWNLOAD MICROCODE EXECUTE DEVICE DIAGNOSTIC FLUSH CACHE FLUSH CACHE EXT FLUSH NV CACHE GET MEDIA STATUS IDENTIFY DEVICE IDENTIFY PACKET DEVICE IDLE IDLE IMMEDIATE MEDIA EJECT MEDIA LOCK MEDIA UNLOCK NOP PACKET QUERY NV CACHE MISSES QUERY NV CACHE PINNED SET REMOVE LBA(S) FROM NV CACHE PINNED SET READ BUFFER READ DMA READ DMA EXT READ DMA QUEUED READ DMA QUEUED EXT READ LOG EXT READ LOG DMA EXT READ MULTIPLE READ MULTIPLE EXT READ NATIVE MAX ADDRESS READ NATIVE MAX ADDRESS EXT READ SECTOR(S) READ SECTOR(S) EXT READ STREAM DMA EXT READ STREAM EXT READ VERIFY SECTOR(S)
T13/1699-D Revision 3f
Words Transferred IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) 256 256 256 256 256 256 IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) 256 256 IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) 23
T13/1699-D Revision 3f Table 4 Block Size By Command (part 3 of 4) Command RETURN FROM NV CACHE POWER MODE READ VERIFY SECTOR(S) EXT SECURITY DISABLE PASSWORD SECURITY ERASE PREPARE SECURITY ERASE UNIT SECURITY FREEZE LOCK SECURITY SET PASSWORD SECURITY UNLOCK SERVICE SET FEATURES SET MAX SET PASSWORD SET MAX LOCK SET MAX FREEZE LOCK SET MAX UNLOCK SET MAX ADDRESS SET MAX ADDRESS EXT SET MULTIPLE MODE SET NV CACHE POWER MODE SLEEP SMART DISABLE OPERATIONS SMART ENABLE/DISABLE AUTOSAVE SMART ENABLE OPERATIONS SMART EXECUTE OFF-LINE IMMEDIATE SMART READ DATA SMART READ LOG SMART RETURN STATUS SMART WRITE LOG STANDBY STANDBY IMMEDIATE TRUSTED RECEIVE TRUSTED RECEIVE DMA TRUSTED SEND TRUSTED SEND DMA WRITE BUFFER WRITE DMA WRITE DMA EXT WRITE DMA FUA EXT WRITE DMA QUEUED WRITE DMA QUEUED EXT WRITE DMA QUEUED FUA EXT WRITE LOG EXT WRITE LOG DMA EXT WRITE MULTIPLE 24 Words Transferred 256 256 256 256 256 256 256 256 256 256 256 256 256 256
IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) 256 256 IDENTIFY DEVICE data words (118:117)
December 11, 2006 Table 4 Block Size By Command (part 4 of 4) Command WRITE MULTIPLE EXT WRITE MULTIPLE FUA EXT WRITE SECTOR(S) WRITE SECTOR(S) EXT WRITE STREAM DMA EXT WRITE STREAM EXT
T13/1699-D Revision 3f
Words Transferred IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117) IDENTIFY DEVICE data words (118:117)
Table 4 describes the command behavior of drives that have been manufactured with the Long Logical Sector feature set. Data transfer commands transfer either the long logical sector length or 256 words depending on the command. For example, Read and Write Extended commands transfer data in long logical sectors while READ LOG EXT and WRITE LOG EXT commands transfer 256 word blocks of data, regardless of the logical sector length. Figure 6 example 2 shows a diagram of a device formatted with long logical sectors. 4.11.1.1 Devices Implementing the Long Physical Sector feature set and the Long Logical Feature Sector Set The long physical sector feature set and the long logical sector feature set are not exclusive. Figure 6 example 4 illustrates a device implementing both the Long Physical Sector and Long Logical Sector feature sets.
logical sector 1
25
T13/1699-D Revision 3f
logical sector 0
There are 4 logical sectors within one physical sector, and the first logical sector is in the second half. The proposed offset would be: 3, and the value in word 209 would be 4003h. physical sector 0 (inaccessible) (inaccessible) physical sector 1 logical 1 logical 2
(inaccessible)
logical 0
logical 3
logical 4
1) Conventional Logical Sector Format: 512 Bytes Per LBA Address 512 512 512 512 512 512 512 512 LBA LBA LBA LBA LBA LBA LBA LBA ...
2) Long Logical Sector Format Example: 524 Bytes Per LBA Address 524 B 524 B 524 B 524 B 524 B 524 B 524 B LBA 0 LBA 1 LBA 2 LBA 3 LBA 4 LBA 5 LBA 6 ...
3) Long Physical Sector Format Example: 512 Bytes Per LBA Address, 2048 Bytes Per Physical Sector 512 LBA 512 LBA 512 LBA 512 LBA 512 LBA 512 LBA 512 LBA 512 LBA ... ...
Physical Sector 0
Physical Sector 1
4) Long Logical and Long Physical Sector Format Example: 524 Bytes Per LBA Address, 2096 Bytes Per Physical Sector 524 B LBA 0 524 B LBA 1 524 B LBA 2 524 B LBA 3 524 B LBA 4 524 B LBA 5 524 B LBA 6 ... ...
Physical Sector 0
Physical Sector 1
26
T13/1699-D Revision 3f
The Media Card Pass Through Command feature set uses the command codes D1h, D2h, D3h, and D4h and bits in IDENTIFY DEVICE data word 84 and IDENTIFY DEVICE data word 87. The command codes D2h through D4h are reserved for the Media Card Pass Through Command feature set if this feature set is enabled by the CHECK MEDIA CARD TYPE command (D1h). This feature set embeds small-format flash memory card commands inside the ATA commands. The adapters firmware passes the embedded memory cards command to the memory card as is from the ATA command. The Media Card Pass Through Command feature set reduces the number of commands required for this feature set regardless of the number or type of memory card commands. It also reduces the adapters firmware overhead in processing them. As new memory cards types are defined in the market, they may all be supported within this one feature. The commands unique to the Media Card Pass Through Command feature set are: a) CHECK MEDIA CARD TYPE b) Command codes D2h through D4h The CHECK MEDIA CARD TYPE command returns the supporting status of the device to this feature set. It also enables and disables the device from running the Media Card Pass Through Command feature set. When the Media Card Pass Through Command feature set is disabled, the command codes D2h through D4h shall not be interpreted as Media Card Pass Through Command feature set commands and the device shall return command aborted. A device shall disable the Media Card Pass Through Command feature set during the processing of a power-on reset, a hardware reset, or a software reset. The definitions of the commands D2h-D4h are media card type dependent. Table 5 lists the Media card types and their associated reference document. Table 5 Media Card type references Media Card Type SD Card Smart Media Reference Document SD Card ATA Command Extension (SDA 3C) Smart Media ATA Command Extension (SSFDC Forum)
27
There are two common scenarios where a host will pin an LBA: it wants to pin an LBA for subsequent read operations, or it wants to pin an LBA which is about to be written to. a) If the host knows that the logical blocks are about to be read, or frequently read from, the host will want to have the sector data come from the magnetic media and will issue the Add command with the PI set. Example: A) Preloading frequent randomly accessed OS files. B) Preloading boot files in preparation for a system reboot. b) If the host knows that the logical blocks are about to be written to, the host will want to have the sector data come from the host and will issue the Add command with PI cleared. The device should not implement a background population of the pinned logical blocks from its media. Example: The writing of the hibernate file in preparation for system hibernation. 4.14.3 Cache Management 4.14.3.1 Overview The NV Cache management refers to the use of ATA commands to query or take action on the contents of the NV Cache Pinned Set. It involves transmitting lists of logical blocks that need to be used in an NV Cache management action. Some NV Cache management actions take lists of logical blocks as inputs and some NV Cache management actions give lists of logical blocks as outputs. When sending logical blocks between the host and the device, logical blocks are grouped into ranges. LBA ranges consist of an initial LBA and a number which indicates the sequential logical blocks after the initial LBA in the range. More than one LBA range can be sent in a single Add or Remove command. A list of LBA ranges sent in a single Add or Remove command is referred to as the command's NV Cache Set Data. 4.14.3.2 LBA Range Entry An individual LBA range is called an LBA Range Entry and is represented by 8 bytes. The LBA is expressed by the LBA Range Entry's first 6 bytes and the range length is a zero based number (i.e. 0=0 , 1=1, etc.) represented by the remaining 2 bytes. If the 2 byte range length is 0 then the LBA Range Entry is not valid and should be discarded as padding. Examples: a) If logical blocks 11, 12, 13, 14, 15, 16, 17, and 18 were in the NV Cache Pinned Set and logical blocks 10 and 19 were not, logical blocks 11 through 18 would make one LBA Range Entry which would have the LBA 11 as its first 48 bits and the value of 8 as its next 16 bits. (0000 0000 000B 0008h). b) If only the single LBA 20 was represented in an LBA Range Entry the range value would be 1. (0000 0000 0014 0001h) The largest range that can be specified in a LBA Range Entry is 65535 and is specified as a range value of all Fs. Multiple LBA Range Entries must be used to specify larger range values. 4.14.3.3 NV Cache Set Data NV Cache Set Data consists of an ascending ordered, non overlapping series of 8 byte LBA Range Entries which have 8 byte alignment within the NV Cache Set Data. An NV Cache Set Data transfer is a multiple of 512 bytes. In the event that not all of the last block's 64 entries are needed, the unused LBA Range Entries must have their LBA and range length set to 0. During an Add command, the Populate Immediately (PI) bit in the command applies to all logical blocks specified in the NV Cache Set Data. (See the Pinning section above) 4.14.3.4 NV Cache Remaining for Pinned logical blocks The NV Cache can run out of space to hold any more pinned logical blocks data. The number of the remaining available spaces shall be returned to the host during the completion of NV Cache Commands. This is referred to as logical blocks Remaining (see 7.21.3.2 and 7.21.3.3 for a description of the return data structure.)
28
T13/1699-D Revision 3f
logical blocks Remaining is 6 byte number that always represents the number of logical blocks in the total NV Cache size minus the number of logical blocks currently in the Pinned Cache Set. 4.14.3.5 NV Cache Set Data as Input NV Cache commands that take an NV Cache Set Data as Input can be thought of as the Set operations. Set operations change the members of the NV Cache Pinned Set. 4.14.3.6 NV Cache Set Data as Output NV Cache commands that return an NV Cache Set Data as Output can be thought of as the GET operations. The GET operations return the members of the current NV Cache Pinned Set or NV Cache misses members. 4.14.4 NV Cache behavior after a power-on event 4.14.4.1 Query NV Cache Misses In order to gather information about the system's BIOS read and write behavior, a query of NV Cache misses is necessary (see 7.21.5). 4.14.4.2 Rotating media state after power-on event If the NV Cache Power Mode is set in a device, then the device should not spin up its rotating media after a power-on event until the device receives a read or write command that requires media access. 4.14.5 Preparing to Pin a Large NV Cache Set Data Before the pinning of a large number of logical blocks in the NV Cache Pinned Set it is desirable for the host to instigate a flush of some or all of the NV Cache Unpinned Set. This ensures that the potentially lengthy flushing operation in a large NV Cache is completed as quickly and early as possible. This is accomplished using the Flush NV Cache command described in section 7.1.5.
T13/1699-D Revision 3f
e) A Device Configuration Overlay command that disables the NV Cache Power Mode support in the device causes the NV Cache Power Mode to be cleared. 4.15.2 Check Power Mode Changes Because much of the aggressive policy to remove power from the device's rotational media is vendor specific the Check Power Modes command must be updated to be able to respond with a value that indicates that the device is in the NV Cache Power Mode.
A device that implements the PACKET feature set and implements the Power Management feature set shall implement the following minimum set of functions: a) b) c) d) CHECK POWER MODE command IDLE IMMEDIATE command SLEEP command STANDBY IMMEDIATE command
4.16.1 Power management commands The CHECK POWER MODE command allows a host to determine if a device is currently in, going to or leaving Standby or Idle mode. The CHECK POWER MODE command shall not change the power mode or affect the operation of the Standby timer. The IDLE and IDLE IMMEDIATE commands move a device to Idle mode immediately from the Active or Standby modes. The IDLE command also sets the Standby timer count and enables or disables the Standby timer. The STANDBY and STANDBY IMMEDIATE commands move a device to Standby mode immediately from the Active or Idle modes. The STANDBY command also sets the Standby timer count and enables or disables the Standby timer. The SLEEP command moves a device to Sleep mode. The device's interface becomes inactive at command completion of the SLEEP command. A device only transitions from Sleep mode after processing a hardware reset, a software reset, or a DEVICE RESET command. 4.16.2 Standby timer The Standby timer provides a method for the device to automatically enter Standby mode from either Active or Idle mode following a host programmed period of inactivity. If the Standby timer is enabled and if the device is in the Active or Idle mode, the device waits for the specified time period and if no command is received, the device automatically enters the Standby mode. If the Standby timer is disabled, the device may automatically enter Standby mode.
30
December 11, 2006 4.16.3 Power modes Figure 7 shows the set of mode transitions that shall be implemented.
T13/1699-D Revision 3f
PM0: Active
Power-up with Power-up in Stand-by feature not implemented or not enabled reset
PM0:PM0
SLEEP command
PM1: Idle
reset
PM1:PM1
IDLE or IDLE IMMEDIATE command, or vendor specific Implementation
PM0:PM2
Media access required
PM0:PM1
Media access required
PM2:PM0
Power-up with Power-up in Standby implemented reset and enabled PM2:PM2
PM1:PM0
STANDBY or STANDBY IMMEDIATE command, vendor specific implementation, or STANDBY timer expiration
PM1:PM2
IDLE or IDLE IMMEDIATE command
PM2:PM3
SLEEP command
reset PM3:PM2
PM1:PM3
Figure 7 Power management state diagram PM0: Active: This mode shall be entered when the device receives a media access command while in Idle or Standby mode. This mode shall also be entered when the device is powered-up with the Power-Up In Standby feature not implemented or not enabled (see 4.17). In Active mode the device is capable of responding to commands. During the execution of a media access command a device shall be in Active mode. Power consumption is greatest in this mode. Transition PM0:PM0: The device shall transition to the PM0:Active mode after processing a hardware reset, software reset, or DEVICE RESET command. Transition PM0:PM1: When an IDLE or IDLE IMMEDIATE command is received or when a vendor specific implementation determines a transition is required, then the device shall make a transition to the PM1:Idle mode.
31
T13/1699-D Revision 3f
Transition PM0:PM2: When a STANDBY or STANDBY IMMEDIATE command is received, the Standby timer expires, or a vendor specific implementation determines a transition is required, then the device shall make a transition to the PM2:Standby mode. Transition PM0:PM3: When a SLEEP command is received, the device shall make a transition to the PM3:Sleep mode. PM1: Idle: This mode shall be entered when the device receives an IDLE or IDLE IMMEDIATE command. Some devices may perform vendor specific internal power management and make a transition to the Idle mode without host intervention. In Idle mode the device is capable of responding to commands but the device may take longer to complete commands than when in the Active mode. Power consumption may be reduced from that of Active mode. Transition PM1:PM0: When a media access is required, the device shall make a transition to the PM0:Active mode. Transition PM1:PM1: The device shall transition to the PM1:Idle mode after processing a hardware reset, software reset, or DEVICE RESET command. Transition PM1:PM2: When a STANDBY or STANDBY IMMEDIATE command is received, the Standby timer expires, or a vendor specific implementation determines a transition is required, then the device shall make a transition to the PM2:Standby mode. Transition PM1:PM3: When a SLEEP command is received, the device shall make a transition to the PM3:Sleep mode. PM2: Standby: This mode shall be entered when the device receives a STANDBY command, the device receives a STANDBY IMMEDIATE command, the Standby timer expires, or the NV Cache Power mode timer expires. Some devices may perform vendor specific internal power management and make a transition to the Standby mode without host intervention. This mode shall also be entered when the device is powered-up with the Power-Up In Standby feature implemented and enabled. In Standby mode the device is capable of responding to commands but the device may take longer to complete commands than in the Idle mode. The time to respond could be as long as 30 s. Power consumption may be reduced from that of Idle mode. Transition PM2:PM0: When a media access is required, the device shall make a transition to the PM0:Active mode. Transition PM2:PM1: When an IDLE or IDLE IMMEDIATE command is received, or a vendor specific implementation determines a transition is required, then the device shall make a transition to the PM1:Idle mode. Transition PM2:PM2: The device shall transition to the PM2:Standby mode after processing a hardware reset, software reset, or DEVICE RESET command. Transition PM2:PM3: When a SLEEP command is received, the device shall make a transition to the PM3:Sleep mode. PM3: Sleep: This mode shall be entered when the device receives a SLEEP command. A device transitions from Sleep mode only after processing a hardware reset, a software reset, or a DEVICE RESET command. The time to respond could be as long as 30 s. Sleep mode provides the lowest power consumption of any mode. In Sleep mode, see the transport standard for a description of the device's interface behavior. Transition PM3:PM2:, A device shall transition to the PM2:Standby mode after processing a hardware reset, software reset, or DEVICE RESET command.
T13/1699-D Revision 3f
disabled via the SET FEATURES command. The IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data indicates whether this feature set is implemented and/or enabled. Once this feature is enabled in a device, the device shall not disable the feature as a result of processing a power-on reset, a hardware reset, or a software reset. A device may implement a SET FEATURES subcommand that notifies the device to spin-up to the Active state when the device has powered-up into Standby. If the device implements this SET FEATURES subcommand and power-up into Standby is enabled, the device shall remain in Standby until the SET FEATURES subcommand is received. If the device implements this SET FEATURES subcommand, the fact that the feature is implemented is reported in the IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data. If the device: a) implements the Enable/disable Power-up in Standby subcommand, b) power-up into Standby is enabled, and c) an IDENTIFY DEVICE or IDENTIFY PACKET DEVICE is received while the device is in Standby as a result of powering up into Standby, the device shall respond to the command and remain in Standby without spinning-up. If the device has IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data that requires access to the media, the device shall set word 0 bit 2 to one to indicate that the response is incomplete. At a minimum, word 0 and word 2 shall be correctly reported. Those fields that cannot be provided shall be filled with zeros. Once a device is able to return all data for an IDENTIFY DEVICE command or IDENTIFY PACKET DEVICE command, the device shall return all data for those commands until after processing the next power-on reset. If the device does not implement the SET FEATURES subcommand to spin-up the device after power-up and power-up into Standby is enabled, the device shall spin-up upon receipt of the first command that requires the device to access the media.
33
A device with Security enabled has two ways of using the Master password. This capability has values of 'High' or 'Maximum'. When the Master Password Capability is set to High, either the User or Master password may be used interchangably. See table 6. When the Master Password Capability is set to Maximum, the Master password cannot be used with the SECURITY DISABLE PASSWORD and SECURITY UNLOCK commands. The SECURITY ERASE UNIT command, however, does accept either a valid User or Master password. Table 6 Interaction of Master Password Capability and Passwords (when Security is not frozen) Master Password Capability N/A N/A High High Maximum Maximum Actions Taken by Security Commands SECURITY SECURITY SECURITY ENABLE UNLOCK ERASE UNIT PASSWORD N N P A A A P P A P P P A P P P P P
Passwords Defined Master Only Master Only Master and User Master and User Master and User Master and User
Password Supplied Correct Master Not Valid Correct Master Correct User Correct Master Correct User
N - NOP, do nothing and return normal completion A - Return command aborted P - Process the command (if all validations pass) or return command aborted 4.18.4 Frozen Mode The SECURITY FREEZE LOCK command prevents changes to all Security states until a following power-on reset or hardware reset. The purpose of the SECURITY FREEZE LOCK command is to prevent password setting attacks on the security system. 4.18.5 Commands A device that implements the Security feature set shall implement the following set of commands: a) b) c) d) e) f) SECURITY SET PASSWORD SECURITY UNLOCK (requires a password) SECURITY ERASE PREPARE SECURITY ERASE UNIT (requires a password) SECURITY FREEZE LOCK SECURITY DISABLE PASSWORD (requires a password)
4.18.6 IDENTIFY DEVICE data Support of the Security feature set is indicated in IDENTIFY DEVICE and IDENTIFY PACKET DEVICE data word 82 and data word 128. Security information in words 82, 89 and 90 is fixed until the next power-on reset and shall not change unless DEVICE CONFIGURATION OVERLAY removes support for the Security feature set. Security information in words 85, 92 and 128 are variable and may change. If the Security feature set is not supported, then words 89, 90, 92 and 128 are N/A.
34
T13/1699-D Revision 3f
When the device is shipped by the manufacturer, Security shall be disabled (e.g. is not Locked). The initial Master password value is not defined by this standard. 4.18.8 Password Rules This section applies to any Security command that accepts a password, and for which there exists a valid password. This section does not apply while Security is Frozen. The SECURITY ERASE UNIT command ignores the Master Password Capability value when comparing passwords, and shall accept either a valid Master or User password. If the User password sent to the device does not match the user password previously set with the SECURITY SET PASSWORD command, the device shall return command aborted. If the Master Password Capability was set to High during the last SECURITY SET (user) PASSWORD command, the device shall accept the Master password and complete normally. If the Master Password Capability was set to Maximum during the last SECURITY SET (user) PASSWORD command, the device shall return command aborted for SECURITY UNLOCK or SECURITY DISABLE PASSWORD if the Master password is supplied. . 4.18.9 Password Attempt Counter The device shall have an password attempt counter. The purpose of this counter is to defeat repeated trial attacks. The counter shall be decremented while in state SEC4, whenever the SECURITY UNLOCK command fails because of an invalid User or Master password. Once the counter reaches zero, it shall not be decremented, and the PasswordAttemptCounterExceeded bit (IDENTIFY DEVICE (data word 128, bit 4) shall be set to one, and the SECURITY UNLOCK and SECURITY ERASE UNIT commands shall be command aborted until after processing the next power-on or hardware reset. The PasswordAttemptCounterExceeded bit shall be cleared to zero by processing a power-on or a hardware reset. The counter shall be set to five (5) after a power-on or hardware reset. 4.18.10 Security states See figure 8 and table 7. When the power is off, the Security characteristics are as in table 7, but are not reportable. Table 7 Summary of Security States and Characteristics Security Characteristics Security State SEC0 SEC1 SEC2 SEC3 SEC4 SEC5 SEC6
a b
Enabled 0 0 0 1 1 1 1
IDENTIFY DEVICE data word 85 bit 1 IDENTIFY DEVICE data word 128 bit 2 c IDENITFY DEVICE data word 128 bit 3 d IDENTIFY DEVICE data word 128 bit 4
35
T13/1699-D Revision 3f
Editors Note 1: The proposal calls for an Unlocked/disabled column as previously documented, but asks for a normative statement regarding download microcode being diffferent. The original proposal does not list any differences for download mcrocode.
Table 8 Security Mode Command Actions (part 1 of 3) Command ADD LBA(S) TO NV CACHE PINNED SET CFA ERASE SECTORS CFA REQUEST EXTENDED ERROR CODE CFA TRANSLATE SECTOR CFA WRITE MULTIPLE WITHOUT ERASE CFA WRITE SECTORS WITHOUT ERASE CHECK MEDIA CARD TYPE CHECK POWER MODE CONFIGURE STREAM DEVICE CONFIGURATION DEVICE RESET DOWNLOAD MICROCODE EXECUTE DEVICE DIAGNOSTIC FLUSH CACHE FLUSH CACHE EXT FLUSH NV CACHE GET MEDIA STATUS IDENTIFY DEVICE IDENTIFY PACKET DEVICE IDLE IDLE IMMEDIATE MEDIA EJECT MEDIA LOCK MEDIA UNLOCK NOP PACKET QUERY NV CACHE MISSES QUERY NV CACHE PINNED SET READ BUFFER READ DMA READ DMA EXT
a b
Lockeda Command aborted Command aborted Executable Executable Command aborted Command aborted Command aborted Executable Command aborted Command aborted Executable Vendor Specific Executable Command aborted Command aborted Command aborted Command aborted Executable Executable Executable Executable Command aborted Command aborted Command aborted Executable Command aborted Command aborted Command aborted Executable Command aborted Command aborted
Unlocked or Disabledb Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Vendor Specific Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable
Frozenc Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Vendor Specific Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable
36
December 11, 2006 Table 8 Security Mode Command Actions (part 2 of 3) Command READ DMA QUEUED READ DMA QUEUED EXT READ LOG EXT READ MULTIPLE READ MULTIPLE EXT READ NATIVE MAX ADDRESS READ NATIVE MAX ADDRESS EXT READ SECTOR(S) READ SECTOR(S) EXT READ STREAM DMA EXT READ STREAM EXT READ VERIFY SECTOR(S) READ VERIFY SECTOR(S) EXT REMOVE LBA(S) FROM NV CACHE PINNED SET RETURN FROM NV CACHE POWER MODE SCT READ/WRITE LONG SCT WRITE SAME SCT ERROR RECOVERY CONTROL SCT FEATURE CONTROL SCT DATA TABLES SCT READ STATUS SECURITY DISABLE PASSWORD SECURITY ERASE PREPARE SECURITY ERASE UNIT SECURITY FREEZE LOCK SECURITY SET PASSWORD SECURITY UNLOCK SERVICE SET FEATURES SET MAX ADDRESS SET MAX ADDRESS EXT SET MAX SET PASSWORD SET MAX LOCK SET MAX FREEZE LOCK SET MAX UNLOCK SET MULTIPLE MODE SET NV CACHE POWER MODE SLEEP SMART DISABLE OPERATIONS State SEC4 States SEC1 or SEC5 c States SEC2 or SEC6
b a
T13/1699-D Revision 3f
Lockeda Command aborted Command aborted Executable Command aborted Command aborted Executable Executable Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Executable Command aborted Executable Executable Command aborted Command aborted Executable Command aborted Executable Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Executable Command aborted Executable Executable
Unlocked or Disabledb Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable
Frozenc Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Command aborted Command aborted Command aborted Executable Command aborted Command aborted Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable
37
T13/1699-D Revision 3f Table 8 Security Mode Command Actions (part 3 of 3) Command SMART ENABLE/DISABLE AUTOSAVE SMART ENABLE OPERATIONS SMART EXECUTE OFF-LINE IMMEDIATE SMART READ DATA SMART READ LOG SMART RETURN STATUS SMART WRITE LOG STANDBY STANDBY IMMEDIATE TRUSTED RECEIVE TRUSTED RECEIVE DMA TRUSTED SEND TRUSTED SEND DMA WRITE BUFFER WRITE DMA WRITE DMA EXT WRITE DMA FUA EXT WRITE DMA QUEUED WRITE DMA QUEUED EXT WRITE DMA QUEUED FUA EXT WRITE LOG DMA EXT WRITE LOG EXT WRITE MULTIPLE WRITE MULTIPLE EXT WRITE MULTIPLE FUA EXT WRITE SECTOR(S) WRITE SECTOR(S) EXT WRITE STREAM DMA EXT WRITE STREAM EXT State SEC4 States SEC1 or SEC5 c States SEC2 or SEC6
b a
Lockeda Executable Executable Executable Executable Executable Executable Executable Executable Executable Command aborted Command aborted Command aborted Command aborted Executable Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted Command aborted
Unlocked or Disabledb Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable
Frozenc Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable Executable
38
December 11, 2006 4.18.11 Security mode states Figure 8 describes security mode states and state transitions.
T13/1699-D Revision 3f
SEC2:SEC0
Hardware Reset
Power-up
SEC2:SEC1
SECURITY FREEZE LOCK command
Note: Some events may change Security characteristics without changing state in this diagram SEC3: Powered down/Enabled/ Locked/ Not Frozen
SEC5a:SEC1
SECURITY ERASE UNIT command
SEC5b:SEC1
SEC4: Enabled/ Locked/ Not Frozen SECURITY ERASE UNIT command SEC4:SEC1 Power-down SEC4:SEC3
SECURITY UNLOCK command
SEC4:SEC5
Hardware Reset
Power-up
SEC3:SEC4
SEC5:SEC4
SEC6:SEC4
Power-down
SEC5:SEC6 SEC6:SEC3
Power-down
SEC5:SEC3
Figure 8 Security mode state diagram Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) 39
T13/1699-D Revision 3f
State SEC0: Powered down/Security Disabled/Not Locked/ Not Frozen: This state shall be entered when the device is powered-down with the Security feature set disabled. Transition SEC0:SEC1: When the device is powered-up, the device shall make a transition to state SEC1. State SEC1: Security Disabled/Not Locked/ Not Frozen: This state shall be entered when the device is powered-up or a hardware reset is received with the Security feature set disabled or when the Security feature set is disabled by a SECURITY DISABLE PASSWORD or SECURITY ERASE UNIT command. When entering this state after processing a power-on or hardware reset, the device shall initialize the password attempt counter and clear the PasswordAttemptCounterExceeded flag In this state, the device shall respond to all commands as specified in the "Disabled" column of Table 4. With the exception of the SECURITY commands, execution of these commands shall not cause a transition from state SEC1. In this state, IDENTIFY DEVICE and IDENTIFY PACKET DEVICE shall report values as described in table 9. Table 9 IDENTIFY settings for Security state SEC1 Word 82 85 128 128 128 128 128 128 Bit Position 1 1 0 1 2 3 4 8 Value 1 0 copy of word 82 bit 1 copy of word 85 bit 1 0 0 Varies 0 Description Security feature set is supported There is no active User password Security feature set is supported Security feature set is disabled device is not locked device is not frozen Password Attempt Counter Exceeded 1= counter exceeded 0= counter not exceeded Master Password Capability is not maximum
Transition SEC1:SEC0: When the device is powered-down, the device shall make a transition to state SEC0. Transition SEC1:SEC1: When a SECURITY SET (master) PASSWORD command completes successfully, the Master password and the optional Master Password Identifier shall be saved, and the device shall remain in state SEC1. The Master Password Capability shall remain unchanged.Transition SEC1:SEC2: When a SECURITY FREEZE LOCK command completes successfully, the device shall make a transition to state SEC2. Transition SEC1:SEC5: When a SECURITY SET (user) PASSWORD command completes successfully, the device shall save the User password, update the Master Password Capability and make a transition to state SEC5. State SEC2: Security Disabled/ Not Locked/ Frozen: This state shall be entered when the device receives a SECURITY FREEZE LOCK command while in state SEC1. In this state, the device shall respond to all commands as specified in the "Frozen" column of table 8. Execution of any of these commands shall not cause a transition from state SEC2.
40
T13/1699-D Revision 3f
The device shall report IDENTIFY DEVICE or IDENTIFY PACKET DEVICE field values in accordance with table 10. Table 10 IDENTIFY settings for Security state SEC2 Word 82 85 128 128 128 128 128 Bit Position 1 1 0 1 2 3 4 Value 1 0 copy of word 82 bit 1 copy of word 85 bit 1 0 1 Varies Description Security feature set is supported There is no active User password Security feature set is supported Security feature set is disabled device is not locked device is frozen Password Attempt Counter Exceeded 1= counter exceeded 0= counter not exceeded Master Password Capability 0=high/User password disabled 1=Maximum/User password disabled
128
Varies
Transition SEC2:SEC0: When the device is powered-down, the device shall make a transition to state SEC0. Transition SEC2:SEC1: When the device receives a hardware reset, the device shall make a transition to state SEC1. State SEC3: Powered down/Security Enabled/ Locked/ Not Frozen: This state shall be entered when the device is powered-down with the Security feature set enabled. Transition SEC3:SEC4: When the device is powered-up, the device shall make a transition to state SEC4. State SEC4: Security Enabled/ Locked/ Not Frozen: This state shall be entered when the device is powered-up or a hardware reset is received with the Security feature set enabled. In this state, the device shall respond to all commands as specified in the "Locked" column of table 8. With the exception of the SECURITY commands, execution of these commands shall not cause a transition from state SEC4. When entering this state from power-on or hardware reset, the device shall initialize the password attempt counter and clear the PasswordAttemptCounterExceeded flag
41
T13/1699-D Revision 3f
The device shall report IDENTIFY DEVICE or IDENTIFY PACKET DEVICE field values in accordance with table 11. Table 11 IDENTIFY settings for Security state SEC4 Word 82 85 128 128 128 128 128 Bit Position 1 1 0 1 2 3 4 Value 1 1 copy of word 82 bit 1 copy of word 85 bit 1 1 0 Varies Description Security feature set is supported There is an active User password Security feature set is supported Security feature set is enabled device is locked device is not frozen Password Attempt Counter Exceeded 1= counter exceeded 0= counter not exceeded Master Password Capability 0=high 1=Maximum
128
Varies
Transition SEC4:SEC1: When a SECURITY ERASE UNIT command completed successfully, the device shall make a transition to state SEC1. Transition SEC4:SEC3: When the device is powered-down, the device shall make a transition to state SEC3. Transition SEC4:SEC4: When a SECURITY UNLOCK command is received with an incorrect password, the password attempt counter shall be decremented by 1, and remain in state SEC4. If password attempt counter reaches 0, the PasswordAttemptCounterExceeded bit (IDENTIFY DEVICE word 128, bit 4) shall be set to 1. After execution of the SECURITY ERASE PREPARE command, the device remains in state SEC4. Transition SEC4:SEC5: When a SECURITY UNLOCK command is successful, the device shall make a transition to state SEC5. State SEC5: Security Enabled/ Not Locked/ Not Frozen: This state shall be entered when either a SECURITY SET (user) PASSWORD command or a SECURITY UNLOCK command is successful. In this state, the device shall respond to all commands as specified in the "Unlocked" column of table 8. With the exception of the SECURITY commands, execution of these commands shall not cause a transition from state SEC5.
42
T13/1699-D Revision 3f
The device shall report IDENTIFY DEVICE or IDENTIFY PACKET DEVICE field values in accordance with table 12. Table 12 IDENTIFY settings for Security state SEC5 Word 82 85 128 128 128 128 128 Bit Position 1 1 0 1 2 3 4 Value 1 1 copy of word 82 bit 1 copy of word 85 bit 1 0 0 Varies Description Security feature set is supported There is an active User password Security feature set is supported Security feature set is enabled device is not locked device is not frozen Password Attempt Counter Exceeded 1= counter exceeded 0= counter not exceeded Master Password Capability 0=high 1=Maximum
128
Varies
Transition SEC5:SEC1: When a SECURITY DISABLE PASSWORD or a SECURITY ERASE UNIT command is successful, the device shall make a transition to the SEC1 state. Transition SEC5:SEC3: When the device is powered-down, the device shall make a transition to state SEC3. Transition SEC5:SEC4: When the device receives a hardware reset, the device shall make a transition to state SEC4. Transition SEC5:SEC5: When a successful SECURITY SET (master) PASSWORD command is received, the Master password and the optional Master Password Identifier shall be saved, the Master Password Capability shall remain unchanged, and the device shall remain in state SEC5. When a SECURITY SET (user) PASSWORD command is successful, the device shall save the User password, update the Master Password Capability and shall remain in state SEC5. After execution of the SECURITY ERASE PREPARE command, the device remains in state SEC4. Transition SEC5:SEC6: When a SECURITY FREEZE LOCK command is successful , the device shall make a transition to state SEC6. State SEC6: Security Enabled/ Not Locked/ Frozen: This state shall be entered when the device receives a SECURITY FREEZE LOCK command while SEC5 state. In this state, the device shall respond to all commands as specified in the "Frozen" column of Table 4. With the exception of the SECURITY commands, execution of these commands shall not cause a transition from state SEC6.
43
T13/1699-D Revision 3f
The device shall report IDENTIFY DEVICE or IDENTIFY PACKET DEVICE field values in accordance with table 12. Table 13 IDENTIFY settings for Security state SEC6 Word 82 85 128 128 128 128 128 Bit Position 1 1 0 1 2 3 4 Value 1 1 copy of word 82 bit 1 copy of word 85 bit 1 0 1 Varies Description Security feature set is supported There is an active User password Security feature set is supported Security feature set is enabled device is not locked device is frozen Password Attempt Counter Exceeded 1= counter exceeded 0= counter not exceeded Master Password Capability 0=high 1=Maximum
128
Varies
Transition SEC6:SEC4: When the device receives a hardware reset, the device shall make a transition to state SEC4. Transition SEC6:SEC3: When the device is powered-down, the device shall make a transition to state SEC3. 4.18.12 Master Password Identifier feature This is an optional enhancement to the Security feature set, which is a prerequisite. 4.18.12.1 Use Case (Informative) The intended purpose of this feature is to assist an administrator that uses several sets of Master passwords (for use in different deployments of devices). The administrator may maintain a mapping of actual Master passwords and a corresponding Identifier. When an administrator sets a Master password, the corresponding Master Password Identifier could be also set. When the time comes to redeploy a device for which a User password had been set (and subsequently lost), the administrator needs to know which Master password is actually valid for this individual device. Since the device never reveals the Master password but does reveal the Identifier, the administrator may obtain a hint as to which Master password was previously set. 4.18.12.2 Requirements The device shall maintain a 2-byte host vendor-specific data value associated with the Master Password. The Master Password Identifier does not indicate whether a Master Password exists or is valid. Support for this feature is reported in the IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data in word 92. Valid identifiers are 0001h through FFFEh. A value of 0000h or FFFFh indicates that the this feature is not supported. If the device supports this feature, a) The device shall store a non-volatile identifier field with the stored Master password. The identifier is maintained for the benefit of the host. The value is not modified by the device. b) Prior to first use, the initial Master Password Identifier shall be set to FFFEh by the manufacturer.
T13/1699-D Revision 3f
and/or fault of the device. By monitoring and storing critical performance and calibration parameters, SMART feature set devices attempt to predict the likelihood of near-term degradation or fault condition. Providing the host system the knowledge of a negative reliability condition allows the host system to warn the user of the impending risk of a data loss and advise the user of appropriate action. Support of this feature set is indicated in the IDENTIFY DEVICE data. Devices that implement the PACKET feature set shall not implement the SMART feature set. 4.19.1 Device SMART data structure SMART feature set capability and status information for the device are stored in the device SMART data structure. The off-line data collection capability and status data stored herein may be useful to the host if the SMART EXECUTE OFF-LINE IMMEDIATE command is implemented (see 7.52.5). 4.19.2 Background data collection Collection of SMART data in the background shall have no impact on device performance. The SMART data that is collected or the methods by which data is collected in this mode may be different than those in the off-line data collection mode for any particular device and may vary from one device to another. 4.19.3 Off-line/Captive mode data collection The device shall use the off-line or captive mode for data collection and self-test routines that have an impact on performance if the device is required to respond to commands from the host while performing that data collection. This impact on performance may vary from device to device. The data that is collected or the methods by which the data is collected in this mode may be different than those in the background data collection mode for any particular device and may vary from one device to another. 4.19.4 Threshold exceeded condition This condition occurs when the devices SMART reliability status indicates an impending degrading or fault condition. 4.19.5 SMART feature set commands These commands use a single command code and are differentiated from one another by the value placed in the Feature field (see 7.52). If the SMART feature set is implemented, the following commands shall be implemented. a) b) c) d) a) b) c) d) SMART DISABLE OPERATIONS SMART ENABLE/DISABLE AUTOSAVE SMART ENABLE OPERATIONS SMART RETURN STATUS SMART EXECUTE OFF-LINE IMMEDIATE SMART READ DATA SMART READ LOG SMART WRITE LOG
If the SMART feature set is implemented, the following commands may be implemented.
4.19.6 SMART operation with power management modes When used with a host that has implemented the Power Management feature set, a SMART enabled device should automatically save the device accumulated SMART data upon receipt of an IDLE IMMEDIATE, STANDBY IMMEDIATE, or SLEEP command or upon return to an Active or Idle mode from a Standby mode (see 7.52.6). If a SMART feature set enabled device has been set to use the Standby timer, the device should automatically save the device accumulated SMART data prior to going from an Idle mode to the Standby mode or upon return to an Active or Idle mode from a Standby mode. A device shall not execute any routine to automatically save the device accumulated SMART data while the device is in a Standby or Sleep mode.
45
Logging of reported errors is an optional SMART feature. If error logging is supported by a device, it is indicated in byte 370 of the SMART READ DATA command response and IDENTIFY DEVICE DATA word 84 bit 0. If error logging is supported, the device shall provide information on the last five errors that the device reported as described in the SMART READ LOG command (see 7.52.7). The device may also provide additional vendor specific information on these reported errors. If error logging is supported, it shall not be disabled when SMART is disabled. Error log information shall be gathered when the device is powered-on except that logging of errors when in a reduced power mode is optional. If errors are logged when in a reduced power mode, the reduced power mode shall not change. Disabling SMART shall disable the delivering of error log information via the SMART READ LOG command.
Support of the Streaming feature set is indicated in IDENTIFY DEVICE data word 84 bit 4. 4.20.2 Streaming commands 4.20.2.1 Streaming command overview The CONFIGURE STREAM command is used by a host to define the properties of a stream to assist the device in configuring its caching for best performance. The Stream Identifier (Stream ID) in the CONFIGURE STREAM command is used by the host to specify the number of the stream to which the operating parameters in the command apply. Up to a total of eight streams may be configured. The Stream ID may be used by the device to configure its resources to support the streaming requirements of the AV content. A host may use both READ STREAM and WRITE STREAM commands to access any stream. The Default Command Completion Time Limit (Default CCTL) provides a method for a host to set the time limit for a device to process READ STREAM and WRITE STREAM commands (see 7.9.3.4). If the host does not use a CONFIGURE STREAM command to set Default CCTL, the host may specify the time limit for command processing by using the Command Completion Time Limit (CCTL) in each READ STREAM or WRITE STREAM command, where the time limit is effective for that command only (see 7.36.3.2). Each stream may be configured for with different command completion time limits by each CONFIGURE STREAM command. The READ STREAM and WRITE STREAM commands may access any user LBA on a device. These commands may be interspersed with commands not in the Streaming feature set, but, if commands not in the Streaming feature set are interspersed with READ STREAM or WRITE STREAM commands, there may be an impact on performance due to the unknown time required to complete the commands not in the Streaming feature set. 46 Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS)
T13/1699-D Revision 3f
READ STREAM or WRITE STREAM commands should be issued using a specified minimum number of logical sectors to be transferred per command. This number is the Stream Minimum Request Size indicated in IDENTIFY DEVICE data word 95. The transfer length of a request should be a multiple of the minimum number of logical sectors per transfer. 4.20.2.2 Flush bit The Flush bit (Flush) in the WRITE STREAM commands (see 7.73.3.3) specifies that the device flushes all data for the specified stream to the media before command completion. If a host requests flushes at times other than the end of each Allocation Unit ((see 7.9.3.5), streaming performance may be degraded. The SET FEATURES command to enable and disable caching (see 7.47.4) may affect caching for commands in the Streaming feature set. 4.20.2.3 Not Sequential bit The Not Sequential bit (NS) in the READ STREAM commands (see 7.36.3.4) specifies that the next READ STREAM command with the same Stream ID may not be sequential in LBA space. This information helps the device with pre-fetching decisions. 4.20.2.4 Read Continuous bit The Read Continuous bit (RC) in the READ STREAM commands (see 7.36.3.3) specifies that the device shall transfer the requested amount of data to the host within the time specified by Default CCTL or CCTL even if an error occurs. The data sent to the host by the device in an error condition is vendor specific. 4.20.2.5 Write Continuous bit The Write Continuous bit (WC) in the WRITE STREAM commands (see 7.73.3.2) specifies that the device shall transfer the requested amount of data to the host within the time specified by Default CCTL or CCTL even if an error occurs. If an error cannot be resolved by the device within the time specified by Default CCTL or CCTL, the erroneous section on the media may be unchanged or may contain undefined data. A future read of this area may not report as an error, even though the data is erroneous. 4.20.2.6 Handle Streaming Error The Handle Streaming Error feature allows a device to continue its error recovery sequence for a stream from where it left off earlier. The Handle Streaming Error feature is vendor-specific and may be always enabled in devices conforming to this standard. 4.20.2.7 Streaming Logs A device implementing the Streaming feature set shall implement a Read Stream Error Log (see A.5) and a Write Stream Error Log (see A.6). These logs are accessed by a host via the READ LOG EXT command (see 7.28). The Read Stream and Write Stream Error logs are 512 bytes in length. The Read Stream Error log retains the last 31 errors that occurred during any READ STREAM command. The Write Stream Error log retains the last 31 errors that occurred during any WRITE STREAM command. The information included in the error logs is volatile and is not maintained by a device after the device processes a power-on reset or a hard reset, or after the device enters the Sleep mode.
47
T13/1699-D Revision 3f When the TCQ feature set is supported, the following commands are optional: a) READ DMA QUEUED EXT b) WRITE DMA QUEUED EXT c) WRITE DMA QUEUED FUA EXT
For the READ DMA QUEUED and WRITE DMA QUEUED commands, the device may or may not perform a release. If the device is ready to complete execution of the command, the device may complete the command immediately. If the device is not ready to complete execution of the command, the device may perform a release and complete the command via a service request. If a device has an outstanding command that has been released, the device only indicates that service is required when the device is selected. This implies that the host has to poll each device to determine if a device is requesting service. The polling is performed at the host either by hardware or by a software routine. The latter implies a considerable host processor overhead. Hardware polling is initiated by the NOP Auto Poll command. The NOP Poll command is a host adapter function and is ignored by the device. The host software may test for the support of this feature by issuing the NOP Auto Poll subcommand and check for command aborted. If the host adapter does not support this feature, the NOP poll command shall be transmitted to the device and the device shall abort the command with the ERR bit set to one. If the host adapter does support the command, the response shall be from the host adapter with the ERR bit cleared to zero. The only action taken by a device supporting the TCQ feature set shall be to return the error indication in the Status field and to not abort any outstanding commands. When this command is received, the user data shall be written to the device media before ending status for the command is reported regardless of the state of any write cache or queue. A queue shall not be aborted. 4.21.2 Queueing The queueing allows the host to issue concurrent commands to the same device. The queue contains all commands for which command acceptance has occurred but command completion has not occurred. If a queue exists when a non-queued command is received, the non-queued command shall be command aborted and the commands in the queue shall be discarded. The ending status shall be command aborted and the results are indeterminate. The maximum queue depth supported by a device shall be indicated in IDENTIFY DEVICE data word 75 or IDENTIFY PACKET DEVICE data word 75. A queued command shall have a Tag provided by the host in the Count field to uniquely identify the command. When the device restores command parameters during the execution of the SERVICE command, this Tag shall be restored so that the host may identify the command for which status is being presented. A Tag value may be any value between 0 and 31, regardless of the queue depth supported. If a queued command is issued with a Tag value that is identical to the Tag value for a command already in the queue, the entire queue shall be aborted including the new command. The ending status shall be command aborted and the results are indeterminate. If any error occurs, the command queue shall be aborted. When the device is ready to continue the processing of a released command, the device requests service by setting SERV to one. SERV shall remain set until all commands ready for service have been serviced. When the device is ready to continue the processing of a released command the device requests service by setting SERV to one. SERV shall remain set until all commands ready for service have been serviced. When the device receives a new command while queued commands are ready for service, the device shall execute the new command per the protocol for the new command. If the queued commands ready for service still exist at command completion of this command, SERV remains set to one. When reading status at command completion of a command, the host should check the SERV bit since the SERV bit may be set because the device is ready for service associated with another command.
T13/1699-D Revision 3f
This feature set defines two data-in commands (TRUSTED RECEIVE and TRUSTED RECEIVE DMA) and two data-out commands (TRUSTED SEND and TRUSTED SEND DMA). These commands provide for variable length data transfers. TRUSTED SEND and TRUSTED SEND DMA may be used interchangeably. They only differ by the type of data transport protocol used (PIO vs. DMA). Similarly, TRUSTED RECEIVE and TRUSTED RECEIVE DMA are interchangeable. The IDENTIFY DEVICE command indicates whether or not this feature set is supported. The DEVICE CONFIGURATION OVERLAY (SET) command offers a mechanism to remove support for the feature set. The data streams and subsequent actions resulting from these commands are defined by the security protocol identified in the command parameters. These protocols may be defined by groups outside of T10 and T13. The intent is to standardize the data content so it is identical across both ATA and SCSI interfaces.
See 7.47.10 for a description of device behavior when this feature set is supported and enabled. The IDENTIFY DEVICE or IDENTIFY PACKET DEVICE command shall reflect the enabled or disabled state of the feature set. If the Write Cache is enabled, the device may report status to the Host before writing the data to the media. When the device Write Cache is enabled, the device may report good status to the host even if the data is in the device Write Cache and not Written and Verified to the media. This is important to reduce the performance degradation when we use the Write-Read-Verify function. Read Verify behavior is unaffected by whether Write Caching is enabled or disabled. If the WriteReadVerify feature is disabled, or if the device has already verified the maximum number of logical sectors configured for this feature set, then no further action shall be taken. After the device has written the sectors to the media, it shall attempt to read (Verify) those same sectors. A read from the media shall be performed before verification. The verification of sectors is defined as vendor specific. If an unrecoverable error condition is encountered by the device during the write, read, or verify operation, the device shall set the DF bit. See 6.1.3 for details on the DF bit operation.
49
T13/1699-D Revision 3f
50
T13/1699-D Revision 3f
5 ATA Protocols
ATA Protocols are fully described in the transport documents. The protocols listed here shall be implemented by all transports that use ATA8-ACS commands. The following list of protocols are described in ATA8-AAM and the implementation is described in the applicable transport standard. a) b) c) d) e) f) g) h) Non-data Command Protocol PIO data-in Command Protocol PIO data-out Command Protocol DMA Command Protocol Packet Command Protocol DMA Queued Command Protocol Execute Device Diagnostic Command Protocol Device Reset Command Protocol
51
T13/1699-D Revision 3f
52
T13/1699-D Revision 3f
53
Error bit 0. CCTO shall be set to one if a Command Completion Time Limit Out error has occurred. 6.2.3 End of Media (EOM) Error bit 1. The operation of this bit is specific to the SCSI command set implemented by ATAPI devices. 6.2.4 ID Not Found (IDNF) Error bit 4. ID Not Found shall be set to one if a user-accessible address could not be found. ID Not Found shall be set to one if an address outside of the range of user-accessible addresses is requested when command aborted is not returned. 6.2.5 Illegal Length Indicator (ILI) Error bit 0. The operation of this bit is specific to the SCSI command set implemented by ATAPI devices. 6.2.6 Interface CRC (ICRC) Error bit 7. Interface CRC shall be set to one if an interface CRC error has occurred during an Ultra DMA data transfer. The content of this bit may be applicable to Multiword DMA and PIO data transfers. 6.2.7 Media Error (MED) Error bit 0. Media Error shall be set to one if a media error is detected. 6.2.8 Sense Key Error bits (7:4) The operation of this four bit field is specific to the SCSI command set implemented by ATAPI devices. 6.2.9 Uncorrectable Error (UNC) Error bit 6. Uncorrectable Error shall be set to one if data is uncorrectable. 6.2.10 Write Protect (WP) Error bit 6. Write Protect shall be set to one for each execution of GET MEDIA STATUS while the media is write protected. 6.2.11 Attempted partial range removal Error bit 0. The command attempted to unpin part of a previously defined command range. 6.2.12 Insufficient NV Cache space Error bit 0. There is not enough NV Cache to satisfy the NV Cache command 6.2.13 Insufficient LBA Range Entries remaining Error bit 1. The device has run out of space to store LBA ranges for NV Cache commands.
54
T13/1699-D Revision 3f
Count bits (7:3). If the device supports TCQ, this field contains the Tag value for the command. A Tag value may be any value between 0 and 31 regardless of the queue depth supported.
55
T13/1699-D Revision 3f
56
T13/1699-D Revision 3f
57
T13/1699-D Revision 3f
Word 00h
Name Feature
01h
Count
LBA
Device
Command
Description In ATA/ATAPI-7 this was the Feature register. Each transport standard shows how the Feature field is mapped for proper functionality. The transport documents also show how 28-bit commands are mapped differently from 48-bit commands. In ATA/ATAPI-7 this was the Sector Count register. Each transport standard shows how the Count field is mapped for proper functionality. The transport documents also show how 28-bit commands are mapped differently from 48-bit commands. (MSB) In ATA/ATAPI-7 this was the LBA Low, LBA Mid, LBA High, and Device (3:0) Registers. For many commands this is the address of first logical sector to be transferred. Bits 47:28 shall be cleared (LSB) to zero for 28 bit commands. Each transport defines how these 48-bits are mapped to the appropriate fields or registers. In ATA/ATAPI-7 this was the Device register. This standard includes bits 3:0 of the ATA/ATAPI-7 Device register as a part of the LBA field. Each transport standard shows how the Device field bits 7:4 are mapped for proper functionality Bit 7:0 - The command number goes here.
The Feature, Count, and Command fields are 16 bit fields where bits 15:8 shall be cleared to zero. The LBA field is 48 bits where bits 47:28 shall be cleared to zero. The command field shall always be represented as an 8-bit value. 7.1.5.2 Inputs for 48-bit Read/Write Commands All commands require inputs. Inputs are specified in the Command Structure. A generic command structure for 48-bit commands is listed below. The description field shows how the fields mapped to ATA/ATAPI-7 registers. Word 00h 01h 02h 03h 04h 05h Name Feature Count LBA Description In ATA/ATAPI-7 this was the Feature Current and Previous registers. Each transport standard shows how the Feature field is mapped for proper functionality. In ATA/ATAPI-7 this was the Count Current and Previous registers. Each transport standard shows how the Count field is mapped for proper functionality. (MSB) In ATA/ATAPI-7, this are the LBA Low, LBA Mid, LBA High both Current and Previous registers. For many commands this is the address of first logical sector to be transferred. Each transport (LSB) defines how these 48-bits are mapped to the appropriate fields or registers. In ATA/ATAPI-7 this was the Device register. Each transport standard shows how the Device field is mapped for proper functionality. The command number goes here.
Device Command
The Feature, and Count, fields shall be 16 bit values; the LBA field shall be a 48-bit value. The command field shall always be represented as an 8-bit value. 7.1.6 Normal Outputs Many of the commands have a Normal Outputs description that looks exactly like the one shown below. A command with Normal Outputs has no error, this field is reserved in every command. Count and LBA may be reserved. In some commands these fields have return parameters on successful command completion. The status field shows the Device Fault bit and the Error bit. Bits 7,6, and 3 are marked Transport Dependent in
58
T13/1699-D Revision 3f
many of the Normal Outputs. These bits correspond to Busy, Device Ready, and Device Request in ATA/ATAPI-7 and are transport specific in their operation. Word 00h 01h 02h-04h 05h Name Error Count LBA Status Description Reserved Reserved Reserved Bit 15:8 7:6 5 4 3 2 1 0 7.1.7 Error Outputs The Error Outputs subclause shows the Error, Count, LBA and Status fields. An Error Output occurs when a bit in the Status field indicates that an error has occurred. Examples of status bits that indicate and error has occurred include Error, Device Fault, Stream Error, etc. If the Error bit is set to one, the Error field shall indicate the type of Error that occurred. Word 00h Name Error Bit 15:8 7 6 5 4 3 2 1 0 01h 02h 03h 04h 05h Count LBA Description Description Reserved Interface CRC - See 6.2.6 Uncorrectable Error - See 6.2.9 Obsolete ID Not Found - See 6.2.4 Obsolete Abort - See 6.2.1 Obsolete Obsolete Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A N/A Error - See 6.1.2
Reserved (MSB) Address of first unrecoverable error. Bits 47:28 shall be cleared to zero. (LSB)
Status Bit 15:8 7:6 5 4 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A
59
T13/1699-D Revision 3f Word Name 3 2:1 0 7.1.8 Input Data Structure Description Transport Dependent - See 6.1.9. N/A Error - See 6.1.2
Some commands, such as IDENTIFY DEVICE or DEVICE CONFIGURATION SET, return a data structure to the host. This data structure is referred to as an input data structure and is documented following the Error Outputs subclause. 7.1.9 Output Data Structure Some commands, such as DEVICE CONFIGURATION SET or SECURITY SET PASSWORD, accept a data structure from the host. This data structure is referred to as an Output Data Structure and is documented following the Error Outputs subclause.
60
T13/1699-D Revision 3f
Device
61
T13/1699-D Revision 3f
7:0 03h
December 11, 2006 Table 14 Extended error codes Extended error code 30-34h 35h, 36h 37h, 3Eh 38h 39h 3Ah 3Bh 3Ch, 3Fh 3Dh All other values 7.3.5 Error Outputs See table 99. Description (Continued) Self-test or diagnostic failed Supply or generated voltage out of tolerance Self-test or diagnostic failed Corrupted media format Vendor specific Spare sectors exhausted Corrupted media format Vendor specific Reserved
T13/1699-D Revision 3f
63
T13/1699-D Revision 3f
Logical sector Address. Bits 47:28 shall be cleared to zero. Description Obsolete Shall be set to one Obsolete Transport Dependent - See 6.1.9 Reserved
(LSB)
7.4.4 Normal Outputs See table 80 for the data structure layout. 7.4.5 Output Data Structure 512 bytes of data are transferred to the host (see table 15). Table 15 CFA TRANSLATE SECTOR data Bytes 00h-03h 04h 05h 06h 07h-12h 13h 14h-17h 18h 19h 1Ah 1Bh-1FFh Description Obsolete LBA bits (23:16) LBA bits (15:8) LBA bits (7:0) Reserved Logical sector erased flag (FFh = erased; 00h = not erased) Reserved Logical sector write cycles count bits (23:16) Logical sector write cycles count bits (15:8) Logical sector write cycles count bits (7:0) Reserved
64
T13/1699-D Revision 3f
Device
7:0 CDh
65
T13/1699-D Revision 3f
Device
7:0 38h
66
T13/1699-D Revision 3f
7:0 D1h
67
T13/1699-D Revision 3f
7:0 E5h
68
T13/1699-D Revision 3f
Allocation Unit See 7.9.3.5 Reserved Bit 15 14 13 12 11:8 Description Obsolete Shall be set to one Obsolete Transport Dependent - See 6.1.9 Reserved
Command
7:0 51h
7.9.3.2 Add/Remove Stream (A/R) If A/R is set to one, then the device shall set the operating parameters for the stream as specified by this command. If A/R is cleared to zero, then the device shall clear the operating characteristics for the Stream ID specified by this command. If A/R is cleared to zero, then the other bits in Features are N/A. If A/R is set to one, the Stream ID was specified by a previous CONFIGURE STREAM command, and the current CONFIGURE STREAM command completes without error, then the operating parameters specified by the current CONFIGURE STREAM command shall replace the operating parameters specified by the previous CONFIGURE STREAM command for the stream. 7.9.3.3 Stream Identifier (Stream ID) Stream ID specifies the stream to which the operating parameters in the command apply. There are eight possible streams total. A host may use both READ STREAM and WRITE STREAM commands to access any stream. 7.9.3.4 Default Command Completion Time Limit (Default CCTL) If CCTL is cleared to zero for a READ STREAM or WRITE STREAM command (see 7.36.3.2) with the Stream ID specified in this command, then the device shall report command completion within (Default CCTL * (IDENTIFY DEVICE data words (99:98)) microseconds Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) 69
T13/1699-D Revision 3f
The device shall measure the time before reporting command completion from command acceptance. 7.9.3.5 Allocation Unit The Allocation Unit Size specifies the number of logical blocks a device should use for read ahead and write cache operations for the stream being configured. NOTE 1 Setting the AU Size does not restrict or change command behavior. 7.9.4 Normal Outputs See table 83. 7.9.5 Error Outputs ABRT shall be set to one if any of the following are true: a) The device does not support the requested stream configuration; b) A/R is cleared to zero and the Feature field contains a Stream ID that has not been sent in a previous CONFIGURE STREAM command; c) The device does not support the requested Default CCTL; or d) The device does not support the Streaming feature set. See table 102 for the definition of other Error Outputs.
70
T13/1699-D Revision 3f
71
T13/1699-D Revision 3f 7.10.2 DEVICE CONFIGURATION FREEZE LOCK - B1h/C1h, Non-data 7.10.2.1 Feature Set
This command is mandatory for devices implementing the Device Configuration Overlay feature set. 7.10.2.2 Description The DEVICE CONFIGURATION FREEZE LOCK command prevents accidental modification of the Device Configuration Overlay settings. After successful execution of a DEVICE CONFIGURATION FREEZE LOCK command, all DEVICE CONFIGURATION SET, DEVICE CONFIGURATION FREEZE LOCK, DEVICE CONFIGURATION IDENTIFY, and DEVICE CONFIGURATION RESTORE commands shall be aborted by the device. A device shall be in the DCO factory_config state (see 4.14) after processing a power-on reset. A device shall not change Device Configuration Overlay states as the result of processing a hardware reset or a software reset. 7.10.2.3 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description C1h N/A N/A Bit 15:13 12 11:8 05h Command Description N/A Transport Dependent - See 6.1.9 Reserved
7:0 B1h
7.10.2.4 Normal Outputs See table 79. 7.10.2.5 Error Outputs Abort shall be set to one if the device has completed a previous DEVICE CONFIGURATION FREEZE LOCK command without error since processing the most recent power-on reset. See table 100.
72
December 11, 2006 7.10.3 DEVICE CONFIGURATION IDENTIFY - B1h/C2h, PIO Data-in 7.10.3.1 Feature Set
T13/1699-D Revision 3f
This command is mandatory for devices implementing the Device Configuration Overlay feature set. 7.10.3.2 Description The DEVICE CONFIGURATION IDENTIFY command returns a 512 byte data structure. The content of this data structure indicates the selectable commands, modes, and feature sets that the device is capable of supporting. If a DEVICE CONFIGURATION SET command has been issued reducing the capabilities, the response to an IDENTIFY DEVICE, IDENTIFY PACKET DEVICE, and other commands shall reflect the reduced set of capabilities, while the DEVICE CONFIGURATION IDENTIFY command shall reflect the entire set of selectable capabilities. The term is allowed indicates that the device may report that a feature is supported. If the device is not allowed to report support, then the device shall not support and shall report that the selected feature is both not supported and if appropriate not enabled. The format of the Device Configuration Overlay data structure is shown in table 17. 7.10.3.3 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description C2h N/A N/A Bit 15:13 12 11:8 05h Command Description N/A Transport Dependent - See 6.1.9 Reserved
7:0 B1h
7.10.3.4 Normal Outputs See table 79. 7.10.3.5 Error Outputs Abort shall be set to one if the device has completed a previous DEVICE CONFIGURATION FREEZE LOCK command without error since processing the most recent power-on reset. The device may return error status if an Interface CRC error has occurred. See table 100.
865H
NOTE 2 There is no defined mechanism for a device to return an ICRC error status that may have occurred during the last data block of a PIO-in data transfer, there may be other mechanisms in which a host may verify that an Interface CRC error occurred in these cases.
73
Table 17 Device Configuration Identify data structure (part 1 of 2) Word 0 1 Content Data structure revision Multiword DMA modes supported 15:3 Reserved 2 1 = Reporting support for Multiword DMA mode 2 and below is allowed 1 1 = Reporting support for Multiword DMA mode 1 and below is allowed 0 1 = Reporting support for Multiword DMA mode 0 is allowed Ultra DMA modes supported 15:7 Reserved 6 1 = Reporting support for Ultra DMA mode 6 and below is allowed 5 1 = Reporting support for Ultra DMA mode 5 and below is allowed 4 1 = Reporting support for Ultra DMA mode 4 and below is allowed 3 1 = Reporting support for Ultra DMA mode 3 and below is allowed 2 1 = Reporting support for Ultra DMA mode 2 and below is allowed 1 1 = Reporting support for Ultra DMA mode 1 and below is allowed 0 1 = Reporting support for Ultra DMA mode 0 is allowed Maximum LBA Command set/feature set supported part 1 15 Reserved 14 1 = Reporting support for Write-Read-Verify feature set is allowed 13 1 = Reporting support for SMART Conveyance self-test is allowed 12 1 = Reporting support for SMART Selective self-test is allowed 11 1 = Reporting support for Forced Unit Access is allowed 10 Reserved for ANSI/INCITS TR-37-2004 9 1 = Reporting support for Streaming feature set is allowed 8 1 = Reporting support for 48-bit Addressing feature set is allowed 7 1 = Reporting support for Host Protected Area feature set is allowed 6 1 = Reporting support for Automatic acoustic management is allowed 5 1 = Reporting support for READ/WRITE DMA QUEUED commands is allowed 4 1 = Reporting support for Power-up in Standby feature set is allowed 3 1 = Reporting support for Security feature set is allowed 2 1 = Reporting support for SMART error log is allowed 1 1 = Reporting support for SMART self-test is allowed 0 1 = Reporting support for SMART feature set is allowed Reserved for serial ATA Reserved Command set/feature set supported part 2 15 1 = Reporting Support for NV Cache feature set is allowed 14 1 = Reporting Support for NV Cache Power Management feature set is allowed 13 1= Reporting support for WRITE UNCORRECTABLE is allowed 12 1= reporting of support for the Trusted Computing feature set is allowed 11 Reserved for e06144 10:0 Reserved Command set/feature set supported part 3
3-6 7
8-9 10-20 21
22
74
T13/1699-D Revision 3f
Table 17 Device Configuration Identify data structure (part 2 of 2) Word 23-207 208-254 255 15:0 Reserved Reserved Vendor Specific Integrity word 15:8 Checksum 7:0 Signature Content
7.10.3.6.1 Word 0: Data structure revision Word 0 shall contain the value 0002h. 7.10.3.6.2 Word 1: Multiword DMA modes supported Word 1 bits (2:0) contain the same information as contained in IDENTIFY DEVICE data word 63 or IDENTIFY PACKET DEVICE data word 63 (see 7.16.7.23). Bits (15:3) of word 1 are reserved. 7.10.3.6.3 Word 2: Ultra DMA modes supported Word 2 bits (6:0) contain the same information as contained in IDENTIFY DEVICE data word 88 or IDENTIFY PACKET DEVICE data word 88 (see 7.16.7.36). Bits (15:7) of word 2 are reserved. 7.10.3.6.4 Words (6:3): Maximum LBA Words (6:3) define the maximum LBA. This is the highest address accepted by the device in the factory default condition. If no DEVICE CONFIGURATION SET command has been executed modifying the factory default condition, this is the same value as that returned by a READ NATIVE MAX ADDRESS or READ NATIVE MAX ADDRESS EXT command. 7.10.3.6.5 Word 7: Command/features set supported part 1 Word 7 bit 0 if set to one indicates that the device is allowed to report support for the SMART feature set. Word 7 bit 1 if set to one indicates that the device allowed to report support for SMART self-test including the self-test log. Word 7 bit 2 if set to one indicates that the device is allowed to report support for SMART error logging. Word 7 bit 3 if set to one indicates that the device is allowed to report support for the Security feature set. Word 7 bit 4 if set to one indicates that the device is allowed to report support for the Power-up in Standby feature set. Word 7 bit 5 if set to one indicates that the device is allowed to report support for the READ DMA QUEUED and WRITE DMA QUEUED commands. Word 7 bit 6 if set to one indicates that the device is allowed to report support for the Automatic Acoustic Management feature set. Word 7 bit 7 if set to one indicates that the device is allowed to report support for the Host Protected Area feature set. Word 7 bit 8 if set to one indicates that the device is allowed to report support for the 48-bit Addressing feature set. Word 7 bit 9 if set to one indicates that the device is allowed to report support for Streaming feature set. Word 7 bit 10 is reserved for technical report ANSI/INCITS TR-37-2004. Word 7 bit 11if set to one indicates that the device is allowed to report support for Force Unit Access commands. Word 7 bit 12 if set to one indicates that the device is allowed to report support for SMART Selective self-test, see 7.52.6.6
75
T13/1699-D Revision 3f
Word 7 bit 13 if set to one indicates that the device is allowed to report support for SMART Conveyance self-test, see 7.52.6.6. Word 7 bit 14 if set to one indicates that the device is allowed to report support for the Write-Read-Verify feature set. 7.10.3.6.6 Word (9:8): Reserved for serial ATA These words are reserved for Serial ATA. 7.10.3.6.7 Words (20:10) Reserved 7.10.3.6.8 Word 21: Command/features set supported part 2 Word 21 bits 15 if set to one indicates that the device is allowed to support the NV Cache feature set Word 21 bit 14 if set to one indicates that the device is allowed to support the NV Cache Power Management feature set Word 21 bit 13 if set to one indicates that the device is allowed to support the WRITE UNCORRECTABLE command. Word 21, bit 12 if set to one indicates that the device is allowed to report support for the Trusted Computing feature set. Word 21 bit 11 is reserved for e06144. Word 21 bits 10:0 are reserved. 7.10.3.6.9 Word 22: Command/features set supported part 3 Bits 15:0 are reserved. 7.10.3.6.10 Words (207:23): Reserved 7.10.3.6.11 Words (254:208): Vendor Specific 7.10.3.6.12 Word 255: Integrity word Bits (7:0) of this word shall contain the value A5h. Bits (15:8) of this word shall contain the data structure checksum. The data structure checksum shall be the twos complement of the sum of all byte in words (154:0) and the byte consisting of bits (7:0) of word 255. Each byte shall be added with unsigned arithmetic, and overflow shall be ignored. The sum of all bytes is zero when the checksum is correct.
76
December 11, 2006 7.10.4 DEVICE CONFIGURATION RESTORE - B1h/C0h, Non-data 7.10.4.1 Feature Set
T13/1699-D Revision 3f
This command is mandatory for devices implementing the Device Configuration Overlay feature set. 7.10.4.2 Description The DEVICE CONFIGURATION RESTORE command disables any setting previously made by a DEVICE CONFIGURATION SET command and restores the content of the IDENTIFY DEVICE data, IDENTIFY PACKET DEVICE data, and other feature settings to their original settings. The results of this action are indicated by the data returned from the Input Data of an DEVICE CONFIGURATION IDENTIFY command. If DCO RESTORE changes reporting of support for the Security feature set from 'not allowed' to 'allowed', and if DCO IDENTIFY would indicate that reporting of that support is 'allowed', then the device shall set the Security state to SEC1, setting IDENTIFY DEVICE data to the values described in table 9, and shall restore the saved Master password and Master Password Identifier ; otherwise, the Security state shall not change. 7.10.4.3 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description C0h N/A N/A Bit 15:13 12 11:8 Command 7.10.4.4 Normal Outputs See table 79. 7.10.4.5 Error Outputs Abort shall be set to one if a Host Protected Area has been set by a SET MAX ADDRESS or SET MAX ADDRESS EXT command, or if DEVICE CONFIGURATION FREEZE LOCK is set. See table 100. Description N/A Transport Dependent - See 6.1.9 Reserved
7:0 B1h
77
T13/1699-D Revision 3f 7.10.5 DEVICE CONFIGURATION SET - B1h/C3h, PIO Data Out 7.10.5.1 Feature Set
This command is mandatory for devices implementing the Device Configuration Overlay feature set. 7.10.5.2 Description The DEVICE CONFIGURATION SET command allows a device manufacturer or a personal computer system manufacturer to reduce the set of optional commands, modes, or feature sets supported by a device as indicated by a DEVICE CONFIGURATION IDENTIFY command. The DEVICE CONFIGURATION SET command may modify the data returned by IDENTIFY DEVICE or IDENTIFY PACKET DEVICE. When the IDENTIFY DEVICE data or IDENTIFY PACKET DEVICE data is changed, the device shall respond in a manner consistent with the new data. If a bit is set in the DCO data transmitted by the device that is not set in the DCO data received from a DEVICE CONFIGURATION IDENTIFY command, no action is taken for that bit. Modifying the maximum LBA of the device also modifies the address value returned by a READ NATIVE MAX ADDRESS or READ NATIVE MAX ADDRESS EXT command. The format of the DCO data transmitted by the device is described in 7.10.5.6 table 18. The restrictions on changing these bits are also described in 7.10.5.6. If any of the bit modification restrictions described are violated, the device shall return command aborted. The term is allowed indicates that the device may report that a feature is supported. If the device is not allowed to report support, then the device shall not support and shall report that the selected feature is both not supported and if appropriate not enabled. 7.10.5.3 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description C3h N/A N/A Bit 15:13 12 11:8 05h Command Description N/A Transport Dependent - See 6.1.9 Reserved
7:0 B1h
7.10.5.4 Normal Outputs See table 79. 7.10.5.5 Error Outputs See table 113
78
T13/1699-D Revision 3f
Table 18 Device Configuration Overlay (DCO) data structure (part 1 of 2) Word 0 1 Content Data structure revision Multiword DMA modes supported 15:3 Reserved 2 1 = Reporting support for Multiword DMA mode 2 and below is allowed 1 1 = Reporting support for Multiword DMA mode 1 and below is allowed 0 1 = Reporting support for Multiword DMA mode 0 is allowed Ultra DMA modes supported 15:7 Reserved 6 1 = Reporting support for Ultra DMA mode 6 and below is allowed 5 1 = Reporting support for Ultra DMA mode 5 and below is allowed 4 1 = Reporting support for Ultra DMA mode 4 and below is allowed 3 1 = Reporting support for Ultra DMA mode 3 and below is allowed 2 1 = Reporting support for Ultra DMA mode 2 and below is allowed 1 1 = Reporting support for Ultra DMA mode 1 and below is allowed 0 1 = Reporting support for Ultra DMA mode 0 is allowed Maximum LBA Command set/feature set supported part 1 15 Reserved 14 1 = Reporting support for Write-Read-Verify feature set is allowed 13 1 = Reporting support for SMART Conveyance self-test is allowed 12 1 = Reporting support for SMART Selective self-test is allowed 11 1 = Reporting support for Forced Unit Access is allowed 10 Reserved for ANSI/INCITS TR-37-2004 9 1 = Reporting support for Streaming feature set is allowed 8 1 = Reporting support for 48-bit Addressing feature set is allowed 7 1 = Reporting support for Host Protected Area feature set is allowed 6 1 = Reporting support for Automatic acoustic management is allowed 5 1 = Reporting support for READ/WRITE DMA QUEUED commands is allowed 4 1 = Reporting support for Power-up in Standby feature set is allowed 3 1 = Reporting support for Security feature set is allowed 2 1 = Reporting support for SMART error log is allowed 1 1 = Reporting support for SMART self-test is allowed 0 1 = Reporting support for SMART feature set is allowed Reserved for Serial ATA Reserved Command set/feature set supported part 2 15 Reserved for e05106 14 Reserved for e05106 13 1= Reporting support for the WRITE UNCORRECTABLE command is allowed 12 1= reporting of support for the Trusted Computing feature set is allowed 11 Reserved for e06144 10:0 Reserved Command set/feature set supported part 3
3-6 7
8-9 10-20 21
22
79
T13/1699-D Revision 3f
Table 18 Device Configuration Overlay (DCO) data structure (part 2 of 2) Word 23-207 208-254 255 15:0 Reserved Reserved Vendor Specific Integrity word 15:8 Checksum 7:0 Signature Content
7.10.5.6.1 Word 0: Data structure revision Word 0 shall contain the value 0002h. 7.10.5.6.2 Word 1: Multiword DMA modes supported Word 1 bits (15:3) are reserved. Word 1 bit 2 is cleared to disable support for Multiword DMA mode 2 and has the effect of clearing IDENTIFY DEVICE data word 63 bit 2 or IDENTIFY PACKET DEVICE data word 63 bit 2. This bit shall not be cleared to zero if Multiword DMA mode 2 is currently selected. Word 1 bit 1 is cleared to disable support for Multiword DMA mode 1 and has the effect of clearing bit 1 to zero in word 63 of the IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data. This bit shall not be cleared to zero if Multiword DMA mode 2 is supported or Multiword DMA mode 1 or 2 is selected. Word 1 bit 0 shall not be cleared to zero. 7.10.5.6.3 Word 2: Ultra DMA modes supported Word 2 bits (15:7) are reserved. Word 2 bit 6 is cleared to zero to disable support for Ultra DMA mode 6 and has the effect of clearing IDENTIFY DEVICE data word 88 bit 6 or IDENTIFY PACKET DEVICE data word 88 bit 6. This bit shall not be cleared to zero if Ultra DMA mode 6 is currently selected. Word 2 bit 5 is cleared to zero to disable support for Ultra DMA mode 5 and has the effect of clearing IDENTIFY DEVICE data word 88 bit 5 or IDENTIFY PACKET DEVICE data word 88 bit 5. This bit shall not be cleared to zero if Ultra DMA mode 5 is currently selected. Word 2 bit 4 is cleared to zero to disable support for Ultra DMA mode 4 and has the effect of clearing IDENTIFY DEVICE data word 88 bit 4 or IDENTIFY PACKET DEVICE data word 88 bit 4. This bit shall not be cleared to zero if Ultra DMA mode 5 is supported or if Ultra DMA mode 5 or 4 is selected. Word 2 bit 3 is cleared to zero to disable support for Ultra DMA mode 3 and has the effect of clearing IDENTIFY DEVICE data word 88 bit 3 or IDENTIFY PACKET DEVICE data word 88 bit3. This bit shall not be cleared to zero if Ultra DMA mode 5 or 4 is supported or if Ultra DMA mode 5, 4, or 3 is selected. Word 2 bit 2 is cleared to zero to disable support for Ultra DMA mode 2 and has the effect of clearing IDENTIFY DEVICE data word 88 bit 2 or IDENTIFY PACKET DEVICE data word 88 bit 2. This bit shall not be cleared to zero if Ultra DMA mode 5, 4, or 3 is supported or if Ultra DMA mode 5, 4, 3, or 2 is selected. Word 2 bit 1 is cleared to zero to disable support for Ultra DMA mode 1 and has the effect of clearing IDENTIFY DEVICE data word 88 bit 1 or IDENTIFY PACKET DEVICE data word 88 bit 1. This bit shall not be cleared to zero if Ultra DMA mode 5, 4, 3, or 2 is supported or if Ultra DMA mode 5, 4, 3, 2, or 1 is selected. Word 2 bit 0 is cleared to zero to disable support for Ultra DMA mode 0 and has the effect of clearing IDENTIFY DEVICE data word 88 bit 0 or IDENTIFY PACKET DEVICE data word 88 bit 0 This bit shall not be cleared to zero if Ultra DMA mode 5, 4, 3, 2, or 1 is supported or if Ultra DMA mode 5, 4, 3, 2, 1, or 0 is selected. 7.10.5.6.4 Words (6:3): Maximum LBA Words (6:3) define the maximum LBA. This shall be the highest address accepted by the device after execution of the command. When this value is changed, the content of IDENTIFY DEVICE data words (61:60) and (103:100) shall be changed as described in the SET MAX ADDRESS and SET MAX ADDRESS EXT command 80 Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS)
T13/1699-D Revision 3f
descriptions to reflect the maximum address set with this command. This value shall not be changed and command aborted shall be returned if a Host Protected Area has been established by the execution of a SET MAX ADDRESS or SET MAX ADDRESS EXT command with an address value less than that returned by a READ NATIVE MAX ADDRESS or READ NATIVE MAX ADDRESS EXT command. Any data contained in the Host Protected Area is not affected. 7.10.5.6.5 Word 7: Command/features set supported part 1 Word 7 bits (15:14) are reserved. Word 7 bit 14 is cleared to zero to disable support for the Write-Read-Verify feature set and has the effect of clearing word 119 bit 1 and word 120 bit 1. Word 7 bit 13 is cleared to zero to disable support for the SMART Conveyance self-test. Subsequent attempts to start this test via the SMART EXECUTE OFF-LINE IMMEDIATE command shall cause that command to abort. In addition, the SMART READ DATA command shall clear bit 5 to zero in the Off-line data collection capabilities field. If this bit is supported by DEVICE CONFIGURATION SET, then this feature shall not be disabled by bit 1 of word 7. Word 7 bit 12 is cleared to zero to disable support for the SMART Selective self-test. Subsequent attempts to start this test via the SMART EXECUTE OFF-LINE IMMEDIATE command shall cause that command to abort. In addition, the SMART READ DATA command shall clear bit 6 to zero in the Off-line data collection capabilities field. If this bit is supported by DEVICE CONFIGURATION SET, then this feature shall not be disabled by bit 1 of word 7. Word 7 bit 11 is cleared to zero to disable support for the Force Unit Access commands and has the effect of clearing IDENTIFY DEVICE data word 84 bits (7:6) or IDENTIFY PACKET DEVICE data word 84 bits (7:6). Word 7 bit 10 is Reserved for ANSI/INCITS TR-37-2004 Word 7 bit 9 is cleared to zero to disable support for the Streaming feature set and has the effect of clearing IDENTIFY DEVICE data or IDENTIFY PACKET DEVICE data word 84 bits 4, 9 and 10 and IDENTIFY DEVICE data or IDENTIFY PACKET DEVICE data word 87 bits 4, 9 and 10 to zero and clearing IDENTIFY DEVICE data or IDENTIFY PACKET DEVICE data words (99:95) and IDENTIFY DEVICE data word 104. Word 7 bit 8 is cleared to zero to disable support for the 48-bit Addressing feature set and has the effect of clearing IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data word 83 bit 10, word 86 bit 10, and words (103:100) to zero. Word 7 bit 7 is cleared to zero to disable support for the Host Protected Area feature set and has the effect of clearing IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data word 82 bit 10, word 85 bit 10, word 83 bit 8, and word 86 bit 8 to zero. If a Host Protected Area has been established by use of the SET MAX ADDRESS or SET MAX ADDRESS EXT command, these bits shall not be cleared to zero and the device shall return command aborted. Word 7 bit 6 is cleared to zero to disable for the Automatic Acoustic Management feature set and has the effect of clearing IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data word 83 bit 9 and word 94 to zero. Word 7 bit 5 is cleared to zero to disable support for the READ DMA QUEUED and WRITE DMA QUEUED commands and has the effect of clearing IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data word 83 bit 1and word 86 bit 1 to zero. Word 7 bit 4 is cleared to zero to disable support for the Power-up in Standby feature set and has the effect of clearing IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data word 83 bits (6:5) and word 86 bits (6:5) to zero. If Power-up in Standby has been enabled by a jumper, these bits shall not be cleared. When word 7 bit 3 is cleared to zero, if Security is Enabled, then the device shall return command aborted. When word 7 bit 3 is cleared to zero, if Security is Disabled then any stored Master Password and Master Password Identifier shall be preserved and IDENTIFY DEVICE or IDENTIFY PACKET DEVICE commands shall respond as follows: clear word 82 bit 1 to zero, clear word 85 bit 1 to zero, clear words 89, 90, 92 and 128 to zero. When word 7 bit 3 is set to one, the Security state shall not change. Word 7 bit 2 is cleared to zero to disable support for the SMART error logging and has the effect of clearing IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data word 84 bit 0 and 87bit 0 to zero.
81
T13/1699-D Revision 3f
Word 7 bit 1 is cleared to zero to disable support for the SMART self-test and has the effect of clearing IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data word 84 bit 1 and word 87 bit 1to zero. Word 7 bit 1 disables support for the offline, short, extended self-tests (off-line and captive modes). For backward compatibility, if word 7 bits 12 or 13 of are not supported, Word 7 bit 1 may also disable support for conveyance self-test and selective self-test, see 7.52.6.6. Word 7 bit 0 is cleared to zero to disable support for the SMART feature set and has the effect of clearing IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data word 82 bit 0 and word 85 bit 0 to zero. If bits (2:1) of word 7 are not cleared to zero or if the SMART feature set has been enabled by use of the SMART ENABLE OPERATIONS command, these bits shall not be cleared and the device shall return command aborted. 7.10.5.6.6 Words (9:8): Reserved for serial ATA These words are reserved for Serial ATA use. 7.10.5.6.7 Words (20:10) Reserved 7.10.5.6.8 Word 21: Command/features set supported part 2 Word 21 bits 15:14 Reserved for technical report. Word 21 bit 13 if set to one indicates that the device is allowed to support the WRITE UNCORRECTABLE command. Word 21 bit 12 shall be cleared to zero to disable support for the Trusted Computing feature set and has the effect of clearing IDENTIFY DEVICE data word 48 bit 0 to zero. This value shall not be changed and command aborted shall be returned if the Security Mode feature set is enabled. Word 21 bits 11 is reserved for e06144. Word 21 bits 10:0 are reserved. 7.10.5.6.9 Word 22: Command/features set supported part 3 Bits 15:0 are reserved. 7.10.5.6.10 Words (207:23): Reserved 7.10.5.6.11 Words (254:208): Vendor Specific 7.10.5.6.12 Word 255: Integrity word Bits (7:0) of this word shall contain the value A5h. Bits (15:8) of this word shall contain the data structure checksum. The data structure checksum shall be the twos complement of the sum of all byte in words (254:0) and the byte consisting of bits (7:0) of word 255. Each byte shall be added with unsigned arithmetic, and overflow shall be ignored. The sum of all bytes is zero when the checksum is correct.
82
T13/1699-D Revision 3f
7:0 08h
7.11.4 Normal Outputs See table 85. 7.11.5 Error Outputs If DEVICE RESET is supported, it should not complete with an error. If the device is able to complete the DEVICE RESET and maintain the device setting then DEVICE RESET shall complete with Check Condition cleared to zero. If the device reverts to its default state, the device shall report an exception by setting the Check Condition bit in the Status field.
83
T13/1699-D Revision 3f
84
December 11, 2006 7.12.3 Inputs Word 00h Name Feature Sub command 00h 01h 02h 03h Description Description
T13/1699-D Revision 3f
Reserved Obsolete Reserved Optional Download with offsets and save microcode for immediate and future use. 04h-06h Reserved 07h Download and save microcode for immediate and future use. 08-FFh Reserved
01h
Count Bit Description 15:8 Reserved 7:0 Block count (Low Order)
02h-04h
LBA Bit Description 47:24 Reserved 23:8 Buffer offset (only used for Feature = 03h, otherwise this field shall be reserved) 7:0 Block count (High Order)
05h
Device Bit 15 14 13 12 11:8 Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
7:0 92h
7.12.4 Normal Outputs If IDENTIFY DEVICE data word 234 or IDENTIFY DEVICE data word 235 have a value other than 0000h or FFFFh then table 19 describes the indicator returned in the count field. Table 19 DOWNLOAD MICROCODE Mode 3 return options Value 00h 01h 02h 03h-FFh Description No indication of download microcode status. Indicates the device is expecting more download microcode commands to follow. Indicates that the drive has applied the new microcode. Reserved
85
The device shall return command aborted if the device did not accept the microcode data. The device shall return command aborted if subcommand code is not a supported value. See table 100.
86
T13/1699-D Revision 3f
7:0 90h
7.13.4 Normal Outputs See table 85. The diagnostic code written into the Error field is an 8-bit code. Table 20 defines these values. Table 20 Diagnostic codes Code a 01h 00h, 02h-7Fh 81h 80h, 82h-FFh Description When this code is in the Device 0 Error field Device 0 passed, Device 1 passed or not present Device 0 failed, Device 1 passed or not present Device 0 passed, Device 1 failed Device 0 failed, Device 1 failed When this code is in the Device 1 Error field 01h Device 1 passed b 00h, 02h-7Fh Device 1 failed b a Codes other than 01h and 81h may indicate additional information about the failure(s). b If Device 1 is not present, the host may see the information from Device 0 even though Device 1 is selected. 7.13.5 Error Outputs This command shall complete without setting the Error bit in the Status field, see table 20.
87
T13/1699-D Revision 3f
7:0 E7h
7.14.4 Normal Outputs See table 79. 7.14.5 Error Outputs An unrecoverable error encountered during execution of writing data results in the termination of the command. The logical sector address of the sector where the first unrecoverable error occurred. Subsequent FLUSH CACHE commands continue the process of flushing the cache starting with the first logical sector after the sector in error is returned. LBA bits 47:28 shall be cleared to zero. See table 103. If an error occurs during the flush process and the LBA of the data in error is outside the 28 bit address range then the LBA of the logical sector in error shall be incorrectly reported. For correct error reporting in a device that has more than a 28 bit address range, use FLUSH CACHE EXT (see 7.15).
88
T13/1699-D Revision 3f
7:0 EAh
7.15.4 Normal Outputs See table 92. 7.15.5 Error Outputs An unrecoverable error encountered while writing data results in the termination of the command and the logical sector address of the logical sector where the first unrecoverable error occurred is returned. Subsequent FLUSH CACHE EXT commands continue the process of flushing the cache starting with the first sector after the sector in error. See table 103.
89
T13/1699-D Revision 3f
7:0 ECh
7.16.4 Normal Outputs for devices that do not implement the PACKET feature set See table 79. 7.16.5 Normal Outputs for PACKET feature set devices In response to this command, devices that implement the PACKET feature set shall post command aborted and place the PACKET feature set signature in the appropriate fields (see 7.11.4). 7.16.6 Error Outputs Devices implementing the General feature set shall not report an error.
90
December 11, 2006 7.16.7 Input Data Table 21 IDENTIFY DEVICE data (part 1 of 10) O Word M 0 M
T13/1699-D Revision 3f
O M
M M M
48
49 M
S FV P Description B General configuration bit-significant information: F 15 0 = ATA device X 14:8 Retired F 7:6 Obsolete X 5:3 Retired V 2 Response incomplete X 1 Retired F 0 Reserved X Obsolete B V Specific configuration X Obsolete X Retired X Obsolete N V Reserved for assignment by the CompactFlash Association X Retired B F Serial number (20 ASCII characters) X Retired X Obsolete B F Firmware revision (8 ASCII characters) B F Model number (40 ASCII characters) F 15:8 80h F 7:0 00h = Reserved P F 01h-FFh = Maximum number of logical sectors that shall be transferred per DRQ data block on READ/WRITE MULTIPLE commands F Trusted Computing feature set options 15 Shall be cleared to zero 14 Shall be set to zero 13:1 Reserved for the Trusted Computing Group 0 1=Trusted Computing feature set is supported Capabilities F 15:14 Reserved for the IDENTIFY PACKET DEVICE command. B F 13 1 = Standby timer values as specified in this standard are supported 0 = Standby timer values shall be managed by the device F 12 Reserved for the IDENTIFY PACKET DEVICE command. P F 11 1 = IORDY supported 0 = IORDY may be supported P F 10 1 = IORDY may be disabled B F 9 1 = LBA supported P F 8 1 = DMA supported. X 7:0 Retired
91
T13/1699-D Revision 3f Table 21 IDENTIFY DEVICE data (part 2 of 10) O Word M 50 M S FV P F F F X F X F B B B P 54-58 59 M B B 60-61 M 62 63 M B P P P P P P P P P P 64 M P 65 M P 66 M P 67 M P 68 M P 69-70 71-74 F F F F F F F F X X F V V F X F V V V F F F F F F Description
B 51-52 53 M
Capabilities 15 Shall be cleared to zero. 14 Shall be set to one. 13:2 Reserved. 1 Obsolete 0 Shall be set to one to indicate a device specific Standby timer value minimum. Obsolete 15:8 Reserved for e06144 7:3 Reserved 2 1 = the fields reported in word 88 are valid 0 = the fields reported in word 88 are not valid 1 1 = the fields reported in words (70:64) are valid 0 = the fields reported in words (70:64) are not valid 0 Obsolete Obsolete 15:9 Reserved 8 1 = Multiple sector setting is valid 7:0 xxh = Current setting for number of logical sectors that shall be transferred per DRQ data block on READ/WRITE Multiple commands Total number of user addressable logical sectors Obsolete 15:11 Reserved 10 1 = Multiword DMA mode 2 is selected 0 = Multiword DMA mode 2 is not selected 9 1 = Multiword DMA mode 1 is selected 0 = Multiword DMA mode 1 is not selected 8 1 = Multiword DMA mode 0 is selected 0 = Multiword DMA mode 0 is not selected 7:3 Reserved 2 1 = Multiword DMA mode 2 and below are supported 1 1 = Multiword DMA mode 1 and below are supported 0 1 = Multiword DMA mode 0 is supported 15:8 Reserved 7:0 PIO modes supported Minimum Multiword DMA transfer cycle time per word 15:0 Cycle time in nanoseconds Manufacturers recommended Multiword DMA transfer cycle time 15:0 Cycle time in nanoseconds Minimum PIO transfer cycle time without flow control 15:0 Cycle time in nanoseconds Minimum PIO transfer cycle time with IORDY flow control 15:0 Cycle time in nanoseconds Reserved Reserved for the IDENTIFY PACKET DEVICE command.
92
December 11, 2006 Table 21 IDENTIFY DEVICE data (part 3 of 10) O Word M 75 O S FV P Description
T13/1699-D Revision 3f
76-79 80 M
B S B
B B B B B
81 M 82 M
B B B B N B B B B B B B B B
Queue depth F 15:5 Reserved F 4:0 Maximum queue depth - 1 F Reserved for Serial ATA Major revision number 0000h or FFFFh = device does not report version F 15:9 Reserved F 8 1 = supports ATA8-ACS F 7 1 = supports ATA/ATAPI-7 F 6 1 = supports ATA/ATAPI-6 F 5 1 = supports ATA/ATAPI-5 F 4 1 = supports ATA/ATAPI-4 F 3 Obsolete X 2 Obsolete X 1 Obsolete F 0 Reserved F Minor revision number Command set supported. X 15 Obsolete F 14 1 = NOP command supported F 13 1 = READ BUFFER command supported F 12 1 = WRITE BUFFER command supported X 11 Obsolete F 10 1 = Host Protected Area feature set supported F 9 1 = DEVICE RESET command supported F 8 1 = SERVICE interrupt supported F 7 1 = release interrupt supported F 6 1 = look-ahead supported F 5 1 = write cache supported F 4 Shall be cleared to zero to indicate that the PACKET feature set is not supported. F 3 1 = mandatory Power Management feature set supported F 2 Obsolete F 1 1 = Security Mode feature set supported F 0 1 = SMART feature set supported
93
T13/1699-D Revision 3f Table 21 IDENTIFY DEVICE data (part 4 of 10) O Word M 83 M S FV P F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F F Description
B B B B B B B B B B B N B B 84 M
B B B B B B B B B N B B B
Command sets supported. 15 Shall be cleared to zero 14 Shall be set to one 13 1 = FLUSH CACHE EXT command supported 12 1 = mandatory FLUSH CACHE command supported 11 1 = Device Configuration Overlay feature set supported 10 1 = 48-bit Address feature set supported 9 1 = Automatic Acoustic Management feature set supported 8 1 = SET MAX security extension supported 7 See Address Offset Reserved Area Boot, INCITS TR27:2001 6 1 = SET FEATURES subcommand required to spin-up after power-up 5 1 = Power-Up In Standby feature set supported 4 Obsolete 3 1 = Advanced Power Management feature set supported 2 1 = CFA feature set supported 1 1 = READ/WRITE DMA QUEUED supported 0 1 = DOWNLOAD MICROCODE command supported Command set/feature supported 15 Shall be cleared to zero 14 Shall be set to one 13 1 = IDLE IMMEDIATE with UNLOAD FEATURE supported 12 Reserved for technical report INCITS TR-37-2004 (TLC) 11 Reserved for technical report INCITS TR-37-2004 (TLC) 10:9 1 = Obsolete 8 1 = 64-bit World wide name supported 7 1 = WRITE DMA QUEUED FUA EXT command supported 6 1 = WRITE DMA FUA EXT and WRITE MULTIPLE FUA EXT commands supported 5 1 = General Purpose Logging feature set supported 4 1 = Streaming feature set supported 3 1 = Media Card Pass Through Command feature set supported 2 1 = Media serial number supported 1 1 = SMART self-test supported 0 1 = SMART error logging supported
94
December 11, 2006 Table 21 IDENTIFY DEVICE data (part 5 of 10) O Word M 85 M S FV P X F F F X V F V V V V F F F V V
T13/1699-D Revision 3f
B B B B N B B B B
B B B B 86 M B B B B B B B B B B B B N B B
F F F F F V V F F V V V F F F
Description Command set/feature enabled/supported. 15 Obsolete 14 1 = NOP command supported 13 1 = READ BUFFER command supported 12 1 = WRITE BUFFER command supported 11 Obsolete 10 1 = Host Protected Area has been established (i.e., the maximum LBA is less than the maximum native LBA) 9 1 = DEVICE RESET command supported 8 1 = SERVICE interrupt enabled 7 1 = release interrupt enabled 6 1 = look-ahead enabled 5 1 = write cache enabled 4 Shall be cleared to zero to indicate that the PACKET feature set is not supported. 3 1 = Power Management feature set enabled 2 Obsolete 1 1 = Security Mode feature set enabled 0 1 = SMART feature set enabled Command set/feature enabled/supported. 15 1 = Words 120:119 are valid 14 Reserved 13 1 = FLUSH CACHE EXT command supported 12 1 = FLUSH CACHE command supported 11 1 = Device Configuration Overlay supported 10 1 = 48-bit Address features set supported 9 1 = Automatic Acoustic Management feature set enabled 8 1 = SET MAX security extension enabled by SET MAX SET PASSWORD 7 Reserved for Address Offset Reserved Area Boot, INCITS TR27:2001 6 1 = SET FEATURES subcommand required to spin-up after power-up 5 1 = Power-Up In Standby feature set enabled 4 Obsolete 3 1 = Advanced Power Management feature set enabled 2 1 = CFA feature set supported 1 1 = READ/WRITE DMA QUEUED command supported 0 1 = DOWNLOAD MICROCODE command supported
95
B B B B B B B B B N B B B 88 O P P P P P P P P P P P P P P P P P P P P P P B B B B
89 90 91 92
O O O O
Description Command set/feature enabled/supported. 15 Shall be cleared to zero 14 Shall be set to one 13 1 = IDLE IMMEDIATE with UNLOAD FEATURE supported 12 Reserved for technical report- INCITS TR-37-2004 (TLC) 11 Reserved for technical report- INCITS TR-37-2004 (TLC) 10:9 1 = Obsolete 8 1 = 64 bit World wide name supported 7 1 = WRITE DMA QUEUED FUA EXT command supported 6 1 = WRITE DMA FUA EXT and WRITE MULTIPLE FUA EXT commands supported 5 1 = General Purpose Logging feature set supported 4 1 = Obsolete 3 1 = Media Card Pass Through Command feature set supported 2 1 = Media serial number is valid 1 1 = SMART self-test supported 0 1 = SMART error logging supported Ultra DMA modes 15 Reserved 14 1 = Ultra DMA mode 6 is selected 0 = Ultra DMA mode 6 is not selected 13 1 = Ultra DMA mode 5 is selected 0 = Ultra DMA mode 5 is not selected 12 1 = Ultra DMA mode 4 is selected 0 = Ultra DMA mode 4 is not selected 11 1 = Ultra DMA mode 3 is selected 0 = Ultra DMA mode 3 is not selected 10 1 = Ultra DMA mode 2 is selected 0 = Ultra DMA mode 2 is not selected 9 1 = Ultra DMA mode 1 is selected 0 = Ultra DMA mode 1 is not selected 8 1 = Ultra DMA mode 0 is selected 0 = Ultra DMA mode 0 is not selected 7 Reserved 6 1 = Ultra DMA mode 6 and below are supported 5 1 = Ultra DMA mode 5 and below are supported 4 1 = Ultra DMA mode 4 and below are supported 3 1 = Ultra DMA mode 3 and below are supported 2 1 = Ultra DMA mode 2 and below are supported 1 1 = Ultra DMA mode 1 and below are supported 0 1 = Ultra DMA mode 0 is supported Time required for security erase unit completion Time required for Enhanced security erase completion Current advanced power management value Master Password Identifier
96
December 11, 2006 Table 21 IDENTIFY DEVICE data (part 7 of 10) O Word M 93 S FV P
T13/1699-D Revision 3f
P P P P P P P P P P P P
F F V
F V V
F F V V V V
F F V F V V F V V F
Description Hardware reset result. The contents of bits (12:0) of this word shall change only during the execution of a hardware reset. See 7.16.7.41 for more information. 15 Shall be cleared to zero. 14 Shall be set to one. 13 1 = device detected CBLID- above VBiHB 0 = device detected CBLID- below ViL B B 12:8 Device 1 hardware reset result. Device 0 shall clear these bits to zero. Device 1 shall set these bits as follows: 12 Reserved. 11 0 = Device 1 did not assert PDIAG-. 1 = Device 1 asserted PDIAG-. 10:9 These bits indicate how Device 1 determined the device number: 00 = Reserved. 01 = a jumper was used. 10 = the CSEL signal was used. 11 = some other method was used or the method is unknown. 8 Shall be set to one. 7:0 Device 0 hardware reset result. Device 1 shall clear these bits to zero. Device 0 shall set these bits as follows: 7 Reserved. 6 0 = Device 0 does not respond when Device 1 is selected. 1 = Device 0 responds when Device 1 is selected. 5 0 = Device 0 did not detect the assertion of DASP-. 1 = Device 0 detected the assertion of DASP-. 4 0 = Device 0 did not detect the assertion of PDIAG-. 1 = Device 0 detected the assertion of PDIAG-. 3 0 = Device 0 failed diagnostics. 1 = Device 0 passed diagnostics. 2:1 These bits indicate how Device 0 determined the device number: 00 = Reserved. 01 = a jumper was used. 10 = the CSEL signal was used. 11 = some other method was used or the method is unknown. 0 Shall be set to one. 15:8 Vendors recommended acoustic management value. 7:0 Current automatic acoustic management value. Stream Minimum Request Size Streaming Transfer Time - DMA Streaming Access Latency - DMA and PIO Streaming Performance Granularity Total Number of User Addressable Sectors for the 48-bit Address feature set. Streaming Transfer Time - PIO Reserved
97
T13/1699-D Revision 3f Table 21 IDENTIFY DEVICE data (part 8 of 10) O Word M 106 O S FV P B B B B B B B B B B B B F F F F F F F F F F F V F F F F B B B B P 120 M F F F B B B B P 121-126 127 O F F F F F F F F F F F
Description Physical sector size / Logical Sector Size 15 Shall be cleared to zero 14 Shall be set to one 13 1 = Device has multiple logical sectors per physical sector. 12 1= Device Logical Sector Longer than 256 Words 11:4 Reserved 3:0 2X logical sectors per physical sector Inter-seek delay for ISO-7779 acoustic testing in microseconds 15:12 NAA (3:0) 11:0 IEEE OUI (23:12) 15:4 IEEE OUI (11:0) 3:0 Unique ID (35:32) 15:0 Unique ID (31:16) 15:0 Unique ID (15:0) Reserved for world wide name extension to 128 bits Reserved for INCITS TR-37-2004 Words per Logical Sector Supported Settings (Continued from words 84:82) 15 Shall be cleared to zero 14 Shall be set to one 13:6 Reserved 5 Reserved for e06144 4 1 = The Segmented feature for DOWNLOAD MICROCODE is supported 3 1 = READ and WRITE DMA EXT GPL optional commands are supported 2 1 = WRITE UNCORRECTABLE is supported 1 1 = Write-Read-Verify feature set is supported 0 reserved for DT1825 Command set/feature enabled/supported. (Continued from words 87:85) 15 Shall be cleared to zero 14 Shall be set to one 13:6 Reserved 5 Reserved for e06144 4 1 = The Segmented feature for DOWNLOAD MICROCODE is supported 3 1 = READ and WRITE DMA EXT GPL optional commands are supported 2 1 = WRITE UNCORRECTABLE is supported 1 1 = Write-Read-Verify feature set is enabled 0 Reserved for DT1825 Reserved for expanded supported and enabled settings Obsolete
P P
98
December 11, 2006 Table 21 IDENTIFY DEVICE data (part 9 of 10) O Word M 128 O S FV P Description
T13/1699-D Revision 3f
B B B B B B B 129-159 160 O
207-208 209
215 216
O O
B B
Security status F 15:9 Reserved V 8 Security level 0 = High, 1 = Maximum F 7:6 Reserved F 5 1 = Enhanced security erase supported V 4 1 = Security count expired V 3 1 = Security frozen V 2 1 = Security locked V 1 1 = Security enabled F 0 1 = Security supported X Vendor specific CFA power mode 1 F 15 Word 160 supported F 14 Reserved F 13 CFA power mode 1 is required for one or more commands implemented by the device V 12 CFA power mode 1 disabled F 11:0 Maximum current in ma X Reserved for assignment by the CompactFlash Association V Current media serial number (60 ASCII characters) SCT Command Transport X 15:12 Vendor Specific 11:6 Reserved F 5 SCT Command Transport Data Tables supported F 4 SCT Command Transport Features Control supported F 3 SCT Command Transport Error Recovery Control supported F 2 SCT Command Transport Write Same supported F 1 SCT Command Transport Long Sector Access supported F 0 SCT Command Transport supported F Reserved for CE-ATA. F Alignment of logical blocks within a larger physical block 15 Shall be cleared to zero 14 Shall be set to one 13:0 Logical sector offset within the first physical sector where the first logical sector is placed. V Write-Read-Verify Sector Count Mode 3 Only F Verify Sector Count Mode 2 Only NV Cache Capabilities F 15:12 NV Cache feature set version F 11:8 NV Cache Power Mode feature set version 7:5 Reserved V 4 1 = NV Cache feature set enabled 3:1 Reserved V 0 1 = NV Cache Power Mode feature set enabled V NV Cache Size in Logical Blocks (LSW) V NV Cache Size in Logical Blocks (MSW) 99
T13/1699-D Revision 3f Table 21 IDENTIFY DEVICE data (part 10 of 10) O Word M 217 O 218 O 219 O
220
221 222 M
S FV P Description B V NV Cache Read Transfer Speed in MB/s B V NV Cache Write Transfer Speed in MB/s B NV Cache Options 15:8 Reserved F 7:0 Device Estimated Time to Spin Up in Seconds B 15:8 Reserved V 7:0 Write-Read-Verify feature set current mode Reserved F Transport Major revision number. 0000h or FFFFh = device does not report version B 15:12 Transport Type 0 = Parallel, 1 = Serial, 2-15 = Reserved
Parallel Serial S 11:4 Reserved Reserved S 3 Reserved SATA Rev 2.5 S 2 Reserved SATA II: Extensions S 1 Reserved SATA 1.0a P 0 ATA8-APT ATA8-AST 223 M B F Transport Minor revision number 224-233 F Reserved for CE-ATA 234 O B F Minimum number of 512 byte units per DOWNLOAD MICROCODE command mode 3 235 O B F Maximum number of 512 byte units per DOWNLOAD MICROCODE command mode 3 236-254 Reserved 255 M X Integrity word B 15:8 Checksum B 7:0 Signature V The contents of the field is variable and may Key: change depending on the state of the device or O/M Mandatory/optional requirement. the commands executed by the device. M Support of the word is mandatory. X The content of the field may be fixed or O Support of the word is optional. variable F/V Fixed/variable content F The content of the field is fixed and does S/P Content applies to Serial or Parallel transport S Serial Transport not change. The DCO command may change the value of a fixed field. For P Parallel Transport removable media devices, these values may B Both Serial and Parallel Transports change when media is removed or changed. N Belongs to a transport other than Serial or Parallel
7.16.7.1 Word 0: General configuration Devices that conform to this standard shall clear bit 15 to zero. Bits 7:6 are obsolete. If bit 2 is set to one it indicates that the content of the IDENTIFY DEVICE data is incomplete. This may occur if the device supports the Power-up in Standby feature set and required data is contained on the device media. In this case the content of at least word 0 and word 2 shall be valid.
100
T13/1699-D Revision 3f
Devices supporting the CFA feature set shall place the value 848Ah in word 0. In this case, the above definitions for the bits in word 0 are not valid. 7.16.7.2 Word 1: Obsolete 7.16.7.3 Word 2: Specific configuration Word 2 shall be set as follows: Value Description 37C8h Device requires SET FEATURES subcommand to spin-up after power-up and IDENTIFY DEVICE data is incomplete (see 4.17). 738Ch Device requires SET FEATURES subcommand to spin-up after power-up and IDENTIFY DEVICE data is complete (see 4.17). 8C73h Device does not require SET FEATURES subcommand to spin-up after power-up and IDENTIFY DEVICE data is incomplete (see 4.17). C837h Device does not require SET FEATURES subcommand to spin-up after power-up and IDENTIFY DEVICE data is complete (see 4.17). All other values Reserved. 7.16.7.4 Word 3: Obsolete 7.16.7.5 Words 4-5: Retired 7.16.7.6 Word 6: Obsolete 7.16.7.7 Words 7-8: Reserved for assignment by the CompactFlash Association 7.16.7.8 Word 9: Retired 7.16.7.9 Words 10-19: Serial number This field contains the serial number of the device. The contents of this field is an ASCII character string of twenty bytes. The device shall pad the character string with spaces (20h), if necessary, to ensure that the string is the proper length. The combination of Serial number (words 10-19) and Model number (words 27-46) shall be unique for a given manufacturer (See 0). 7.16.7.10 Words 20-21: Retired 7.16.7.11 Word 22: Obsolete 7.16.7.12 Words 23-26: Firmware revision This field contains the firmware revision number of the device. The contents of this field is an ASCII character string of eight bytes. The device shall pad the character string with spaces (20h), if necessary, to ensure that the string is the proper length (See 0). 7.16.7.13 Words 27-46: Model number This field contains the model number of the device. The contents of this field is an ASCII character string of forty bytes. The device shall pad the character string with spaces (20h), if necessary, to ensure that the string is the
101
T13/1699-D Revision 3f
proper length. The combination of Serial number (words 10-19) and Model number (words 27-46) shall be unique for a given manufacturer. 7.16.7.14 Word 47: READ/WRITE MULTIPLE support For PATA devices Bits (7:0) of this word define the maximum number of logical sectors per DRQ data block that the device supports for READ/WRITE MULTIPLE commands. For SATA devices this field shall be set to 16 or less. 7.16.7.15 Word 48: Trusted Computing feature set options Bit 0 of word 48 when set to one, indicates that the Trusted Computing feature set is supported. 7.16.7.16 Words 49-50: Capabilities Bits (15:14) of word 49 are reserved for use in the IDENTIFY PACKET DEVICE data. Bit 13 of word 49 is used to determine whether a device uses the Standby timer values as defined in this standard. Table 25 specifies the Standby timer values used by the device if bit 13 is set to one. If bit 13 is cleared to zero, the timer values shall be vendor specific. Bit 12 of word 49 is reserved for use in the IDENTIFY PACKET DEVICE data. For PATA devices bit 11 of word 49 indicates whether a device supports IORDY. If this bit is set to one, then the device supports IORDY operation. All devices except CFA and PCMCIA devices shall support PIO mode 3 or higher, shall support IORDY, and shall set this bit to one. For SATA devices bit 11 of word 49 shall be set to one. For PATA devices bit 10 of word 49 is used to indicate a devices ability to enable or disable the use of IORDY. If this bit is set to one, then the device supports the disabling of IORDY. Disabling and enabling of IORDY is accomplished using the SET FEATURES command. For SATA devices bit 10 of word 49 shall be set to one. Bit 9 of word 49 shall be set to one to indicate that an LBA transition is supported. Bits 8 of word 49 Shall be set to one to indicate that DMA is supported. For devices not implementing the CompactFlash feature set this bit shall be set to one. Bits (7:0) of word 49 are retired. Bit 15 of word 50 shall be cleared to zero to indicate that the contents of word 50 are valid. Bit 14 of word 50 shall be set to one to indicate that the contents of word 50 are valid. Bits (13:2) of word 50 are reserved. Bit 1 of word 50 is obsolete. Bit 0 of word 50 set to one indicates that the device has a minimum Standby timer value that is device specific. 7.16.7.17 Words 51-52: Obsolete 7.16.7.18 Word 53: Field validity Bit 0 of word 53 is obsolete. For PATA devices when bit 1 of word 53 is set to one, the values reported in words 64-70 are valid. If this bit is cleared to zero, the values reported in words 64-70 are not valid. All devices except CFA and PCMCIA devices shall support PIO mode 3 or above and shall set bit 1 of word 53 to one and support the fields contained in words 64-70. For SATA devices bit 1 of word 53 shall be set to one. For PATA devices if the device supports Ultra DMA and the values reported in word 88 are valid, then bit 2 of word 53 shall be set to one. If the device does not support Ultra DMA and the values reported in word 88 are not valid, then this bit is cleared to zero. 102 Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS)
December 11, 2006 For SATA devices bit 2 of word 53 shall be set to one. 7.16.7.19 Words 54-58: Obsolete 7.16.7.20 Word 59: Multiple sector setting
T13/1699-D Revision 3f
If bit 8 is set to one, bits (7:0) reflect the number of logical sectors currently set to transfer on a READ/WRITE MULTIPLE command. This field may default to the preferred value for the device (see 7.50). 7.16.7.21 Words 60-61: Total number of user addressable sectors This field contains a value that is one greater than the maximum user accessible logical block address. The maximum value that shall be placed in this field is 0FFF_FFFFh. 7.16.7.22 Word 62: Obsolete 7.16.7.23 Word 63: Multiword DMA transfer Word 63 identifies the Multiword DMA transfer modes supported by the device and indicates the mode that is currently selected. Only one DMA mode shall be selected at any given time. If an Ultra DMA mode is enabled, then no Multiword DMA mode shall be enabled. If a Multiword DMA mode is enabled then no Ultra DMA mode shall be enabled. Bits (15:11) of word 63 are reserved. If bit 10 of word 63 is set to one, then Multiword DMA mode 2 is selected. If this bit is cleared to zero, then Multiword DMA mode 2 is not selected. If bit 9 is set to one or if bit 8 is set to one, then this bit shall be cleared to zero. If bit 9 of word 63 is set to one, then Multiword DMA mode 1 is selected. If this bit is cleared to zero then Multiword DMA mode 1 is not selected. If bit 10 is set to one or if bit 8 is set to one, then this bit shall be cleared to zero. If bit 8 of word 63 is set to one, then Multiword DMA mode 0 is selected. If this bit is cleared to zero then Multiword DMA mode 0 is not selected. If bit 10 is set to one or if bit 9 is set to one, then this bit shall be cleared to zero. Bits (7:3) of word 63 are reserved. For PATA devices when bit 2 of word 63 is set to one Multiword DMA modes 2 and below are supported. If this bit is cleared to zero, then Multiword DMA mode 2 is not supported. If Multiword DMA mode 2 is supported, then Multiword DMA modes 1 and 0 shall also be supported. If this bit is set to one, bits (1:0) shall be set to one. For SATA devices bit 2 of word 63 shall be set to one. For PATA devices when bit 1 of word 63 is set to one Multiword DMA modes 1 and below are supported. If this bit is cleared to zero, then Multiword DMA mode 1 is not supported. If Multiword DMA mode 1 is supported, then Multiword DMA mode 0 shall also be supported. If this bit is set to one, bit 0 shall be set to one. For SATA devices bit 1 of word 63shall be set to one. For PATA devices when bit 0 of word 63 is set to one Multiword DMA mode 0 is supported. For SATA devices bit 0 of word 63 shall be set to one. 7.16.7.24 Word 64: PIO transfer modes supported For PATA devices bits (7:0) of word 64 is defined as the PIO data and register transfer supported field. If this field is supported, bit 1 of word 53 shall be set to one. This field is bit significant. Any number of bits may be set to one in this field by the device to indicate the PIO modes the device is capable of supporting. Of these bits, bits (7:2) are Reserved for future PIO modes. Bit 0, if set to one, indicates that the device supports PIO mode 3. All devices except CFA and PCMCIA devices shall support PIO mode 3 and shall set bit 0 to one. Bit 1, if set to one, indicates that the device supports PIO mode 4. See ATA8-APT for more information.
103
T13/1699-D Revision 3f For SATA devices bits (1:0) shall be set to one. 7.16.7.25 Word 65: Minimum Multiword DMA transfer cycle time per word
For PATA devices word 65 is defined as the minimum Multiword DMA transfer cycle time per word. This field defines, in nanoseconds, the minimum cycle time that the device supports when performing Multiword DMA transfers on a per word basis. For SATA devices word 65 shall be set to indicate 120ns. If this field is supported, bit 1 of word 53 shall be set to one. Any device that supports Multiword DMA mode 1 or above shall support this field, and the value in word 65 shall not be less than the minimum cycle time for the fastest DMA mode supported by the device. If bit 1 of word 53 is set to one because a device supports a field in words 64-70 other than this field and the device does not support this field, the device shall return a value of zero in this field. 7.16.7.26 Word 66: Device recommended Multiword DMA cycle time For PATA devices word 66 is defined as the device recommended Multiword DMA transfer cycle time. This field defines, in nanoseconds, the minimum cycle time per word during a single logical sector host transfer while performing a multiple logical sector READ DMA or WRITE DMA command for any location on the media under nominal conditions. If a host runs at a faster cycle rate by operating at a cycle time of less than this value, the device may negate DMARQ for flow control. The rate at which DMARQ is negated could result in reduced throughput despite the faster cycle rate. Transfer at this rate does not ensure that flow control is not be used, but implies that higher performance may result. See ATA8-APT for more information. If this field is supported, bit 1 of word 53 shall be set to one. Any device that supports Multiword DMA mode 1 or above shall support this field, and the value in word 66 shall not be less than the value in word 65. If bit 1 of word 53 is set to one because a device supports a field in words 64-70 other than this field and the device does not support this field, the device shall return a value of zero in this field. For SATA devices word 66 shall be set to indicate 120ns. 7.16.7.27 Word 67: Minimum PIO transfer cycle time without IORDY flow control For PATA devices word 67 is defined as the minimum PIO transfer without IORDY flow control cycle time. This field defines, in nanoseconds, the minimum cycle time that, if used by the host, the device guarantees data integrity during the transfer without utilization of IORDY flow control. For SATA devices word 67 shall be set to indicate 120ns. If this field is supported, Bit 1 of word 53 shall be set to one. Any device that supports PIO mode 3 or above shall support this field, and the value in word 67 shall not be less than the value reported in word 68. If bit 1 of word 53 is set to one because a device supports a field in words 64-70 other than this field and the device does not support this field, the device shall return a value of zero in this field. 7.16.7.28 Word 68: Minimum PIO transfer cycle time with IORDY flow control For PATA devices word 68 is defined as the minimum PIO transfer with IORDY flow control cycle time. This field defines, in nanoseconds, the minimum cycle time that the device supports while performing data transfers while utilizing IORDY flow control. For SATA devices word 68 shall be set to indicate 120ns. If this field is supported, Bit 1 of word 53 shall be set to one. All devices except CFA and PCMCIA devices shall support PIO mode 3 and shall support this field, and the value in word 68 shall be the fastest defined PIO mode supported by the device. The maximum value reported in this field shall be 180 to indicate support for PIO mode 3 or above. If bit 1 of word 53 is set to one because a device supports a field in words 64-70 other than this field and the device does not support this field, the device shall return a value of zero in this field.
104
December 11, 2006 7.16.7.29 Words 69-74: Reserved 7.16.7.30 Word 75: Queue depth
T13/1699-D Revision 3f
Bits (4:0) of word 75 indicate the maximum queue depth supported by the device. The queue depth includes all commands for which command acceptance has occurred and command completion has not occurred. The value in this field equals (maximum queue depth - 1), e.g., a value of zero indicates a queue depth of one, a value of 31 indicates a queue depth of 32. If bit 1 of word 83 is cleared to zero indicating that the device does not support READ/WRITE DMA QUEUED commands, the value in this field shall be zero. Support of this word is mandatory if the TCQ feature set is supported. 7.16.7.31 Words 76-79: Reserved for Serial ATA 7.16.7.32 Word 80: Major revision number If not 0000h or FFFFh, the device claims compliance with the major version(s) as indicated by bits (6:3) being set to one. Values other than 0000h and FFFFh are bit significant. Since ATA standards maintain downward compatibility, a device may set more than one bit. 7.16.7.33 Word 81: Minor revision number Table 22 defines the value that shall be reported in word 81 to indicate the revision of the standard that guided the implementation. Table 22 Minor revision number (part 1 of 2) Value 0000h 0001h 0002h 0003h 0004h 0005h 0006h 0007h 0008h 0009h 000Ah 000Bh 000Ch 000Dh 000Eh 000Fh 0010h 0011h 0012h 0013h 0014h 0015h 0016h 0017h 0018h 0019h Minor Revision Minor revision is not reported Obsolete Obsolete Obsolete Obsolete Obsolete Obsolete Obsolete Obsolete Obsolete Obsolete Obsolete Obsolete ATA/ATAPI-4 X3T13 1153D revision 6 ATA/ATAPI-4 T13 1153D revision 13 ATA/ATAPI-4 X3T13 1153D revision 7 ATA/ATAPI-4 T13 1153D revision 18 ATA/ATAPI-4 T13 1153D revision 15 ATA/ATAPI-4 published, ANSI INCITS 317-1998 ATA/ATAPI-5 T13 1321D revision 3 ATA/ATAPI-4 T13 1153D revision 14 ATA/ATAPI-5 T13 1321D revision 1 ATA/ATAPI-5 published, ANSI INCITS 340-2000 ATA/ATAPI-4 T13 1153D revision 17 ATA/ATAPI-6 T13 1410D revision 0 ATA/ATAPI-6 T13 1410D revision 3a
105
T13/1699-D Revision 3f Table 22 Minor revision number (part 2 of 2) Value 001Ah 001Bh 001Ch 001Dh 001Eh 001Fh 0020h 0021h 0022h 0023h-0026h 0027h 0028h-0032h 0033h 0034h-0041h 0042h 0043h-0051h 0052h 0053h-0106h 0107h 0108h-FFFEh FFFFh Minor Revision ATA/ATAPI-7 T13 1532D revision 1 ATA/ATAPI-6 T13 1410D revision 2 ATA/ATAPI-6 T13 1410D revision 1 ATA/ATAPI-7 published ANSI INCITS 397-2005. ATA/ATAPI-7 T13 1532D revision 0 Reserved Reserved ATA/ATAPI-7 T13 1532D revision 4a ATA/ATAPI-6 published, ANSI INCITS 361-2002 Reserved ATA8-ACS revision 3c Reserved ATA8-ACS Revision 3e Reserved ATA8-ACS Revision 3f Reserved ATA8-ACS revision 3b Reserved ATA8-ACS revision 2d Reserved Minor revision is not reported
7.16.7.34 Words 82-84: Features/command sets supported Words 82-84 and 119 shall indicate features/command sets supported. If a defined bit is cleared to zero, the indicated features/command set is not supported. If bit 14 of word 83 is set to one and bit 15 of word 83 is cleared to zero, the contents of words 82-83 contain valid support information. If not, support information is not valid in these words. If bit 14 of word 84 is set to one and bit 15 of word 84 is cleared to zero, the contents of word 84 contains valid support information. If not, support information is not valid in this word. If bit 14 of word 119 is set to one and bit 15 of word 119 is cleared to zero, the contents of word 119 contains valid support information. If not, support information is not valid in this word. If bit 0 of word 82 is set to one, the SMART feature set is supported. If bit 1 of word 82 is set to one, the Security feature set is supported. bit 2 of word 82 is obsolete. If bit 3 of word 82 is set to one, the Power Management feature set is supported. If bit 4 of word 82 is set to one, the PACKET feature set is supported. If bit 5 of word 82 is set to one, write cache is supported. If bit 6 of word 82 is set to one, read look-ahead is supported. If bit 7 of word 82 is set to one, release interrupt is supported. If bit 8 of word 82 is set to one, SERVICE interrupt is supported. If bit 9 of word 82 is set to one, the DEVICE RESET command is supported. If bit 10 of word 82 is set to one, the Host Protected Area feature set is supported. Bit 11 of word 82 is obsolete. If bit 12 of word 82 is set to one, the device supports the WRITE BUFFER command.
106
December 11, 2006 If bit 13 of word 82 is set to one, the device supports the READ BUFFER command. If bit 14 of word 82 is set to one, the device supports the NOP command. Bit 15 of word 82 is obsolete.
T13/1699-D Revision 3f
If bit 0 of word 83 is set to one, the device supports the DOWNLOAD MICROCODE command. If bit 1 of word 83 is set to one, the device supports the READ DMA QUEUED and WRITE DMA QUEUED commands. If bit 2 of word 83 is set to one, the device supports the CFA feature set. If bit 3 of word 83 is set to one, the device supports the Advanced Power Management feature set. bit 4 of word 83 is obsolete. If bit 5 of word 83 is set to one, the device supports the Power-Up In Standby feature set. If bit 6 of word 83 is set to one, the device requires the SET FEATURES subcommand to spin-up after power-up if the Power-Up In Standby feature set is enabled (see 7.47.8). Bit 7 is defined in Address Offset Reserved Area Boot, INCITS TR27:2001. If bit 8 of word 83 is set to one, the device supports the SET MAX security extension. If bit 9 of word 83 is set to one, the device supports the Automatic Acoustic Management feature set. If bit 10 of word 83 is set to one, the 48-bit Address feature set is supported. If bit 11 of word 83 is set to one, the device supports the Device Configuration Overlay feature set. Bit 12 of word 83 shall be set to one indicating the device supports the mandatory FLUSH CACHE command. If bit 13 of word 83 is set to one, the device supports the FLUSH CACHE EXT command. If bit 0 of word 84 is set to one, the device supports SMART error logging. If bit 1 of word 84 is set to one, the device supports SMART self-test. If bit 2 of word 84 is set to one, the device supports the media serial number field words 176-205. If bit 3 of word 84 is set to one, the device supports the Media Card Pass Through Command feature set. If bit 4 of word 84 is set to one, the device supports the Streaming feature set. If bit 5 of word 84 is set to one, the device supports the General Purpose Logging feature set. If bit 6 of word 84 is set to one, the device supports the WRITE DMA FUA EXT and WRITE MULTIPLE FUA EXT commands. If bit 7 of word 84 is set to one, the device supports the WRITE DMA QUEUED FUA EXT command. If bit 8 of word 84 is set to one, the device supports a world wide name. Bit 11 of word 84 is reserved for INCITS TR-37-2004 (TLC) Bit 12 of word 84 is reserved for INCITS TR-37-2004 (TLC) If bit 13 of word 84 is set to one, the device supports IDLE IMMEDIATE with UNLOAD FEATURE. Bit 0 of word 119 is reserved for technical report DT1825. If bit 1 of word 119 is set to one, the device supports the Write-Read-Verify feature set If bit 2 of word 119 is set to one, the device supports the WRITE UNCORRECTAB LE command If bit 3 of word 119 is set to one, READ and WRITE DMA EXT GPL optional commands are supported if bit 4 of word 119 is set to one, the Segmented feature for DOWNLOAD MICROCODE is supported 7.16.7.35 Words 85-87: Features/command sets enabled Words 85-87 and 120 shall indicate features/command sets enabled. If a defined bit is cleared to zero, the indicated features/command set is not enabled. If a supported features/command set is supported and cannot Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) 107
T13/1699-D Revision 3f
be disabled, it is defined as supported and the bit shall be set to one. If bit 14 of word 87 is set to one and bit 15 of word 87 is cleared to zero, the contents of words 85-87 contain valid information. If bit 14 of word 120 is set to one and bit 15 of word 120 is cleared to zero, the contents of word 120 contain valid information. If not, information is not valid in these words. If bit 0 of word 85 is set to one, the SMART feature set has been enabled via the SMART ENABLE OPERATIONS command. If bit 0 of word 85 is cleared to zero, the SMART feature set has been disabled via the SMART DISABLE OPERATIONS command. If bit 1 of word 85 is set to one, then Security has been enabled by setting a User password via the SECURITY SET PASSWORD command. If bit 1 of word 85 is cleared to zero, there is no valid User password. If the Security feature set is not supported, this bit shall be cleared to zero. bit 2 of word 85 is obsolete. Bit 3 of word 85 shall be set to one indicating the mandatory Power Management feature set is supported. Bit 4 of word 85 shall be cleared to zero to indicate that the PACKET feature set is not supported. If bit 5 of word 85 is set to one, write cache has been enabled via the SET FEATURES command (see 7.47.4). If bit 5 of word 85 is cleared to zero, write cache has been disabled via the SET FEATURES command. If bit 6 of word 85 is set to one, read look-ahead has been enabled via the SET FEATURES command (see 7.47.13). If bit 6 of word 85 is cleared to zero, look-ahead has been disabled via the SET FEATURES command. If bit 7 of word 85 is set to one, release interrupt has been enabled via the SET FEATURES command (see 7.47.14). If bit 7 of word 85 is cleared to zero, release interrupt has been disabled via the SET FEATURES command. If bit 8 of word 85 is set to one, SERVICE interrupt has been enabled via the SET FEATURES command (see 7.47.15). If bit 8 of word 85 is cleared to zero, SERVICE interrupt has been disabled via the SET FEATURES command. If bit 9 of word 85 is set to one, the DEVICE RESET command is supported. If the device is not indicating its full size as defined by READ NATIVE MAX or READ NATIVE MAX EXT command because a SET MAX ADDESS or SET MAX ADDRESS EXT command has been issued to resize the device, then bit 10 of word 85 shall be set to one indicating that a Host Protected Area has been established (i.e., HPA enabled). If the device is indicating its full size as defined by READ NATIVE MAX or READ NATIVE MAX EXT command then bit 10 of word 85 shall be cleared to zero indicating that a Host Protected Area has not been established (i.e., HPA disabled). Bit 11 of word 85 is obsolete. If bit 12 of word 85 is set to one, the device supports the WRITE BUFFER command. If bit 13 of word 85 is set to one, the device supports the READ BUFFER command. If bit 14 of word 85 is set to one, the device supports the NOP command. Bit 15 of word 85 is obsolete. If bit 0 of word 86 is set to one, the device supports the DOWNLOAD MICROCODE command. If bit 1 of word 86 is set to one, the device supports the READ DMA QUEUED and WRITE DMA QUEUED commands. If bit 2 of word 86 is set to one, the device supports the CFA feature set. If bit 3 of word 86 is set to one, the Advanced Power Management feature set has been enabled via the SET FEATURES command. If bit 3 of word 86 is cleared to zero, the Advanced Power Management feature set has been disabled via the SET FEATURES command. If bit 4 of word 86 is obsolete. If bit 5 of word 86 is set to one, the Power-Up In Standby feature set has been enabled via the SET FEATURES command (see 7.47.7). If bit 5 of word 86 is cleared to zero, the Power-Up In Standby feature set has been disabled via the SET FEATURES command 108 Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS)
T13/1699-D Revision 3f
If bit 6 of word 86 is set to one, the device requires the SET FEATURES subcommand to spin-up after power-up (see 7.47.8). Bit 7 of word 86 is defined in Address Offset Reserved Area Boot, INCITS TR27:2001. If bit 8 of word 86 is set to one, the device has had the SET MAX security extension enabled via a SET MAX SET PASSWORD command. If bit 9 of word 86 is set to one, the device has had the Automatic Acoustic Management feature set enabled via a SET FEATURES command and the value in word 94 is valid. If bit 10 of word 86 is set to one, the 48-bit Address feature set is supported. If bit 11 of word 86 is set to one, the device supports the Device Configuration Overlay feature set. Bit 12 of word 86 shall be set to one indicating the device supports the mandatory FLUSH CACHE command. If bit 13 of word 86 is set to one, the device supports the FLUSH CACHE EXT command. If bit 0 of word 87 is set to one, the device supports SMART error logging. If bit 1 of word 87 is set to one, the device supports SMART self-test. If bit 2 of word 87 is set to one, the media serial number field in words 176-205 is valid. This bit shall be cleared to zero if the media does not contain a valid serial number or if no media is present. If bit 3 of word 87 is set to one, the Media Card Pass Through feature set has been enabled. If bit 5 of word 87 is set to one, the device supports the General Purpose Logging feature set. If bit 6 of word 87 is set to one, the device supports the WRITE DMA FUA EXT and WRITE MULTIPLE FUA EXT commands. If bit 7 of word 87 is set to one, the device supports the WRITE DMA QUEUED FUA EXT command. If bit 8 of word 87 is set to one, the device supports a world wide name. Bit 11 of word 87 is reserved for technical report. Bit 12 of word 87 is reserved for technical report. If bit 13 of word 87 is set to one, the device supports IDLE IMMEDIATE with UNLOAD FEATURE. Bit 0 of word 120 is reserved for technical report If bit 1 of word 120 is set to one then the Write-Read-Verify feature set is enabled If bit 2 of word 120 is set to one then the WRITE UNCORRECTABLE command is supported If bit 3 of word 120 is set to one, READ and WRITE DMA EXT GPL optional commands are supported if bit 4 of word 120 is set to one, the Segmented feature for DOWNLOAD MICROCODE is supported 7.16.7.36 Word 88: Ultra DMA modes Word 88 identifies the Ultra DMA transfer modes supported by the device and indicates the mode that is currently selected. Only one DMA mode shall be selected at any given time. If an Ultra DMA mode is selected, then no Multiword DMA mode shall be selected. If a Multiword DMA mode is selected, then no Ultra DMA mode shall be selected. Support of this word is mandatory if Ultra DMA is supported. Bit (15) of word 88 is reserved. If bit 14 of word 88 is set to one, then Ultra DMA mode 6 is selected. If this bit is cleared to zero, then Ultra DMA mode 6 is not selected. If bit 13 or bit 12 or bit 11 or bit 10 or bit 9 or bit 8 is set to one, then this bit shall be cleared to zero. If bit 13 of word 88 is set to one, then Ultra DMA mode 5 is selected. If this bit is cleared to zero, then Ultra DMA mode 5 is not selected. If bit 12 or bit 11 or bit 10 or bit 9 or bit 8 is set to one, then this bit shall be cleared to zero.
109
T13/1699-D Revision 3f
If bit 12 of word 88 is set to one, then Ultra DMA mode 4 is selected. If this bit is cleared to zero, then Ultra DMA mode 4 is not selected. If bit 13 or 11 or bit 10 or bit 9 or bit 8 is set to one, then this bit shall be cleared to zero. If bit 11 of word 88 is set to one, then Ultra DMA mode 3 is selected. If this bit is cleared to zero, then Ultra DMA mode 3 is not selected. If bit 13 or 12 or bit 10 or bit 9 or bit 8 is set to one, then this bit shall be cleared to zero. If bit 10 of word 88 is set to one, then Ultra DMA mode 2 is selected. If this bit is cleared to zero, then Ultra DMA mode 2 is not selected. If bit 13 or 12 or bit 11 or bit 9 or bit 8 is set to one, then this bit shall be cleared to zero. If bit 9 of word 88 is set to one, then Ultra DMA mode 1 is selected. If this bit is cleared to zero then Ultra DMA mode 1 is not selected. If bit 13 or 12 or bit 11 or bit 10 or bit 8 is set to one, then this bit shall be cleared to zero. If bit 8 of word 88 is set to one, then Ultra DMA mode 0 is selected. If this bit is cleared to zero then Ultra DMA mode 0 is not selected. If bit 13 or 12 or bit 11 or bit 10 or bit 9 is set to one, then this bit shall be cleared to zero. Bit (7) of word 88 are reserved. For PATA devices when bit 6 of word 88 is set to one Ultra DMA modes 6 and below are supported. If this bit is cleared to zero, then Ultra DMA mode 6 is not supported. If Ultra DMA mode 6 is supported, then Ultra DMA modes 5, 4, 3, 2, 1 and 0 shall also be supported. If this bit is set to one, then bits (5:0) shall be set to one. For SATA devices bit 6 of word 88 shall be set to one. For PATA devices when bit 5 of word 88 is set to one Ultra DMA modes 5 and below are supported. If this bit is cleared to zero, then Ultra DMA mode 5 is not supported. If Ultra DMA mode 5 is supported, then Ultra DMA modes 4, 3, 2, 1 and 0 shall also be supported. If this bit is set to one, then bits (4:0) shall be set to one. For SATA devices bit 5 of word 88 shall be set to one. For PATA devices when bit 4 of word 88 is set to one Ultra DMA modes 4 and below are supported. If this bit is cleared to zero, then Ultra DMA mode 4 is not supported. If Ultra DMA mode 4 is supported, then Ultra DMA modes 3, 2, 1 and 0 shall also be supported. If this bit is set to one, then bits (3:0) shall be set to one. For SATA devices bit 4 of word 88 shall be set to one. For PATA devices when bit 3 of word 88 is set to one Ultra DMA modes 3 and below are supported. If this bit is cleared to zero, then Ultra DMA mode 3 is not supported. If Ultra DMA mode 3 is supported, then Ultra DMA modes 2, 1 and 0 shall also be supported. If this bit is set to one, then bits (2:0) shall be set to one. For SATA devices bit 3 of word 88 shall be set to one. For PATA devices when bit 2 of word 88 is set to one Ultra DMA modes 2 and below are supported. If this bit is cleared to zero, then Ultra DMA mode 2 is not supported. If Ultra DMA mode 2 is supported, then Ultra DMA modes 1 and 0 shall also be supported. If this bit is set to one, bits (1:0) shall be set to one. For SATA devices bit 2 of word 88 shall be set to one. For PATA devices when bit 1 of word 88 is set to one Ultra DMA modes 1 and below are supported. If this bit is cleared to zero, then Ultra DMA mode 1 is not supported. If Ultra DMA mode 1 is supported, then Ultra DMA mode 0 shall also be supported. If this bit is set to one, bit 0 shall be set to one. For SATA devices bit 1 of word 88 shall be set to one. For PATA devices when bit 0 of word 88 is set to one Ultra DMA mode 0 is supported. If this bit is cleared to zero, then Ultra DMA is not supported. For SATA devices bit 0 of word 88 shall be set to one.
110
December 11, 2006 7.16.7.37 Word 89: Time required for Security erase unit completion
T13/1699-D Revision 3f
Word 89 specifies the estimated time required for the SECURITY ERASE UNIT command to complete its normal mode erasure. Support of this word is mandatory if the Security feature set is supported. If the Security feature set is not supported, this word shall be cleared to zero. Value 0 1-254 255 Time Value not specified (Value*2) minutes >508 minutes
7.16.7.38 Word 90: Time required for Enhanced security erase unit completion Word 90 specifies the estimated time required for the SECURITY ERASE UNIT command to complete its enhanced mode erasure. Support of this word is mandatory if support of the Security feature set is supported. If the Security feature set is not supported, this word shall be cleared to zero. Value 0 1-254 255 Time Value not specified (Value*2) minutes >508 minutes
7.16.7.39 Word 91: Advanced power management level value Bits (7:0) of word 91 contain the current Advanced Power Management level setting. Support of this word is mandatory if advanced power management is supported. 7.16.7.40 Word 92: Master Password Identifier If either the Security feature set or the Master Password Identifier feature are not supported, word 92 shall contain the value 0000h or FFFFh. If the Security feature set and the Master Password Identifier feature are supported, word 92 contains the value of the Master Password Identifier set when the Master Password was last changed. 7.16.7.41 Word 93: Hardware configuration test results For PATA devices when bit 14 of word 93 is set to one and bit 15 of word 93 is cleared to zero the content of word 93 contains valid information. During processing of a hardware reset, Device 0 shall set bits (12:8) of this word to zero and and shall set bits (7:0) of this word as indicated to show the result of the hardware reset. During processing of a hardware reset, Device 1 shall clear bits (7:0) of this word to zero and and shall set bits (12:8) of the word as indicated to show the result of the hardware reset. Support of bits (15:13) is mandatory. Support of bits (12:0) is optional. Bit 13 shall be set or cleared by the selected device to indicate whether the device detected CBLID- above VIH or below VIL at any time during execution of each IDENTIFY DEVICE command after receiving the command from the host but before returning data to the host. This test may be repeated as desired by the device during command execution (See ATA8-APT).
B B B B
For SATA devices word 93 shall be set to the value 0000h. 7.16.7.42 Word 94: Current automatic acoustic management value Bits (15:8) contain the device vendors recommended acoustic management level (see table 37 for an enumeration of all of the possible acoustic management levels). If the host desires the drive to perform with highest performance, it should set the automatic acoustic management level to FEh. If the OEM host desires the vendors recommended acoustic management level as defined by the devices vendor, the host should set the automatic acoustic management level to the value returned to the host in these 8 bits. The use of this setting may not provide the lowest acoustics, or the best trade-off of acoustics and performance, in all configurations. Support of this word is mandatory if the Acoustic Management feature set is supported. Bits (7:0) contain the current automatic acoustic management level. If the Automatic Acoustic Management feature set is supported by the device, but the level has not been set by the host, this byte shall contain the
111
T13/1699-D Revision 3f
drives default setting. If the Automatic Acoustic Management feature set is not supported by the device, the value of this byte shall be zero. 7.16.7.43 Word 95: Stream Minimum Request Size Number of logical sectors that provides optimum performance in a streaming environment. This number shall be a power of two, with a minimum of eight logical sectors (4096 bytes). The starting LBA value for each streaming command should be evenly divisible by this request size. 7.16.7.44 Word 96: Streaming Transfer Time - DMA Word 96 defines the Streaming Transfer Time for DMA mode. The worst-case sustainable transfer time per logical sector for the device is calculated as follows: Streaming Transfer Time = (word 96) * (Streaming Performance Granularity / 65536) The content of word 96 may be affected by the host issuing a SET FEATURES subcommand 43h (Typical Host Interface Sector Time for DMA mode). Because of this effect, an IDENTIFY DEVICE command shall be issued after a SET FEATURES command that may affect these words. If the Streaming feature set is not supported by the device, the content of word 96 shall be zero. 7.16.7.45 Word 97: Streaming Access Latency - DMA and PIO Word 97 defines the Streaming Access Latency for DMA and PIO mode. The worst-case access latency of the device for a streaming command is calculated as follows: Access Latency = (word 97) * (Streaming Performance Granularity / 256) The content of word 97 may be affected by the host issuing a SET FEATURES subcommand 42h or C2h (Automatic Acoustic Management). Because of this effect, an IDENTIFY DEVICE command shall be issued after a SET FEATURES command that may affect these words. If the Streaming feature set is not supported by the device, the content of word 97 shall be zero. 7.16.7.46 Words 98-99: Streaming Performance Granularity These words define the fixed unit of time that is used in IDENTIFY DEVICE data words 96-97 and 104, and SET FEATURES subcommand 43h, and in the Streaming Performance Parameters log, which is accessed by use of the READ LOG EXT command, and in the Command Completion Time Limit that is passed in streaming commands. The unit of time for this parameter shall be in microseconds, e.g., a value of 10000 indicates 10 milliseconds. If yy was returned by the drive for this parameter, then a) the Command Completion Time Limit in the Feature field for a streaming command shall be yy microseconds. b) the Streaming Transfer Time shall be ( (word 96) * (yy/65536) ) microseconds, ( (word 104) * (yy / 5536) ) microseconds, or ( (a Sector Time array entry in the Streaming Performance Parameters log) * (yy/65536) ) microseconds. c) The Streaming Access Latency shall be ( (word 97) * (yy/256) ) microseconds, or ( (an Access Time array entries in the Streaming Performance Parameters log) * (yy / 256) ) microsecon ds. d) taking these units into account, the host may calculate the estimated time for a streaming command of size S logical sectors as ( (word 96 * S / 65536) + (word 97 / 256) ) * yy microseconds for DMA mode. e) taking these units into account, the host may calculate the estimated time for a streaming command of size S logical sectors as ( (word 104 * S / 65536) + (word 97 / 256) ) * yy microseconds for PIO mode. The value of the Streaming Performance Granularity is vendor specific and fixed for a device. 7.16.7.47 Words 100-103: Total Number of User Addressable Sectors for the 48-bit Address feature set Words 100-103 contain a value that is one greater than the maximum LBA in user accessible space when the 48-bit Addressing feature set is supported. The maximum value that shall be placed in this field is 0000_FFFF_FFFF_FFFFh. Support of these words is mandatory if the 48-bit Address feature set is supported.
112
December 11, 2006 7.16.7.48 Word 104: Streaming Transfer Time - PIO
T13/1699-D Revision 3f
Word 104 defines the Streaming Transfer Time for PIO mode. The worst-case sustainable transfer time per logical sector for the device is calculated as follows: Streaming Transfer Time = (word 104) * (Streaming Performance Granularity / 65536) The content of word 104 may be affected by the host issuing a SET FEATURES subcommand 43h (Typical Host Interface Sector Time for PIO mode). Because of this effect, an IDENTIFY DEVICE command shall be issued after a SET FEATURES command that may affect these words. If the Streaming feature set is not supported by the device, the content of word 104 shall be zero. 7.16.7.49 Word 106: Physical sector size / Logical Sector Size If bit 14 of word 106 is set to one and bit 15 of word 106 is cleared to zero, the contents of word 106 contain valid information. If not, information is not valid in this word. Bit 13 of word 106 shall be set to one to indicate that the device has more than one logical sector per physical sector. Bit 12 of word 106 shall be set to 1 to indicate that the device has been formatted with a logical sector size larger than 256 words. Bit 12 of word 106 shall be cleared to 0 to indicate that words 117-118 are invalid and that the logical sector size is 256 words. Bits (11:4) of word 106 are reserved. Bits (3:0) of word 106 indicate the size of the device physical sectors in power of two logical sectors. Examples: Bits (3:0): 0 = 20 = 1 logical sector per physical sector Bits (3:0): 1 = 21 = 2 logical sector per physical sector Bits (3:0): 2 = 22 = 4 logical sector per physical sector Bits (3:0): 3 = 23 = 8 logical sector per physical sector
P P P P P P P P
7.16.7.50 Word 107: Inter-seek delay for ISO 7779 standard acoustic testing Word 107 is defined as the manufacturers recommended time delay between seeks during ISO-7779 standard acoustic testing in microseconds (ISO 7779 value tD. See ISO 7779:1999 (E), subclause C.9 Equipment Category: Disk units and storage subsystems).
B
7.16.7.51 Words 108-111: World wide name Words 111-108 shall contain the mandatory value of the world wide name (WWN) for the device. Word 108 bits 15-12 shall contain 5h, indicating that the naming authority is IEEE. All other values are reserved. Words 108 bits 11-0 and word 109 bits (15:4) shall contain the Organization Unique Identifier (OUI) for the device manufacturer. The OUI shall be assigned by the IEEE/RAC as specified by ISO/IEC 13213:1994. The identifier may be obtained from: Institute of Electrical and Electronic Engineers, Inc. Registration Authority Committee 445 Hoes Lane Piscataway, NJ 08855-1331 Word 109 bits (3:0), word 110, and word 111 shall contain a value assigned by the vendor that is unique for the device in the OUI domain. 7.16.7.52 Words 112-115: Reserved for a 128-bit world wide name 7.16.7.53 Word 116: Reserved for TLC technical report This field is described in Time-Limited Commands (TLC) INCITS TR-37-2004
113
Words 117,118 indicate the size of device logical sectors in words. The value of words 117,118 shall be equal to or greater than 256. The value in words 117,118 shall be valid when word 106 bit 12 is set to 1. All logical sectors on a device shall be 117,118 words long. 7.16.7.55 Words 121-126: Reserved 7.16.7.56 Word 127: Obsolete 7.16.7.57 Word 128: Security status Support of this word is mandatory if the Security feature set is supported. If the Security feature set is not supported, this word shall be cleared to zero. Bit 8 of word 128 indicates the Master Password Capability. If security is enabled and the Master Password Capability is high, bit 8 shall be cleared to zero. If security is enabled and the Master Password Capability is maximum, bit 8 shall be set to one. When security is disabled, bit 8 shall be cleared to zero. Bit 5 of word 128 set to one indicates that the enhanced mode of the SECURITY ERASE UNIT command is supported. Bit 4 of word 128 set to one indicates that the password attempt counter has decremented to zero. This is also known as the "Password Attempt Counter Exceeded" bit. Bit 3 of word 128 set to one indicates that security is frozen. Bit 2 of word 128 set to one indicates that security is locked. Bit 1 of word 128 set to one indicates that security is enabled. This is a copy of word 85, bit 1. Bit 0 of word 128 set to one indicates that the Security feature set is supported. This is a copy of word 82, bit 1. 7.16.7.58 Words 129-159: Vendor specific 7.16.7.59 Word 160: CFA power mode Word 160 indicates the presence and status of a CFA feature set device that supports CFA Power Mode 1. Support of this word is mandatory if CFA Power Mode 1 is supported. If bit 13 of word 160 is set to one then the device shall be in CFA Power Mode 1 to perform one or more commands implemented by the device. If bit 12 of word 160 is set to one the device is in CFA Power Mode 0 (see 7.47.9). Bits (11:0) indicate the maximum average RMS current in Milliamperes required during 3.3V or 5V device operation in CFA Power Mode 1. 7.16.7.60 Words 161-175: Reserved for assignment by the CompactFlash Association 7.16.7.61 Words 176-205: Current media serial number Words (205:176) contain the current media serial number. Serial numbers shall consist of 60 bytes. The first 40 bytes shall indicate the media serial number and the remaining 20 bytes shall indicate the media manufacturer. For removable ATA devices (e.g., flash media with native ATA interfaces) that do not support removable media, the first 20 words of this field shall be the same as words IDENTIFY DEVICE data words (46:27) and the next ten words shall be the same as words IDENTIFY DEVICE data words (19:10). 7.16.7.62 Word 206: SCT Command Transport Bits 15:12 indicate support for vendor specific action codes. Bits 11:6 of word 206 are reserved If bit 5 of word 206 is set to one the device supports SCT Data Tables (see 8.3.6).
114
December 11, 2006 If bit 4 of word 206 is set to one the device supports SCT Features Control (see 8.3.5).
T13/1699-D Revision 3f
If bit 3 of word 206 is set to one the device supports SCT Error Recovery Control (see 8.3.4). If bit 2 of word 206 is set to one the device supports SCT Write Same (see 8.3.3). If bit 1 of word 206 is set to one the device supports SCT Long Sector Access (see 8.3.2). If bit 0 of word 206 is set to one the device supports the SCT Command Transport including SCT Read Status (see clause 8). 7.16.7.63 Word 209: Alignment of logical blocks within a physical block Word 209 shall report the location of LBA0 within the first physical sector of the media. See Annex C for more information. 7.16.7.64 Words 210-211: Write-Read-Verify Sector Count Mode 3 Only Words 210-211 shall indicate the number of logical sectors to be verified after every spin-up, as set by the SET FEATURES command for the Enable Write-Read-Verify subcommand. This count only applies to mode 3. 7.16.7.65 Words 212-213: Verify Sector Count Mode 2 Only Words 212-213 shall indicate the number of logical sectors to be verified after every spin-up, as set by the SET FEATURES command for the Enable Write-Read-Verify subcommand. This count only applies to mode 2. 7.16.7.66 Word 214: NV Cache Capabilities Both the NV Cache Power Mode feature set version (word 214 bits 8-11) and the NV Cache feature set version (word 214 bits 12-15) shall be set to 0. If bit 0 of word 214 is set to 1, the device supports the power modes of the NV Cache feature set. Bits 8 to 11 specify the version of the NV Cache Modes supported. If bit 4 of word 214 is set to 1, the device supports the commands of the NV Cache feature set. Bits 12 to 15 specify the version of the NV Cache Commands supported. 7.16.7.67 Words 215-216: NV Cache Size in Logical Blocks (MSW) Words 215 and 216 specify the maximum number of logical sectors that the device's NV Cache Set can contain for the host to pin. 7.16.7.68 Word 217: NV Cache Read Transfer Speed in MB/s Word 217 specifies the maximum sustained transfer speed of the device's NV Cache during a read operation in megabytes per second. 7.16.7.69 Word 218: NV Cache Write Transfer Speed in MB/s Word 218 specifies the maximum sustained transfer speed of the device's NV Cache during a Write in megabytes per second. 7.16.7.70 Word 219: NV Cache Options Word 219 bits 0-7 specify a value which is the device's estimate of the amount of time it takes to be able to satisfy a read or write request from its rotational media when the read or write request is received while the rotational media is not spinning. 7.16.7.71 Word 220: Write-Read-Verify Mode Word 220 contains the current mode of the Write-Read-Verify feature set, as set by the SET FEATURES Enable/Disable Write-Read-Verify subcommand. See 7.47.10 for more information on setting Write-Read-Verify mode. Bits 15:8 reserved Bits 7:0 current mode of the Write-Read-Verify feature set
115
T13/1699-D Revision 3f 7.16.7.72 Word 221: Reserved 7.16.7.73 Word 222: Transport major revision number
If not FFFFh, the device claims compliance with the Transport Standard major version(s) as indicated by bits (6:3) being set to one. Values other than 0000h and FFFFh are bit significant. Since ATA standards maintain downward compatibility, a device may set more than one bit. 7.16.7.74 Word 223: Transport minor revision number Table 23 defines the value that shall be reported in word 223 to indicate the revision of the standard that guided the implementation. Table 23 Transport minor version number Value 0000h 0001h-0020h 0021h 0022h-FFFEh FFFFh 7.16.7.75 Words 213-254: Reserved 7.16.7.76 Word 255: Integrity word The use of this word is optional. If bits (7:0) of this word contain the signature A5h, bits (15:8) contain the data structure checksum. The data structure checksum is the twos complement of the sum of all bytes in words 0-254 and the byte consisting of bits (7:0) in word 255. Each byte shall be added with unsigned arithmetic, and overflow shall be ignored. The sum of all 512 bytes is zero when the checksum is correct. Minor Revision Minor revision not reported Reserved ATA8-AST T13 Project D1697 Revision 0b Reserved Minor version not reported
116
T13/1699-D Revision 3f
7:0 A1h
7.17.4 Normal Outputs See table 79. 7.17.5 Error Outputs The device shall return command aborted if the device does not implement this command, otherwise, the device shall not report an error. See table 100. The device may return error status if an Interface CRC error has occurred. NOTE 6 There is no defined mechanism for a device to return an ICRC error status that may have occurred during the last data block of a PIO-in data transfer; there may be other mechanisms in which a host may verify that an Interface CRC error occurred in these cases.
117
T13/1699-D Revision 3f 7.17.6 Input Data 7.17.6.1 Overview Table 24 IDENTIFY PACKET DEVICE data (part 1 of 8) Word 0 O M M S P B F V F F F F F F
F V F
B M M M M B B B
F V F F F F F F F F F F F F F F X
P P P P
50
O F F F X B F
Description General configuration bit-significant information: 15:14 10 = ATAPI device 11 = Reserved 13 Reserved 12:8 Field indicates command packet set used by device 7 1 = removable media device 6:5 00 = Device shall set DRQ to one within 3 ms of receiving PACKET command. 01 = Obsolete. 10 = Device shall set DRQ to one within 50 s of receiving PACKET command. 11 = Reserved 4:3 Reserved 2 Incomplete response 1:0 00 = 12 byte command packet 01 = 16 byte command packet 1x = Reserved Reserved Specific configuration Reserved Serial number (20 ASCII characters) Reserved Firmware revision (8 ASCII characters) Model number (40 ASCII characters) Reserved Capabilities 15 Obsolete 14 Obsolete 13 Obsolete 12 1 = Obsolete 11 1 = IORDY supported 10 1 = IORDY may be disabled 9 Shall be set to one. 8 1 = DMA supported. Devices which require the DMADIR bit in the Packet command shall clear this bit to 0 7:0 Vendor specific Capabilities 15 Shall be cleared to zero. 14 Shall be set to one. 13:2 Reserved 1 Obsolete 0 Shall be set to one to indicate a device specific Standby timer value minimum.
118
December 11, 2006 Table 24 IDENTIFY PACKET DEVICE data (part 2 of 8) Word 51-52 53 O M M B B 54-61 62 S P F V X F F F X F F F F F F F F F F F F F F F V V V F F F F 64 65 66 67 68 M P M P M P M P M P 69-70 71-72 73-74 75 O O F F F F F F F F F
T13/1699-D Revision 3f
P P P P P P P P P P P 63 M P P P P P P P
Description Obsolete 15:3 Reserved 2 1 = the fields reported in word 88 are valid 1 1 = the fields reported in words (70:64) are valid 0 Obsolete Reserved 15 1 = DMADIR bit in the Packet command is required for DMA transfers 0 = DMADIR bit in Packet command is not required for DMA transfers. 14:11 Reserved 10 1 = DMA is supported 9 1 = Multiword DMA mode 2 is supported 8 1 = Multiword DMA mode 1 is supported 7 1 = Multiword DMA mode 0 is supported 6 1 = Ultra DMA mode 6 and below are supported 5 1 = Ultra DMA mode 5 and below are supported 4 1 = Ultra DMA mode 4 and below are supported 3 1 = Ultra DMA mode 3 and below are supported 2 1 = Ultra DMA mode 2 and below are supported 1 1 = Ultra DMA mode 1 and below are supported 0 1 = Ultra DMA mode 0 is supported 15:11 Reserved 10 1 = Multiword DMA mode 2 is selected 9 1 = Multiword DMA mode 1 is selected 8 1 = Multiword DMA mode 0 is selected 7:3 Reserved 2 1 = Multiword DMA mode 2 and below are supported. Devices which require the DMADIR bit in the Packet command shall clear this bit to 0. 1 1 = Multiword DMA mode 1 and below are supported. Devices which require the DMADIR bit in the Packet command shall clear this bit to 0. 0 1 = Multiword DMA mode 0 is supported Multiword DMA mode selected Devices which require the DMADIR bit in the Packet command shall clear this bit to 0. 15:8 Reserved 7:0 PIO transfer modes supported Minimum Multiword DMA transfer cycle time per word 15:0 Cycle time in nanoseconds Manufacturers recommended Multiword DMA transfer cycle time 15:0 Cycle time in nanoseconds Minimum PIO transfer cycle time without flow control 15:0 Cycle time in nanoseconds Minimum PIO transfer cycle time with IORDY flow control 15:0 Cycle time in nanoseconds Reserved Obsolete Reserved Obsolete
119
T13/1699-D Revision 3f Table 24 IDENTIFY PACKET DEVICE data (part 3 of 8) Word 76-79 80 O M M S P S B F V R
F F F F F F F X X F 81 M B
82
M X F F F X F F F F F F F F F F F
Description Reserved for Serial ATA Major version number 0000h or FFFFh = device does not report version 15:9 Reserved 8 1 = supports ATA8-ACS 7 1 = Supports ATA/ATAPI-7 6 1 = supports ATA/ATAPI-6 5 1 = supports ATA/ATAPI-5 4 1 = supports ATA/ATAPI-4 3 Obsolete 2 Obsolete 1 Obsolete 0 Reserved Minor version number 0000h or FFFFh = device does not report version 0001h-FFFEh=See 7.16.7.33 Feature sets/commands supported. If words (83:82) = 0000h or FFFFh feature set/command support notification not supported. 15 Obsolete 14 Shall be set to one to indicate that the NOP command is supported 13 Shall be cleared to zero to indicate that the READ BUFFER command is not supported 12 Shall be cleared to zero to indicate that the WRITE BUFFER command is not supported 11 Obsolete 10 Shall be cleared to zero to indicate that the Host Protected Area feature set is not supported 9 Shall be set to one to indicate that the DEVICE RESET command is supported 8 Obsolete 7 Obsolete 6 1 = read look-ahead supported 5 1 = write cache supported 4 Shall be set to one indicating the PACKET feature set is supported. 3 1 = Power Management feature set supported 2 Obsolete 1 1 = Security Mode feature set supported 0 Shall be cleared to zero to indicate that the SMART feature set is not supported
120
December 11, 2006 Table 24 IDENTIFY PACKET DEVICE data (part 4 of 8) Word 83 O M M S P F V
T13/1699-D Revision 3f
F F F F F F F F F F F F F F 84 M
F F
Description Feature sets/commands supported. If words (83:82) = 0000h or FFFFh feature set/command support notification not supported. 15 Shall be cleared to zero 14 Shall be set to one 13 Reserved 12 1 = FLUSH CACHE command supported 11 1 = Device Configuration Overlay feature set supported 10 Reserved 9 1 = AUTOMATIC Acoustic Management feature set supported 8 1 = SET MAX security extension supported 7 See Address Offset Reserved Area Boot, INCITS TR27:2001 6 1 = SET FEATURES subcommand required to spin-up after power-up 5 1 = Power-Up In Standby feature set supported 4 Obsolete 3:1 Reserved 0 Shall be cleared to zero to indicate that the DOWNLOAD MICROCODE command is not supported Feature set/commans supported extension. If words 82, 83, and 84 = 0000h or FFFFh then the feature set/command support notification extension is not supported. 15 Shall be cleared to zero 14 Shall be set to one 13:6 Reserved 5 General Purpose Logging feature set 4:0 Reserved
121
X F F F X V F V V V V F F V V V 86 M F V F F V V V F V V F F 87 M F F
Description Feature sets/commands enabled. If words (87:85) = 0000h or FFFFh feature set/command enabled notification not supported. 15 Obsolete 14 Shall be set to one to indicate that the NOP command is supported 13 Shall be cleared to zero to indicate that the READ BUFFER command is not supported 12 Shall be cleared to zero to indicate that the WRITE BUFFER command is not supported 11 Obsolete 10 Shall be cleared to zero to indicate that the Host Protected Area feature set is not supported 9 Shall be set to one to indicate that the DEVICE RESET command is supported 8 Obsolete 7 Obsolete 6 1 = look-ahead enabled 5 1 = write cache enabled 4 Shall be set to one indicating the PACKET feature set is supported. 3 1 = Power Management feature set enabled 2 Obsolete 1 1 = Security Mode feature set enabled 0 Shall be cleared to zero to indicate that the SMART feature set is not supported Feature sets/commands enabled. If words (87:85) = 0000h or FFFFh feature set/command enabled notification not supported. 15:13 Reserved 12 1 = FLUSH CACHE command supported 11 1 = Device Configuration Overlay feature set supported 10 Reserved 9 1 = Automatic Acoustic Management feature set enabled 8 1 = SET MAX security extension enabled by a SET MAX SET PASSWORD 7 See Address Offset Reserved Area Boot, INCITS TR27:2001 6 1 = SET FEATURES subcommand required to spin-up after power-up 5 1 = Power-Up In Standby feature set enabled 4 Obsolete 3:1 Reserved 0 Shall be cleared to zero to indicate that the DOWNLOAD MICROCODE command is not supported Feature sets/commands enabled. If words (87:85) = 0000h or FFFFh feature set/command enabled notification not supported. 15 Shall be cleared to zero 14 Shall be set to one 13:6 Reserved 5 General Purpose Logging feature set 4:0 Reserved
122
December 11, 2006 Table 24 IDENTIFY PACKET DEVICE data (part 6 of 8) Word 88 O M M S P F V F V V V V V V F F F F F F F F 89 90 91 92 O O O B B B F F V
T13/1699-D Revision 3f
Description 15 Reserved 14 1 = Ultra DMA mode 6 is selected 13 1 = Ultra DMA mode 5 is selected 12 1 = Ultra DMA mode 4 is selected 11 1 = Ultra DMA mode 3 is selected 10 1 = Ultra DMA mode 2 is selected 0 = Ultra DMA mode 2 is not selected 9 1 = Ultra DMA mode 1 is selected 0 = Ultra DMA mode 1 is not selected 8 1 = Ultra DMA mode 0 is selected 0 = Ultra DMA mode 0 is not selected 7 Reserved 6 1 = Ultra DMA mode 6 and below are supported. Devices which require the DMADIR bit in the Packet command shall clear this bit to 0. 5 1 = Ultra DMA mode 5 and below are supported. Devices which require the DMADIR bit in the Packet command shall clear this bit to 0. 4 1 = Ultra DMA mode 4 and below are supported. Devices which require the DMADIR bit in the Packet command shall clear this bit to 0. 3 1 = Ultra DMA mode 3 and below are supported. Devices which require the DMADIR bit in the Packet command shall clear this bit to 0. 2 1 = Ultra DMA mode 2 and below are supported. Devices which require the DMADIR bit in the Packet command shall clear this bit to 0. 1 1 = Ultra DMA mode 1 and below are supported. Devices which require the DMADIR bit in the Packet command shall clear this bit to 0. 0 1 = Ultra DMA mode 0 is supported. Devices which require the DMADIR bit in the Packet command shall clear this bit to 0. Time required for security erase unit completion Time required for Enhanced security erase completion Reserved Master Password Identifier
123
F F V
F V V
F F V V V
B B B B B B
M M M M O
F V V V F V V F F F F F F
Description Hardware reset result. The contents of bits (12:0) of this word shall change only during the execution of a hardware reset. 15 Shall be cleared to zero. 14 Shall be set to one. 13 1 = device detected CBLID- above ViH B B 0 = device detected CBLID- below VBiLB 12:8 Device 1 hardware reset result. Device 0 shall clear these bits to zero. Device 1 shall set these bits as follows: 12 Reserved. 11 0 = Device 1 did not assert PDIAG-. 1 = Device 1 asserted PDIAG-. 10:9 These bits indicate how Device 1 determined the device number: 00 = Reserved. 01 = a jumper was used. 10 = the CSEL signal was used. 11 = some other method was used or the method is unknown. 8 Shall be set to one. 7:0 Device 0 hardware reset result. Device 1 shall clear these bits to zero. Device 0 shall set these bits as follows: 7 Reserved. 6 0 = Device 0 does not respond when Device 1 is selected. 1 = Device 0 responds when Device 1 is selected. 5 0 = Device 0 did not detect the assertion of DASP-. 1 = Device 0 detected the assertion of DASP-. 4 0 = Device 0 did not detect the assertion of PDIAG-. 1 = Device 0 detected the assertion of PDIAG-. 3 0 = Device 0 failed diagnostics. 1 = Device 0 passed diagnostics. 2:1 These bits indicate how Device 0 determined the device number: 00 = Reserved. 01 = a jumper was used. 10 = the CSEL signal was used. 11 = some other method was used or the method is unknown. 0 Shall be set to one. 15:8 Vendors recommended acoustic management value. 7:0 Current automatic acoustic management value. Reserved 15:12 NAA (3:0) 11:0 IEEE OUI (23:12) 15:4 IEEE OUI (11:0) 3:0 Unique ID (35:32) 15:0 Unique ID (31:16) 15:0 Unique ID (15:0) Reserved for world wide name extension to 128 bits Reserved
124
T13/1699-D Revision 3f
Description ATAPI byte count = 0 behavior Obsolete O Obsolete O Security status F 15:9 Reserved V 8 Security level 0 = High, 1 = Maximum F 7:6 Reserved F 5 1 = Enhanced security erase supported V 4 1 = Security count expired V 3 1 = Security frozen V 2 1 = Security locked V 1 1 = Security enabled F 0 1 = Security supported 129-159 X Vendor specific 160-175 N F Reserved for assignment by the CompactFlash Association 176-254 F Reserved 255 O X Integrity word 15:8 Checksum 7:0 Signature V The contents of the field is variable and Key: may change depending on the state of the O/M Mandatory/optional requirement. device or the commands executed by the M Support of the word is mandatory. device. O Support of the word is optional. F/V Fixed/variable content X The content of the field may be fixed or F The content of the field is fixed and does not variable change. The DCO command may change the S/P Content applies to Serial or Parallel transport value of a fixed field. For removable media S Serial Transport devices, these values may change when media is P Parallel Transport removed or changed. B Both Serial and Parallel Transports N Belongs to a transport other than Serial or Parallel 7.17.6.2 Word 0: General configuration Bits (15:14) of word 0 indicate the type of device. Bit 15 shall be set to one and bit 14 shall be cleared to zero to indicate the device implements the PACKET feature set. Bits (12:8) of word 0 indicate the command packet set implemented by the device. This value follows the peripheral device type value as defined in SPC-3. Bit 7 if set to one indicates that the device has removable media. If the Parallel interface is implemented, bits (6:5) of word 0 indicate the DRQ response time when a PACKET command is received. A value of 00b indicates a maximum time of 3 ms from receipt of PACKET to the setting of DRQ to one. A value of 10b indicates a maximum time of 50 s from the receipt of PACKET to the setting of DRQ to one. The value 11b is reserved. If bit 2 is set to one it indicates that the content of the IDENTIFY PACKET DEVICE data is incomplete. This may occur if the device supports the Power-up in Standby feature set and required data is contained on the device media. In this case the content of at least word 0 and word 2 shall be valid. Bits (1:0) of word 0 indicate the packet size the device supports. A value of 00b indicates that a 12-byte packet is supported; a value of 01b indicates a 16 byte packet. The values 10b and 11b are reserved. Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) 125
O M M
S P B
F V F X
T13/1699-D Revision 3f 7.17.6.3 Word 1: Reserved 7.17.6.4 Word 2: Specific configuration Word 2 shall have the same content described for IDENTIFY DEVICE data word 2. 7.17.6.5 Words 3-9: Reserved 7.17.6.6 Words 10-19: Serial number
The use of these words is optional. If not implemented, the content shall be zeros. If implemented, the content shall be as described in IDENTIFY DEVICE data words 10-19. See 7.16.7. 7.17.6.7 Words 20-22: Reserved 7.17.6.8 Words 23-26: Firmware revision Words 23-26 shall have the content described for IDENTIFY DEVICE data words 23-26. 7.17.6.9 Words 27-46: Model number Words 27-46 shall have the content described for IDENTIFY DEVICE data words 27-46. 7.17.6.10 Words 47-48: Reserved 7.17.6.11 Word 49: Capabilities Bit 15:12 of word 49 are obsolete. Bit 11 of word 49 is used to determine whether a device supports IORDY. If this bit is set to one, then the device supports IORDY operation. If this bit is zero, the device may support IORDY. This ensures backward compatibility. If a device supports PIO mode 3 or higher, then this bit shall be set to one. If the serial interface is implemented, this bit shall be set to one. Bit 10 of word 49 is used to indicate a devices ability to enable or disable the use of IORDY. If this bit is set to one, then the device supports the disabling of IORDY. Disabling and enabling of IORDY is accomplished using the SET FEATURES command. If the serial interface is implemented, this bit shall be set to one. Bit 9 of word 49 shall be set to one. Bit 8 of word 49 indicates that DMA is supported. Devices which require the DMADIR bit in the Packet command shall clear this bit to 0 7.17.6.12 Word 50: Capabilities Word 50 shall have the content described for IDENTIFY DEVICE data word 50. Support of this word is mandatory if the STANDBY command is supported. 7.17.6.13 Word 51: Obsolete 7.17.6.14 Word 52: Reserved 7.17.6.15 Word 53: Field validity Word 53 shall have the content described for IDENTIFY DEVICE data word 53. 7.17.6.16 Words 54-61: Reserved
126
T13/1699-D Revision 3f
ATAPI devices that use a serial ATA bridge chip for connection to a serial ATA host may require use of the DMADIR bit to indicate transfer direction for Packet DMA commands. Word 62 is used to indicate if such support is required. If bit 15 of word 62 is set to one, then DMADIR bit in the Packet Command is required by the device for Packet DMA and Bits 2:0 of word 63, bits 15 and 8 in word 49, and bits 6:0 of word 88 shall be cleared to 0,. If bit 15 of word 62 is cleared to 0, DMADIR bit in the PACKET command is not required. If bit 15 of word 62 is cleared to zero, then all bits of word 62 shall be cleared to zero. Bits (14:11) are reserved. Bits (10:1) indicate DMA mode support. Since the DMADIR bit is only used for a Serial ATAPI device, all of these bits are set to 1. 7.17.6.18 Word 63: Multiword DMA transfer Word 63 identifies the Multiword DMA transfer modes supported by the device and indicates the mode that is currently selected. Only one DMA mode shall be selected at any given time. If an Ultra DMA mode is enabled, then no Multiword DMA mode shall be enabled. If a Multiword DMA mode is enabled then no Ultra DMA mode shall be enabled. Bit (15:11) are reserved. Bits 10:8 shall have the content described for IDENTIFY DEVICE data word 63. Bits (7:3) are reserved If bit 2 of Word 63 is set to one, then Multiword DMA modes 2 and below are supported. If this bit is cleared to zero, then Multiword DMA mode 2 is not supported. If Multiword DMA mode 2 is supported, then Multiword DMA modes 1 and 0 shall also be supported. If bit 2 of Word 63 is set to one, bits (1:0) shall be set to one. If the serial interface is implemented, this bit shall be set to one except this bit shall be cleared 0 for Serial ATAPI devices requiring the DMADIR bit in the PACKET command. If bit 1 of Word 63 is set to one, then Multiword DMA modes 1 and below are supported. If this bit is cleared to zero, then Multiword DMA mode 1 is not supported. If Multiword DMA mode 1 is supported, then Multiword DMA mode 0 shall also be supported. If bit 1 of Word 63 is set to one, bit 0 shall be set to one. If the serial interface is implemented, this bit shall be set to one except this bit shall be cleared to 0 for Serial ATAPI devices which require the DMADIR bit in the PACKET command. If bit 0 of word 63 is set to one, then Multiword DMA mode 0 is supported. If the serial interface is implemented, this bit shall be set to one except this bit shall be cleared to 0 for Serial ATAPI devices which require the DMADIR bit in the PACKET command. 7.17.6.19 Word 64: PIO transfer mode supported Word 64 shall have the content described for IDENTIFY DEVICE data word 64. 7.17.6.20 Word 65: Minimum multiword DMA transfer cycle time per word Word 65 shall have the content described for IDENTIFY DEVICE data word 65. 7.17.6.21 Word 66: Device recommended multiword DMA cycle time Word 66 shall have the content described for IDENTIFY DEVICE data word 66. 7.17.6.22 Word 67: Minimum PIO transfer cycle time without flow control Word 67 shall have the content described for IDENTIFY DEVICE data word 67. 7.17.6.23 Word 68: Minimum PIO transfer cycle time with IORDY Word 68 shall have the content described for IDENTIFY DEVICE data word 68.
127
T13/1699-D Revision 3f 7.17.6.24 Words 69-70: Reserved 7.17.6.25 Words 71-72: Obsolete 7.17.6.26 Words 73-74: Reserved 7.17.6.27 Word 75: Obsolete 7.17.6.28 Words 76-79: Reserved for Serial ATA 7.17.6.29 Word 80: Major revision number Word 80 shall have the content described for IDENTIFY DEVICE data word 80. 7.17.6.30 Word 81: Minor revision number Word 81 shall have the content described for IDENTIFY DEVICE data word 81. 7.17.6.31 Words 82-84: Feature sets/commands supported
Words 82-84 shall have the content described for words IDENTIFY DEVICE data words 82-84 except that bit 4 of word 82 shall be set to one to indicate that the PACKET feature set is supported. 7.17.6.32 Words 85-87: Feature sets/commands enabled Words 85-87 shall have the content described for words IDENTIFY DEVICE data words 85-87 except that bit 4 of word 85 shall be set to one to indicate that the PACKET feature set is supported. 7.17.6.33 Word 88:Ultra DMA modes Word 88 shall have the content described for IDENTIFY DEVICE data words 88, except bits 6:0 shall be cleared to 0 for Serial ATAPI devices which require the DMADIR bit in the Packet command. 7.17.6.34 Word 89: Time required for Security erase unit completion Word 89 shall have the content described for IDENTIFY DEVICE data words 89. 7.17.6.35 Word 90: Time required for Enhanced security erase unit completion Word 90 shall have the content described for IDENTIFY DEVICE data words 90. 7.17.6.36 Word 91: Reserved 7.17.6.37 Word 92 Word 92 shall have the content described for IDENTIFY DEVICE data words 92. 7.17.6.38 Word 93: Hardware reset results Word 93 shall have the content described for IDENTIFY DEVICE data words 93. Support of bits (13:15) is mandatory. Support of bits (12:0) is optional. 7.17.6.39 Word 94: Current automatic acoustic management value Word 94 shall have the content described for IDENTIFY DEVICE data words 94. 7.17.6.40 Word 95-107: Reserved
128
T13/1699-D Revision 3f
Words 111-108 shall contain the mandatory value of the world wide name (WWN) for the device. Word 108 bits 15-12 shall contain 5h, indicating that the naming authority is IEEE. All other values are reserved. Words 108 bits 11-0 and word 109 bits (15:4) shall contain the Organization Unique Identifier (OUI) for the device manufacturer. The OUI shall be assigned by the IEEE/RAC as specified by ISO/IEC 13213:1994. The identifier may be obtained from: Institute of Electrical and Electronic Engineers, Inc. Registration Authority Committee 445 Hoes Lane Piscataway, NJ 08855-1331 Word 109 bits (3:0), word 110, and word 111 shall contain a value assigned by the vendor that is unique for the device in the OUI domain. 7.17.6.42 Words 112-115: Reserved for a 128-bit world wide name 7.17.6.43 Words 116-124: Reserved 7.17.6.44 Word 125 ATAPI byte count=0 behavior If the contents of word 125 are 0000h and the value of the byte count limit is zero, the device shall return command aborted. If the contents of word 125 are non-zero and the value of the byte count limit is zero, the device shall use the contents of word 125 as the actual byte count limit for the current command and shall not abort. The device may be reconfigured to report a new value. However, after the device is reconfigured, the content of word 125 reported shall not change until after the next power-on reset or hardware reset. 7.17.6.45 Word 126: Obsolete 7.17.6.46 Word 127: Removable Media Status Notification feature set support Word 127 shall have the content described for IDENTIFY DEVICE data words 127. Support of this word is mandatory if the Removable Media Status Notification feature set is supported. 7.17.6.47 Word 128: Security status Word 128 shall have the content described for IDENTIFY DEVICE data word 128. Support of this word is mandatory if the Security feature set is supported. 7.17.6.48 Words 129-160: Reserved 7.17.6.49 Words 161-175: Reserved for assignment by the CompactFlash Association 7.17.6.50 Words 176-254: Reserved 7.17.6.51 Word 255: Integrity Word Word 255 shall have the content described for IDENTIFY DEVICE data words 255. Word 255 should be implemented.
129
T13/1699-D Revision 3f
7:0 E3h
Values other than zero in the Count field when the IDLE command is issued shall determine the time period programmed into the Standby timer. Table 25 defines these values. Table 25 Automatic Standby timer periods Count field contents Corresponding time-out period 0 (00h) Time-out disabled 1-240 (01h-F0h) (value * 5) seconds 241-251 (F1h-FBh) ((value - 240) *30) minutes 252 (FCh) 21 minutes 253 (FDh) Period between 8 hours and 12 hours 254 (FEh) Reserved 255 (FFh) 21 min. 15 seconds NOTE 7 Times are approximate. 7.18.4 Normal Outputs See table 79. 7.18.5 Error Outputs See table 100.
130
T13/1699-D Revision 3f
131
T13/1699-D Revision 3f 7.19.3 Inputs (Default Function) Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description N/A except when the unload feature is requested, see 7.19.4 N/A except when the unload feature is requested, see 7.19.4 N/A except when the unload feature is requested, see 7.19.4 Bit 15 14 13 12 11:8 05h Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
7:0 E1h
7.19.4 Inputs (Unload Feature) Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description 0044h Reserved 000000554E4Ch Bit 15 14 13 12 11:8 05h Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
7:0 E1h
7.19.5 Normal Outputs (Default Function) See table 79. 7.19.6 Normal Outputs (Unload Feature) See table 86. 7.19.7 Error Outputs See table 100.
132
T13/1699-D Revision 3f
Action Return command aborted and abort any outstanding queued commands. Return command aborted and do not abort any outstanding queued commands. Return command aborted and do not abort any outstanding queued commands.
7.20.4 Normal Outputs This command always fails with an error. 7.20.5 Error Outputs All fields are preserved with the exception of Error and Status. This command always fails with the device returning command aborted. See table 114
133
T13/1699-D Revision 3f
Individual NV Cache Commands are identified by the value placed in the Feature field as shown in table 27. Table 27 NV Cache Commands Value 00h-01h 02h-0Fh 10h 11h 12h 13h 14h 15h-CFh D0h-EFh F0-FFh Command Name Reserved Reserved for NV Cache Power Management feature set ADD LBA(S) TO NV CACHE PINNED SET DMA EXT REMOVE LBA(S) FROM NV CACHE PINNED SET DMA EXT QUERY NV CACHE PINNED SET DMA EXT QUERY NV CACHE MISSES DMA EXT FLUSH NV CACHE Reserved Vendor Specific Reserved
7.21.2 NV Cache Power Management Overview The optional NV Cache Power Management feature set permits a host to modify the behavior of a device in a manner that allows the device to improve response times to read and write commands while reducing the device's power consumption. Commands unique to the NV Cache Power Management feature set use a single command code and are differentiated from one another by the value placed in the Features field. A device that implements the NV Cache Power Management feature set shall implement the following commands: a) Set NV Cache Power Mode b) Return From NV Cache Power Mode
134
T13/1699-D Revision 3f
Individual NV Cache Power Management commands are identified by the value placed in the Feature field as shown in table 28. Table 28 NV Cache Power Managements Commands Value 00h 01h 02h-0Fh 10h-2Fh 30h-CFh D0h-EFh F0-FFh Command Name SET NV CACHE POWER MODE EXT RETURN FROM NV CACHE POWER MODE EXT Reserved for NV Cache feature set ADD LBA(S) TO NV CACHE PINNED SET DMA EXT Reserved Vendor Specific Reserved
135
T13/1699-D Revision 3f 7.21.3 ADD LBA(S) TO NV CACHE PINNED SET - B6h/10h, DMA 7.21.3.1 Description
This command adds the logical blocks specified in the NV Cache Set Data to the NV Cache Pinned Set if they are not already so. If the PI bit is set to one the command shall not complete until the NV Cache population is complete. If the PI bit is set to zero, the command shall complete immediately and the population of the sector data shall be completed on subsequent Write operations to that LBA. If a Read operation occurs to this LBA before the sector data is populated in the NV Cache then this data should be sourced from the valid data located on the magnetic media and may require a disk spin up. If an LBA Range Entry (see 7.21.3.5) specified in the NV Cache Set Data does exist but is beyond the range of user-accessible logical blocks, the device shall add the logical blocks to the NV Cache Pinned Set, but continue to fail all reads and writes to the LBA as before. The response to this command will be the number of sectors that can still be added to the NV Cache's pinned set. 7.21.3.2 Inputs 7.21.3.2.1 Overview Word 00h 01h 02h-04h Name Feature Count LBA Bit 47:1 0 05h Device Bit 15:13 12 11:8 Command 7:0 Description N/A Transport Dependent - See 6.1.9 Reserved B6h Description Reserved Populate Immediately (PI) - See 7.21.3.2.2 Description 0010h Number of 256 word data blocks to be transferred. 0000h specifies that 65,536 blocks shall be transferred.
7.21.3.2.2 Populate Immediately PI (Populate Immediately) shall be set to one to specify that the logical blocks specified in the Cache Set Data are to be added to the device's NV Pinned Cache Set and populated immediately from the disk before the command completion. PI shall be set to zero to specify that the logical blocks specified in the NV Cache Set Data are to be added to the device's NV Pinned Cache Set and populated upon subsequent Write operation to that LBA. 7.21.3.3 Normal Outputs See table 95. 7.21.3.4 Error Outputs If this command fails, none of the requested logical blocks are added to the Pinned Set. See table 124 for more information. 7.21.3.5 Output Data
136
December 11, 2006 7.21.4 FLUSH NV CACHE - B6h/14h, Non-data 7.21.4.1 Description
T13/1699-D Revision 3f
The device ensures that it has at least as many logical blocks as specified in the 'Minimum Number of logical blocks to Flush Make Available' available to be pinned without requiring a future spin up. If the device must spin up in order to make the required number of logical blocks available it must do so. The command completes immediately and if necessary the device performs the task of removing logical blocks from the NV Cache Unpinned Set to provide the capacity requested in a prudent fashion. If the device determines it is unable to complete the operation, it shall report an error. The output of this command is the number of logical blocks which have yet to be removed from the NV Cache Unpinned Set to satisfy the 'Minimum Number of logical blocks to Make Available ' or completely empty the NV Cache Unpinned Set, whichever is lesser. 7.21.4.2 Inputs Word 00h 01h 02h-04h Name Feature Count LBA Description 0014h Reserved Bit 47:32 31:0 05h Device Bit 15:13 12 11:8 Command 7.21.4.3 Normal Outputs The number of unflushed logical blocks is the number of logical blocks which have not yet to be flushed from the NV Cache Unpinned Set to satisfy the Minimum Number of logical blocks to flush or to completely empty the NV Cache Unpinned Set, whichever is lesser. See table 96. 7.21.4.4 Error Outputs See table 126. 7:0 Description N/A Transport Dependent - See 6.1.9 Reserved B6h Description Reserved Minimum number of logical blocks to flush
137
T13/1699-D Revision 3f 7.21.5 QUERY NV CACHE MISSES - B6h/13h, DMA 7.21.5.1 Description
This command requests the device to report NV Cache Misses in LBA Ranges in a single 512 byte block. The LBA Ranges sent must be in the accessed order. If the device does not have as many LBA ranges as are requested in the transfer, the unused LBA ranges shall be filled with zero. The Cache Miss data shall be cleared on every transition to Standby State. 7.21.5.2 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description 0013h 0001h Reserved Bit 15:13 12 11:8 Command 7.21.5.3 Normal Outputs See table 95. 7.21.5.4 Error Outputs See table 126. 7.21.5.5 Input Data 7:0 Description N/A Transport Dependent - See 6.1.9 Reserved B6h
138
December 11, 2006 7.21.6 QUERY NV CACHE PINNED SET - B6h/12h, DMA 7.21.6.1 Description
T13/1699-D Revision 3f
This command requests the device to send the LBA Ranges currently in the NV Cache pinned set in 512 bytes block equal to the number in Block Count. The LBA Ranges sent must be in numerical order. If a device does not have as many LBA Ranges as are requested in the transfer, the unused LBA Ranges shall be filled with zero. 7.21.6.2 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description 0012h Number of 256 word data blocks to be transferred. 0000h specifies that 65,536 blocks shall be transferred. Starting LBA - The first LBA to be Queried Bit 15:13 12 11:8 Command 7.21.6.3 Normal Outputs See table 95. 7.21.6.4 Error Outputs See table 126. 7.21.6.5 Input Data 7:0 Description N/A Transport Dependent - See 6.1.9 Reserved B6h
139
T13/1699-D Revision 3f 7.21.7 REMOVE LBA(S) FROM NV CACHE PINNED SET - B6h/11h, DMA 7.21.7.1 Description
This command removes the logical blocks specified in the NV Cache Set Data from the NV Cache's pinned set, no longer including them in the set of logical blocks that must always be mapped in the NV Cache. If the NV Cache Set Data specifies an LBA not in the NV Cache Pinned Set, the LBA shall be ignored without causing an error. The response to this command will be the number of sectors that the NV Cache can still add to the NV Cache's pinned working set as specified in the Count and LBA fields. 7.21.7.2 Inputs 7.21.7.2.1 Overview Word 00h 01h 02h-04h Name Feature Count LBA Bit 47:1 0 05h Device Bit 15:13 12 11:8 Command 7.21.7.2.2 Unpin All UA (Unpin All) indicates that the Value in Sector Count should be ignored, and the NV Cache Pinned Set shall have no logical blocks mapped 7.21.7.3 Normal Outputs See table 95. 7.21.7.4 Error Outputs If this command fails, none of the requested logical blocks are removed from the Pinned Set. See table 125 for more information. 7.21.7.5 Output Data 7:0 Description N/A Transport Dependent - See 6.1.9 Reserved B6h Description Reserved Unpin All (UA) - See 7.21.7.2.2 Description 0011h Number of 256 word data blocks to be transferred. 0000h specifies that 65,536 blocks shall be transferred.
140
December 11, 2006 7.21.8 RETURN FROM NV CACHE POWER MODE - B6h/01h, Non-data 7.21.8.1 Description
T13/1699-D Revision 3f
This command shall cause the device to clear the NV Cache Power Mode. Upon completion of this command the device shall treat the NV Cache Power Mode value to be FALSE for all Power Management state transitions. 7.21.8.2 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description 0001h Reserved Reserved Bit 15:13 12 11:8 Command 7.21.8.3 Normal Outputs See table 79. 7.21.8.4 Error Outputs See table 101 7:0 Description N/A Transport Dependent - See 6.1.9 Reserved B6h
141
T13/1699-D Revision 3f 7.21.9 SET NV CACHE POWER MODE - B6h/00h, Non-data 7.21.9.1 Description
This command is the only way to cause the device to set the NV Cache Power Mode. Upon completion of this command the device shall treat the NV Cache Power Mode value to be TRUE for all Power Management state transitions and should strive to power down the spindle and use the NV Cache to satisfy read and write requests whenever possible in order to reduce device power consumption. If the device cannot satisfy a read or write request from its NV Cache it shall spin up and stay spun up for at least as many seconds as the value in Sector Count. 7.21.9.2 Inputs 7.21.9.2.1 Overview Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description 0000h Minimum High-Power Time - See 7.21.9.2.2 Reserved Bit 15:13 12 11:8 Command 7:0 Description N/A Transport Dependent - See 6.1.9 Reserved B6h
7.21.9.2.2 Minimum High-Power Time Contains minimum value, in seconds, that the device shall stay in a high power state in the case that the device must enter the high power state to access it's media while NV CACHE Power Mode is set. The high power state can include any PM Power Management state in which the media is spun up and readily available. This timer can be aborted upon receiving the 'Return From NV Cache Power Mode' command. The maximum amount of time the device shall keep the media spun up is vendor specific. 7.21.9.3 Normal Outputs See table 79. 7.21.9.4 Error Outputs See table 101
142
T13/1699-D Revision 3f
01h
02h-04h
LBA Bit 47:24 23:8 7:0 Description Reserved Byte Count - See 7.22.5 Reserved
05h
Device Bit 15 14 13 12 11:8 Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
7:0 A0h
7.22.4 DMADIR This bit indicates Packet DMA direction and is used only for devices that implement the Packet feature set with a Serial ATA bridge that require direction indication from the host. Support for this bit is determined by reading bit 15 of word 62 in the IDENTIFY PACKET DEVICE data. If bit 15 of word 62 is set to 1, the device requires the use of the DMADIR bit for Packet DMA commands. If the device requires the DMADIR bit to be set for Packet DMA operations and the current operations is DMA (i.e. bit 0, the DMA bit, is set), this bit indicates the direction of data transfer (0 = transfer to the device; 1 =
143
T13/1699-D Revision 3f
transfer to the host). If the device requires the DMADIR bit to be set for Packet DMA operations but the current operations is PIO (i.e. bit 0, the DMA bit, is cleared), this bit is ignored. Since the data transfer direction is set by the host as the command is constructed, the DMADIR bit should not conflict with the data transfer direction of the command. If a conflict between the command transfer direction and the DMADIR bit occurs, the device should return with an ABORTED command, and the sense key set to ILLEGAL REQUEST. If the device does not require the DMADIR bit for Packet DMA operations, this bit should be cleared to 0. A device that does not support the DMADIR feature may abort a command if the DMADIR bit is set to 1. 7.22.5 Byte Count This is the maximum byte count that is to be transferred in any single DRQ data block for PIO transfers. The byte count does not apply to the command packet transfer. If the PACKET command does not transfer data, the byte count is ignored. If the PACKET command results in a data transfer: a) the host should not set the byte count limit to zero. If the host sets the byte count limit to zero, the contents of IDENTIFY PACKET DEVICE data word 125 determines the expected behavior; b) the value set into the byte count limit shall be even if the total requested data transfer length is greater than the byte count limit; c) the value set into the byte count limit may be odd if the total requested data transfer length is equal to or less than the byte count limit; The value FFFFh is interpreted by the device as though the value were FFFEh. 7.22.6 Normal Outputs 7.22.6.1 Awaiting command When the device is ready to accept the command packet from the host the return structure shall be set according to table 87. Input/Output shall be cleared to zero, and Command/Data shall be set to one. Byte Count shall reflect the value set by the host when the command was issued. 7.22.6.2 Data transmission Data transfer shall occur after the receipt of the command packet. See table 87 for the return structure when the device is ready to transfer data requested by a data transfer command. Input/Output is ignored, and Command/Data shall be set to zero. If the transfer is to be in PIO mode, the byte count of the data to be transferred for this DRQ data block shall be presented. Valid byte count values are as follows: a) b) c) d) e) the byte count shall be less than or equal to the byte count limit value from the host; the byte count shall not be zero; the byte count shall be less than or equal to FFFEh; the byte count shall be even except for the last transfer of a command; if the byte count is odd, the last valid byte transferred is on DD(7:0) and the data on DD(15:8) is a pad byte of undefined value;
If the last transfer of a command has a pad byte, the byte count shall be odd. 7.22.6.3 Successful command completion When the device has command completion without error, the device returns the data structure found in table 87. Input/Output shall be set to one, Command/Data shall be set to one. Byte Count is reserved at command completion. 7.22.7 Error Outputs The device shall not terminate the PACKET command with an error before the last byte of the command packet has been written. See table 115
144
T13/1699-D Revision 3f
7:0 E4h
7.23.4 Normal Outputs See table 79. 7.23.5 Error Outputs The device may return error status if an Interface CRC error has occurred. See table 100. NOTE 9 There is no defined mechanism for a device to return an ICRC error status that may have occurred during the last data block of a PIO-in data transfer, there may be other mechanisms in which a host may verify that an Interface CRC error occurred in these cases.
145
T13/1699-D Revision 3f
Device
7:0 C8h
146
T13/1699-D Revision 3f
Device
7:0 25h
147
T13/1699-D Revision 3f
7:0 C7h
148
T13/1699-D Revision 3f
When the transfer of all requested data has occurred without error, the device returns the data structure described in table 88. Release shall be cleared to zero, Input/Output shall be set to one, and Command/Data shall be set to one. 7.26.5 Error Outputs The Count field contains the Tag for this command if the device supports the TCQ feature set. The device shall return command aborted if the device supports the TCQ feature set and the Tag is invalid. An unrecoverable error encountered during the execution of this command results in the termination of the command and the logical sector where the first unrecoverable error occurred is returned. If write cache is enabled unrecoverable errors may not be reliably reported as they may occur after the completion of the command. If a queue existed, the unrecoverable error shall cause the queue to abort. See table 116 for more information.
149
T13/1699-D Revision 3f
7:0 26h
150
T13/1699-D Revision 3f
When the transfer of all requested data has occurred without error, the device returns the data structure described in table 94. Release shall be cleared to zero, Input/Output shall be set to one, and Command/Data shall be set to one. 7.27.5 Error Outputs The Count field contains the Tag for this command if the device supports the TCQ feature set. The device shall return command aborted if the device supports the TCQ feature set and the Tag is invalid. An unrecoverable error encountered during the execution of this command results in the termination of the command and the logical sector where the first unrecoverable error occurred is returned. If write cache is enabled unrecoverable errors may not be reliably reported as they may occur after the completion of the command. If a queue existed, the unrecoverable error shall cause the queue to abort. See table 117.
151
T13/1699-D Revision 3f
7:0 2Fh
The Comprehensive SMART error log and the SMART self-test log are defined in 7.52.7 and 7.52.9. If log address 02h or log address 06h are accessed using the READ LOG EXT or WRITE LOG EXT commands, command abort shall be returned. All 28-bit entries contained in the Comprehensive SMART log shall also be included in the Extended Comprehensive SMART error log with the 48-bit entries. The Extended SMART self-test log shall support 48-bit and 28-bit addressing. All 28-bit entries contained in the SMART self-test log shall also be included in the Comprehensive SMART self-test log with the 48-bit entries. 7.28.3.2 Block Count Specifies the number of 512-byte blocks of data to be read from the specified log. The log transferred by the drive shall start at the block of data in the specified log at the specified offset, regardless of the block count requested. A value of zero is illegal and shall result in command aborted. 7.28.3.3 Log Address A device may support a subset of the available logs. Support for individual logs is determined by support for the associated feature set. Support of the associated log(s) is mandatory for devices implementing the associated
152
T13/1699-D Revision 3f
feature set. If this command is implemented, all address values defined as host vendor specific shall be implemented, see A.8 for more information regarding Host Vendor Specific log pages. See A.9 for information on Device Vendor Specific log pages. 7.28.4 Normal Outputs See table 92. 7.28.5 Error Outputs If the device does not support this command, if the feature set associated with the log specified in the LBA field (7:0) is not supported or enabled, or if the values in the Features, Count, or LBA (47:8) fields are invalid, the device shall return command aborted. Abort shall be set to one if the feature associated with the log specified in the LBA bits 7:0 is not supported, if the count field is cleared to zero, or if other field values are invalid. Abort may be set to one if the device is not able to complete the action requested by the command. Abort shall be set to one if the Data Block Offset is larger than the log size reported in the Log Directory. Abort shall be set to one if the host issues a READ LOG EXT or WRITE LOG EXT command with a value of zero as Block Count. The device may return error status if an Interface CRC error has occurred. See table 105. NOTE 10 There is no defined mechanism for a device to return an ICRC error status that may have occurred during the last data block of a PIO-in data transfer; there may be other mechanisms in which a host may verify that an Interface CRC error occurred in these cases.
153
T13/1699-D Revision 3f
154
T13/1699-D Revision 3f
Device
7:0 C4h
T13/1699-D Revision 3f
NOTE 11 There is no defined mechanism for a device to return an ICRC error status that may have occurred during the last data block of a PIO-in data transfer; there may be other mechanisms in which a host may verify that an Interface CRC error occurred in these cases.
156
T13/1699-D Revision 3f
Device
7:0 29h
T13/1699-D Revision 3f
NOTE 12 There is no defined mechanism for a device to return an ICRC error status that may have occurred during the last data block of a PIO-in data transfer; there may be other mechanisms in which a host may verify that an Interface CRC error occurred in these cases.
158
T13/1699-D Revision 3f
7:0 F8h
159
T13/1699-D Revision 3f
7:0 27h
160
T13/1699-D Revision 3f
Device
7:0 20h
161
T13/1699-D Revision 3f
Device
7:0 24h
162
T13/1699-D Revision 3f
The number of logical sectors to be transferred. A value of 0000h indicates that 65536 logical sectors are to be transferred. (MSB) Address of first logical sector to be transferred. (LSB) Bit 15 14 13 12 11:8 Description Obsolete Shall be set to one Obsolete Transport Dependent - See 6.1.9 Reserved 2Ah
Device
Command
7:0
7.36.3.2 Command Completion Time Limit (CCTL) CCTL specifies the time allowed for the device to process the command before reporting command completion. If CCTL is not cleared to zero, then the device shall report command completion within (CCTL * (IDENTIFY DEVICE data words (99:98)) microseconds. The device shall measure the time before reporting command completion from command acceptance. If CCTL is cleared to zero, and Default CCTL was not cleared to zero in the most recent CONFIGURE STREAM command (see 7.9) for the Stream ID, then the device shall report command completion within the time specified by Default CCTL (see 7.9.3.4). If CCTL is cleared to zero, and Default CCTL was cleared to zero in the most recent CONFIGURE STREAM command (see 7.9) for the Stream ID, or CCTL is cleared to zero and no previous CONFIGURE STREAM command was used to specify a Default CCTL for this Stream ID, then the result is vendor specific.
163
T13/1699-D Revision 3f
After reporting command completion, a device may continue to write data for the command from device cache to the media. 7.36.3.3 Read Continuous If RC is set to one, then: a) the device shall not stop processing the command due to errors; b) if an error occurs during data transfer or while reading data from the media before command completion or before the amount of time allowed for command completion based on the setting of CCTL (see 7.36.3.2) or Default CCTL (see 7.9.3) is reached, then the device: 1) shall continue to transfer the amount of data requested; 2) may continue reading data from the media; 3) shall report command completion after all data for the command has been transferred; and 4) shall save the error information in the Read Streaming Error log; or c) if the amount of time allowed for command completion based on the setting of CCTL (see 7.36.3.2) or Default CCTL (see 7.9.3) is reached, then the device: 1) shall stop processing the command; 2) shall report command completion; and 3) shall set CCTO in the Read Streaming Error log to one. If RC is cleared to zero and an error occurs, then the device: a) may continue transferring data; and b) shall report command completion after the data transfer has been completed. 7.36.3.4 Not Sequential (NS) If NS is set to one, then the next READ STREAM command with the same Stream ID may not be sequential in the LBA space. Any read of the device media or internal device buffer management as a result of the state of the NS bit is vendor specific. 7.36.3.5 Stream ID Stream ID specifies the stream to be read. The device shall operate according to the parameters specified by the most recent successful CONFIGURE STREAM command specifying this Stream ID. 7.36.4 Normal Outputs See table 84 for the definition of Normal Outputs. 7.36.5 Error Outputs If: a) RC was set to one in the command, and b) the device is able to return the amount of data requested for the command (e.g., an error occurred while reading from the media); then the device shall set SE to one and clear ERR to zero. If: a) RC was set to one in the command, and b) the device is not able to return the amount of data requested for the command (e.g., an ICRC error is reported at command completion); then the device shall clear SE to zero and set ERR to one. If: a) RC was cleared to zero in the command; b) CCTL was not cleared to zero in the command, or CCTL was cleared to zero in the command and Default CCTL specified in the most recent CONFIGURE STREAM command for the Stream ID (see 7.9) was not cleared to zero; and
164
T13/1699-D Revision 3f
c) the time specified for command completion by CCTL (see 7.36.3.2) or Default CCTL (see 7.9.3) has been reached; then the device shall clear SE to zero, set ERR to one, and set ABRT to one. If: a) RC was cleared to zero in the command; b) CCTL was cleared to zero in the command; and c) Default CCTL was cleared to zero in the most recent CONFIGURE STREAM command for the Stream ID (see 7.9); then the device shall clear SE to zero, set ERR to one, and set ICRC, IDNF, and/or ABRT to one (i.e., indicating the error type). See table 107 for the definition of other Error Outputs.
165
T13/1699-D Revision 3f
166
T13/1699-D Revision 3f
Device
7:0 40h
167
T13/1699-D Revision 3f
Device
7:0 42h
168
T13/1699-D Revision 3f
7:0 F6h
169
The device shall return command aborted if the device is in Locked mode, or the device is in Frozen mode. The device may return error status if an Interface CRC error has occurred. See table 100. 7.40.6 Output Data Structure Table 29 SECURITY DISABLE PASSWORD data content Word 0 Control word Bit Field Name 0 Identifier 15:1 Reserved Password (32 bytes) Reserved Content Description 0=compare User password 1=compare Master password
1-16 17-255
170
T13/1699-D Revision 3f
7:0 F3h
7.41.4 Normal Outputs See table 79. 7.41.5 Error Outputs Abort shall be set to one if the device is in Frozen mode. See table 100.
171
T13/1699-D Revision 3f
172
December 11, 2006 7.42.3 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description N/A N/A N/A Bit 15 14 13 12 11:8 05h Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
T13/1699-D Revision 3f
7:0 F4h
7.42.4 Normal Outputs See table 79. 7.42.5 Error Outputs The device shall return command aborted if the not immediately preceeded by a SECURITY ERASE PREPARE command, or if Enhanced mode was requested but the device does not support it, or of an invalid password was specified, or if the data area is not successfully overwritten. The device may return error status if an Interface CRC error has occurred. See table 100. 7.42.6 Output Data Structure Table 30 SECURITY ERASE UNIT data content Word 0 Content Control word Bit Field Name 0 Identifier 1 Erase mode Description 0=Compare User password 1=Compare Master password 0=Normal Erase 1=Enhanced Erase
1-16 17-255
173
T13/1699-D Revision 3f
7:0 F5h
7.43.4 Normal Outputs See table 79. 7.43.5 Error Outputs Abort shall be set to one if the device is in Frozen mode. See table 100.
174
T13/1699-D Revision 3f
7:0 F1h
7.44.4 Normal Outputs See table 79. 7.44.5 Error Outputs Abort shall be set to one if the device is in Frozen mode. The device may return error status if an Interface CRC error has occurred. See table 100.
175
T13/1699-D Revision 3f 7.44.6 Output Data Structure Table 31 SECURITY SET PASSWORD data content Word 0 Content Control word Bit 0 7:1 8 Field Name Identifier Reserved Security level Description 0=set User password 1=set Master password 0=High 1=Maximum
1-16 17 18-255
15:9 Reserved Password (32 bytes) Master Password Identifier (valid if word 0 bit 0 = 1) Reserved
176
T13/1699-D Revision 3f
7:0 F2h
7.45.4 Normal Outputs See table 79. 7.45.5 Error Outputs If the device is in Frozen mode or an invalid password is supplied or the password attempt counter has decremented to zero, the device shall return command aborted. The device may return error status if an Interface CRC error has occurred. See table 100.
177
T13/1699-D Revision 3f 7.45.6 Output Data Structure Table 32 SECURITY UNLOCK data content Word 0 Control word Bit Field Name 0 Identifier 15:1 Reserved Password (32 bytes) Reserved Content Description 0=compare User password 1=compare Master password
1-16 17-255
178
T13/1699-D Revision 3f
7:0 A2h
7.46.4 Outputs Outputs as a result of a SERVICE command are described in the command description for the command for which SERVICE is being requested.
179
T13/1699-D Revision 3f
180
Value 60h-65h 66h 67h-68h 69h 6Ah-76h 77h 78h-80h 81h 82h 83h 84h 85h 86h 87h 88h 89h 8Ah 8Bh 8Ch-8Fh 90h 91h-94h 95h 96h-99h 99h 9Ah 9Bh-A9h AAh ABh ACh-BAh BBh BCh-C0h C1h C2h C3h-CBh CCh CDh-D5h D6h-DCh DDh DEh DFh E0h E1h-EFh F0h-FFh
Description Reserved Disable reverting to power-on defaults (see 7.47.16) Reserved If the device implements the CFA feature set, then this subcommand is reserved for CFA. Reserved Obsolete Reserved Disable 8-bit PIO transfer mode (CFA feature set only) (see 7.47.3) Disable write cache (see 7.47.4) Reserved for e06144 Obsolete Disable advanced power management (see 7.47.6) Disable Power-Up In Standby feature set (see 7.47.7) Reserved Obsolete If the device implements the CFA feature set, then this subcommand is reserved for CFA. Otherwise, this subcommand is reserved for ANSI INCITS TR27-2001. Disable CFA power mode 1 (see 7.47.9) Disable Write-Read-Verify feature set (see 7.47.10) Reserved Reserved for Serial ATA Reserved Obsolete Reserved Obsolete Obsolete Reserved Enable read look-ahead feature (see 7.47.13) Obsolete Reserved Obsolete Reserved Reserved for e06144 Disable Automatic Acoustic Management feature set (see 7.47.11) Reserved Enable reverting to power-on defaults Reserved Vendor Specific Disable release interrupt (see 7.47.14) Disable SERVICE interrupt (see 7.47.15) Reserved for DT1825 Vendor Specific Reserved Reserved for assignment by the CompactFlash Association
181
Devices implementing the CFA feature set shall support 8-bit PIO data transfers. Devices not implementing the CFA feature set shall not support 8-bit PIO data transfers. See the CFA specification for more information 7.47.4 Enable/disable write cache Subcommand codes 02h and 82h allow the host to enable or disable write cache in devices that implement write cache. When the subcommand disable write cache is issued, the device shall initiate the sequence to flush cache to non-volatile memory before command completion (see 7.14). These subcommands may affect caching for commands in the Streaming feature set. 7.47.5 Set transfer mode A host selects the transfer mechanism by Set Transfer Mode, subcommand code 03h, and specifying a value in the Count field. The upper 5 bits define the type of transfer and the low order 3 bits encode the mode value. The host may change the selected modes by the SET FEATURES command. Table 34 Transfer mode values Mode PIO default mode PIO default mode, disable IORDY PIO flow control transfer mode Retired Multiword DMA mode Ultra DMA mode Reserved Mode = transfer mode number Bits (7:3) 00000b 00000b 00001b 00010b 00100b 01000b 10000b Bits (2:0) 000b 001b mode N/A mode mode N/A
If a device supports this standard, and receives a SET FEATURES command with a Set Transfer Mode parameter and a Count field value of 00000000b, the device shall set the default PIO mode. If the value is 00000001b and the device supports disabling of IORDY, then the device shall set the default PIO mode and disable IORDY. A device shall support all PIO modes below the highest mode supported, e.g., if PIO mode 1 is supported PIO mode 0 shall be supported. Support of IORDY is mandatory when PIO mode 3 or above is the current mode of operation. A device shall support all Multiword DMA modes below the highest mode supported, e.g., if Multiword DMA mode 1 is supported Multiword DMA mode 0 shall be supported. A device shall support all Ultra DMA modes below the highest mode supported, e.g., if Ultra DMA mode 1 is supported Ultra DMA mode 0 shall be supported. If an Ultra DMA mode is enabled any previously enabled Multiword DMA mode shall be disabled by the device. If a Multiword DMA mode is enabled any previously enabled Ultra DMA mode shall be disabled by the device. For PATA systems using a cable assembly, the host should determine that an 80-conductor cable assembly is connecting the host with the device(s) before enabling any Ultra DMA mode greater than 2 in the device(s). 7.47.6 Enable/disable advanced power management Subcommand code 05h allows the host to enable Advanced Power Management. To enable Advanced Power Management, the host writes the Count field with the desired advanced power management level and then executes a SET FEATURES command with subcommand code 05h. The power management level is a scale
182
T13/1699-D Revision 3f
from the lowest power consumption setting of 01h to the maximum performance level of FEh. Table 35 shows these values. Table 35 Advanced power management levels Count Field FEh 81h-FDh 80h 02h-7Fh 01h FFh 00h Level Maximum performance Intermediate power management levels without Standby Minimum power consumption without Standby Intermediate power management levels with Standby Minimum power consumption with Standby Reserved Reserved
Device performance may increase with increasing power management levels. Device power consumption may increase with increasing power management levels. The power management levels may contain discrete bands. For example, a device may implement one power management method from 80h to A0h and a higher performance, higher power consumption method from level A1h to FEh. Advanced power management levels 80h and higher do not permit the device to spin down to save power. Subcommand code 85h disables Advanced Power Management. Subcommand 85h may not be implemented on all devices that implement SET FEATURES subcommand 05h. 7.47.7 Enable/disable Power-Up In Standby feature set Subcommand code 06h enables the Power-Up In Standby feature set. When this feature set is enabled, the device shall power-up into Standby mode, i.e., the device shall be ready to receive commands but shall not spin-up (see 4.17). Once this feature set is enabled, it shall only be disabled by a subsequent SET FEATURES command disabling the feature set (i.e., the feature set shall not be disabled after a power-on reset, a hardware reset, or a software reset). Subcommand code 86h disables the Power-Up In Standby feature set. When this feature set is disabled, the device shall power-up into Active mode. The factory default for this feature set shall be disabled. 7.47.8 Power-Up In Standby feature set device spin-up Subcommand code 07h shall cause a device that has powered-up into Standby to go to the Active state (see 4.17 and figure 7). 7.47.9 Enable/disable CFA power mode 1 Subcommand code 0Ah causes a CFA device to transition to CFA Power Mode 1. CFA devices may consume up to 500 mA maximum average RMS current for either 3.3 V or 5 V operation in Power Mode 1. Subcommand 8Ah causes a CFA device to transition to CFA Power Mode 0. CFA devices may consume up to 75 mA maximum average RMS current for 3.3 V or 100 mA maximum average RMS current for 5 V operation in Power Mode 0. If a CFA device is in CFA Power Mode 0, then the device shall transition to CFA Power Mode 1 during processing of a power-on reset or a hardware reset. If a CFA device is in CFA Power Mode 0 and in the Reverting to defaults enabled mode (see 7.51.17), then the device shall transition to CFA Power Mode 1 during processing of a software reset. If a CFA device is in CFA Power Mode 0 and in the Reverting to defaults disabled mode (see 7.51.17), then the device shall not transition to CFA Power Mode 1 during processing of a software reset. Enabling CFA Power Mode 1 does not cause a spin-up. A device in Power Mode 0 the device shall accept the following commands: a) IDENTIFY DEVICE b) SET FEATURES (function codes 0Ah and 8Ah) c) STANDBY Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) 183
T13/1699-D Revision 3f d) e) f) g) h) STANDBY IMMEDIATE SLEEP CHECK POWER MODE EXECUTE DEVICE DIAGNOSTICS CFA REQUEST EXTENDED ERROR
A device in Power Mode 0 may accept any command that the device is capable of executing within the Power Mode 0 current restrictions. Commands that require more current than specified for Power Mode 0 shall be rejected with an abort error. 7.47.10 Enable/Disable Write-Read-Verify feature set Subcommand code 0Bh enables the Write-Read-Verify feature set. Bits (7:0) of the LBA field in the SET FEATURES command specify the Write-Read-Verify mode. Table 36 defines the Write-Read-Verify modes.. Table 36 Write-Read-Verify Sector Counts Description Always enabled (i.e., the device shall perform a Write-Read-Verify for all sectors for all write commands). 01h The device shall perform a Write-Read-Verify on the first 65,536 logical sectors written by the host after: a) spin-up; or b) the device completes a SET FEATURES command setting the Write-Read-Verify mode without error. 02h The number of logical sectors on which a device performs a Write-Read-Verify is vendor specific. 03h The device shall perform a Write-Read-Verify on the first (number specified by the Count field in the SET FEATURES command x 1024) logical sectors written by the host after: a) spin-up; or b) the device completes a SET FEATURES command setting the Write-Read-Verify mode without error. 04h-FFh Reserved Note 1 - When Mode 03h is not selected, the Count field is ignored Subcommand code 8Bh disables the Write-Read-Verify feature set. A device shall set the Write-Read-Verify feature set to its factory default setting during processing of a power-on reset or a hardware reset. If a device is in the reverting to defaults enabled mode (see 7.47.16), then the device shall set the Write-Read-Verify feature set to its factory default setting during processing of a software reset. If a device is in the reverting to defaults disabled mode (see 7.47.16), then the device shall not change the settings of the Write-Read-Verify feature set during processing of a software reset. 7.47.11 Enable/disable Automatic Acoustic Management Subcommand code 42h allows the host to enable the Automatic Acoustic Management feature set. To enable the Automatic Acoustic Management feature set, the host writes the Count field with the requested automatic acoustic management level and executes a SET FEATURES command with subcommand code 42h. The acoustic management level is selected on a scale from 01h to FEh. Table 37 shows the acoustic management level values. Mode 00h
184
T13/1699-D Revision 3f
Enabling or disabling of the Automatic Acoustic Management feature set, and the current automatic acoustic management level setting shall be preserved by the device across all forms of reset, i.e. power-on, hardware, and software resets. Table 37 Automatic acoustic management levels Count Field FFh FEh 81h-FDh 80h 01h-7Fh 00h Level Reserved Maximum performance Intermediate acoustic management levels Minimum acoustic emanation level Retired Vendor Specific
Device performance may increase with increasing acoustic management levels. Device power consumption may decrease with decreasing acoustic management levels. The acoustic management levels may contain discrete bands. For example, a device may implement one acoustic management method from 80h to BFh and a higher performance, higher acoustic management method from level C0h to FEh. Upon successful completion of this SET FEATURES subcommand, IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data word 94, bits (7:0) shall be updated by the device. If the command is aborted by the device, the previous automatic acoustic management state shall be retained. Subcommand code C2h disables the Automatic Acoustic Management feature set. Devices that implement SET FEATURES subcommand 42h are not required to implement subcommand C2h. If device successfully completes execution of this subcommand, then the acoustic behavior of the device shall be vendor-specific, and the device shall return zeros in bits (7:0) of word 94 and bit 9 of word 86 of the IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data. Upon completion of SET FEATURES subcommands 42h and C2h, the device may update words (97:96) and word 104 in IDENTIFY DEVICE or IDENTIFY PACKET DEVICE data, and the contents of the Stream Performance Parameters Log in the READ LOG EXT command. 7.47.12 Set Maximum Host Interface Sector Times Subcommand code 43h allows the host to inform the device of a host interface rate limitation. This information shall be used by the device to meet the Command Completion Time Limits of the commands of the streaming feature set. To inform the device of a host interface rate limitation, the host writes the value of its Typical PIO Host Interface Sector Time to the Count field (7:0) and LBA (7:0) field and writes the value of its Typical DMA Host Interface Sector Time to the LBA (23:8) field. The Typical Host Interface Sector Times have the same units as IDENTITY DEVICE data word 96 for DMA and word 104 for PIO. A value of zero indicates that the host interface shall be capable of transferring data at the maximum rate allowed by the selected transfer mode. The Typical PIO Mode Host Interface Sector Time includes the hosts interrupt service time. Upon completion of SET FEATURES subcommand 43h, the device may adjust IDENTIFY DEVICE data words (97:96), and the contents of the Stream Performance Parameters Log in the READ LOG EXT command to allow for the specified host interface sector time. Field Count LBA Bits 15:8 7:0 47:24 23:8 7:0 Description Reserved Typical PIO Mode Host Interface Sector Time (7:0) Reserved Typical DMA Mode Host Interface Sector Time Typical PIO Mode Host Interface Sector Time (15:8)
7.47.13 Enable/disable read look-ahead Subcommand codes AAh and 55h allow the host to request the device to enable or disable read look-ahead. Error recovery performed by the device is vendor specific.
185
Subcommand codes 5Dh and DDh allow a host to enable or disable the asserting of Interrupt Pending when a device releases the bus for a TCQ command. 7.47.15 Enable/disable SERVICE interrupt Subcommand codes 5Eh and DEh allow a host to enable or disable the asserting of an Interrupt Pending when DRQ is set to one in response to a SERVICE command. 7.47.16 Enable/disable reverting to defaults Subcommand codes CCh and 66h allow the host to enable or disable the reverting to defaults mode. A device is in the reverting to defaults disabled mode after completing a SET FEATURES command with subcommand code 66h without error. In this mode a device shall not reset parameters to their default power-on values during the processing of a software reset. A device is in the Reverting to defaults enabled mode after the device: a) processes a power-on reset or hardware reset; or b) completes a SET FEATURES command with subcommand CCh without error. A device in the reverting to defaults enabled mode may reset parameters to their default power-on values during the processing of a software reset 7.47.17 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description Subcommand Code - Table 33 defines the value of the subcommand. Subcommand specific Subcommand specific Bit 15 14 13 12 11:8 05h Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
7:0 EFh
7.47.18 Normal Outputs See table 79. 7.47.19 Error Outputs Abort shall be set to one if any subcommand input value is not supported or is invalid. See table 100.
186
T13/1699-D Revision 3f
187
T13/1699-D Revision 3f 7.48.2 SET MAX ADDRESS - F9h 7.48.2.1 Feature Set
This command is mandatory for devices that implement the Host Protected Area feature set. This command shall not be implemented if the Removable feature set is implemented. 7.48.2.2 Description After successful command completion, all read and write access attempts to addresses greater than specified by the successful SET MAX ADDRESS command shall be rejected with an ID Not Found error (see 6.2.4). IDENTIFY DEVICE data words (61:60) shall reflect the maximum address set with this command. If the 48-bit Address feature set is supported, the value placed in IDENTIFY DEVICE data words (103:100) shall be the same as the value placed in IDENTIFY DEVICE data words (61:60). A host should not issue more than one non-volatile SET MAX ADDRESS or SET MAX ADDRESS EXT command after a power-on or hardware reset. Devices should report an IDNF error upon receiving a second non-volatile SET MAX ADDRESS command after a power-on or hardware reset. The contents of IDENTIFY DEVICE data words and the max address shall not be changed if a SET MAX ADDRESS command fails. After a successful SET MAX ADDRESS command using a new maximum LBA the content of all IDENTIFY DEVICE data words shall comply with 4.10.4 and the content of IDENTIFY DEVICE data words (61:60) shall be equal to the new Maximum LBA + 1. A successful READ NATIVE MAX ADDRESS command should immediately precede a SET MAX ADDRESS command. If the SET MAX ADDRESS command is not preceeded by a successful READ NATIVE MAX ADDRESS command, the device may abort the SET MAX ADDRESS command or execute one of the following commands: SET MAX SET PASSWORD, SET MAX LOCK, SET MAX UNLOCK, SET MAX FREEZE LOCK. The result depends on the value of the Feature field. Issuing a SET MAX ADDRESS to the value returned by READ NATIVE MAX ADDRESS shall clear the HPA regardless of the maximum logical block address.
188
December 11, 2006 7.48.2.3 Inputs 7.48.2.3.1 Overview Word 00h 01h Name Feature Count Description N/A Bit Description 16:1 N/A 0 Volatile_Value (V_V) - See 7.48.2.3.2. 02h 03h 04h 05h LBA (MSB) SET MAX LBA Bits 47:28 shall be cleared to zero. Description Obsolete Shall be set to one Obsolete Transport Dependent - See 6.1.9 Reserved
T13/1699-D Revision 3f
(LSB)
7:0 F9h
7.48.2.3.2 Volatile_Value (V_V) If V_V is set to one, then, during processing of a power-on reset or a hardware reset, a device shall not change the content in words 60-61 (see 7.16.7.21) or 100-103 (see 7.16.7.47) in the IDENTIFY DEVICE data. If V_V is cleared to zero, then, during processing of a power-on reset or a hardware reset, a device shall change the content in words 60-61 and words 100-103 in the IDENTIFY DEVICE data to be a value one greater than the value of either: a) the value in the SET MAX LBA field in the most recent SET MAX ADDRESS or SET MAX ADDRESS EXT command that completed without error in which V_V was set to one; or b) if no SET MAX ADDRESS or SET MAX ADDRESS EXT command has completed without error, then the native max address. Regardless of the setting of V_V, a device shall not change the content in words 60-61 or 100-103 in IDENTIFY DEVICE data during processing of a software reset. 7.48.2.4 Normal Outputs See Table 89. LBA bits 47:28 shall be cleared to zero. 7.48.2.5 Error Outputs If this command is not supported, the maximum value to be set exceeds the capacity of the device, a host protected area has been established by a SET MAX ADDRESS EXT command, or the device is in the Set_Max_Locked or Set_Max_Frozen state, then the device shall return command aborted. ID Not Found shall be set to one if the command was the second non-volatile SET MAX ADDRESS or SET MAX ADDRESS EXT command after power-on or hardware reset. Abort shall be set to one if the maximum value requested exceeds the device capacity, a host protected area has been established by a SET MAX ADDRESS EXT command, the device is in the Set_Max_Locked or Set_Max_Frozen state, or the command is not immediately preceded by a READ NATIVE MAX ADDRESS command. See table 108.
189
T13/1699-D Revision 3f 7.48.3 SET MAX FREEZE LOCK F9h/04h, Non-data 7.48.3.1 Feature Set
This command is mandatory for devices that implement the Host Protected Area feature set. This command shall not be implemented if the Removable feature set is implemented. 7.48.3.2 Description The SET MAX FREEZE LOCK command sets the device to Set_Max_Frozen state. After command completion any subsequent SET MAX commands shall be command aborted. Commands disabled by SET MAX FREEZE LOCK are: a) b) c) d) SET MAX ADDRESS SET MAX SET PASSWORD SET MAX LOCK SET MAX UNLOCK
This command shall not be immediately preceded by a READ NATIVE MAX ADDRESS command. If this command is immediately preceded by a READ NATIVE MAX ADDRESS command, it shall be interpreted as a SET MAX ADDRESS command. 7.48.3.3 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description 04h - SET MAX FREEZE LOCK N/A N/A Bit 15 14 13 12 11:8 05h Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
7:0 F9h
7.48.3.4 Normal Outputs See table 79. 7.48.3.5 Error Outputs Abort shall be set to one if the device is not in the Set_Max_Unlocked state. Seetable 101.
190
December 11, 2006 7.48.4 SET MAX LOCK - F9h/02h, Non-data 7.48.4.1 Feature Set
T13/1699-D Revision 3f
This command is mandatory for devices that implement the Host Protected Area feature set. This command shall not be implemented if the Removable feature set is implemented. 7.48.4.2 Description The SET MAX LOCK command sets the device into Set_Max_Locked state. After this command is completed any other SET MAX commands except SET MAX UNLOCK and SET MAX FREEZE LOCK shall be command aborted. The device shall remain in this state until a power cycle or command completion without error of a SET MAX UNLOCK or SET MAX FREEZE LOCK command. This command shall not be immediately preceded by a READ NATIVE MAX ADDRESS command. If this command is immediately preceded by a READ NATIVE MAX ADDRESS command, it shall be interpreted as a SET MAX ADDRESS command. 7.48.4.3 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description 02h - SET MAX LOCK N/A N/A Bit 15 14 13 12 11:8 05h Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
7:0 F9h
7.48.4.4 Normal Outputs See table 79. 7.48.4.5 Error Outputs Abort shall be set to one if the device is in the Set_Max_Locked or Set_Max_Frozen state. See table 101.
191
T13/1699-D Revision 3f 7.48.5 SET MAX SET PASSWORD - F9h/01h, PIO data-out 7.48.5.1 Feature Set
This command is mandatory for devices that implement the Host Protected Area feature set. This command shall not be implemented if the Removable feature set is implemented. 7.48.5.2 Description This command requests a transfer of a single 512-byte block of data from the host. Table 39 defines the content of this 512-byte block of data. The password is not retained by the device after the device has processed a power-on reset. When the device accepts this command the device is in Set_Max_Unlocked state. This command shall not be immediately preceded by a READ NATIVE MAX ADDRESS command. If this command is immediately preceded by a READ NATIVE MAX ADDRESS command, it shall be interpreted as a SET MAX ADDRESS command. 7.48.5.3 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description 01h - SET MAX PASSWORD N/A N/A Bit 15 14 13 12 11:8 05h Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
7:0 F9h
7.48.5.4 Normal Outputs See table 79. 7.48.5.5 Error Outputs Abort shall be set to one if the device is in the Set_Max_Locked or Set_Max_Frozen state. The device may return error status if an Interface CRC error has occurred. See table 108. 7.48.5.6 Output Data Structure Table 39 SET MAX SET PASSWORD data content Word 0 1-16 17-255 Content Reserved Password (32 bytes) Reserved
192
December 11, 2006 7.48.6 SET MAX UNLOCK - F9h/03h, PIO data-out 7.48.6.1 Feature Set
T13/1699-D Revision 3f
This command is mandatory for devices that implement the Host Protected Area feature set. This command shall not be implemented if the Removable feature set is implemented. 7.48.6.2 Description This command requests a transfer of a single 512-byte block of data from the host. Table 39 defines the content of this data. The password supplied in the data transferred shall be compared with the stored SET MAX password. If the password compare fails, then the device shall return command aborted and decrement the unlock counter. On the acceptance of the SET MAX LOCK command, this counter is set to a value of five and shall be decremented for each password mismatch when SET MAX UNLOCK is issued and the device is locked. When this counter reaches zero in a device, then the device shall return command aborted for all subsequent SET MAX UNLOCK commands until after the device has processed a power-on reset. If the password compare matches, then the device shall make a transition to the Set_Max_Unlocked state and all SET MAX commands shall be accepted. This command shall not be immediately preceded by a READ NATIVE MAX ADDRESS command. If this command is immediately preceded by a READ NATIVE MAX ADDRESS command, it shall be interpreted as a SET MAX ADDRESS command. 7.48.6.3 Inputs Word 00h 01h 02h-04h 05h Name Feature Count LBA Device Description 03h - SET MAX UNLOCK N/A N/A Bit 15 14 13 12 11:8 05h Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
7:0 F9h
7.48.6.4 Normal Outputs See table 79. 7.48.6.5 Error Outputs Abort shall be set to one if the device is not in the Set_Max_Locked state. The device may return error status if an Interface CRC error has occurred. See table 101.
193
T13/1699-D Revision 3f
7:0 37h
194
T13/1699-D Revision 3f
B) if no SET MAX ADDRESS or SET MAX ADDRESS EXT command has completed without error, then the native max address; and b) change the content in words 60-61 in the IDENTIFY DEVICE data to be the value in words 100-103 in IDENTIFY DEVICE data or 0FFF_FFFFh, whichever is less. Regardless of the setting of V_V, a device shall not change the content in words 60-61 or 100-103 in the IDENTIFY DEVICE data during processing of a software reset. 7.49.4 Normal Outputs See table 93. 7.49.5 Error Outputs If this command is not supported, the maximum value to be set exceeds the capacity of the device, a host protected area has been established by a SET MAX ADDRESS command, the command is not immediately preceded by a READ NATIVE MAX ADDRESS EXT command, or the device is in the Set_Max_Locked or Set_Max_Frozen state, then the device shall return command aborted. ID Not Found shall be set to one if the command was the second non-volatile SET MAX ADDRESS or SET MAX ADDRESS EXT command after power-on or hardware reset. Abort shall be set to one if the maximum value requested exceeds the device capacity, a host protected area has been established by a SET MAX ADDRESS command, or the command is not immediately preceded by a READ NATIVE MAX ADDRESS EXT command. See table 121.
195
T13/1699-D Revision 3f
7:0 C6h
T13/1699-D Revision 3f
7:0 E6h
197
T13/1699-D Revision 3f
7.52 SMART
7.52.1 Overview Individual SMART commands are identified by the value placed in the Feature field. Table 40 shows these values. Table 40 SMART Feature field values Value 00h-CFh D0h D1h D2h D3h D4h D5h D6h D7h D8h D9h DAh DBh DCh-DFh E0h-FFh Command Reserved SMART READ DATA Obsolete SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE Obsolete SMART EXECUTE OFF-LINE IMMEDIATE SMART READ LOG SMART WRITE LOG Obsolete SMART ENABLE OPERATIONS SMART DISABLE OPERATIONS SMART RETURN STATUS Obsolete Reserved vendor specific
198
December 11, 2006 7.52.2 SMART DISABLE OPERATIONS - B0h/D9h, Non-data 7.52.2.1 Feature Set This command is mandatory for devices that implement the SMART feature set. 7.52.2.2 Description
T13/1699-D Revision 3f
This command disables all SMART capabilities within the device including any and all timer and event count functions related exclusively to this feature. After command acceptance the device shall disable all SMART operations. SMART data shall no longer be monitored or saved by the device. The state of SMART, either enabled or disabled, shall be preserved by the device across power cycles. After receipt of this command by the device, with the exception of SMART ENABLE OPERATIONS and the SCT Command Transport commands, all other SMART commands including SMART DISABLE OPERATIONS commands are disabled and invalid and shall be command aborted by the device.. 7.52.2.3 Inputs The Feature field shall be set to D9h. The LBA field (15:8) shall be set to 4Fh. The LBA field (23:16) shall be set to C2h. Word 00h 01h 02h-04h Name Feature Count LBA Description D9h - SMART DISABLE OPERATIONS N/A Bit 47:28 27:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Command 7.52.2.4 Normal Outputs See table 79. 7.52.2.5 Error Outputs Abort shall be set to one if SMART is not enabled, or if an input value is invalid. See table 100. 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved B0h Description Reserved N/A C24Fh N/A
199
T13/1699-D Revision 3f 7.52.3 SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE - B0h/D2h, Non-data 7.52.3.1 Feature Set This command is mandatory for devices that implement the SMART feature set. 7.52.3.2 Description
This command enables and disables the optional attribute autosave feature of the device. This command may either allow the device, after some vendor specified event, to save the device updated attribute values to non-volatile memory; or this command may cause the autosave feature to be disabled. The state of the attribute autosave feature (either enabled or disabled) shall be preserved by the device across power cycles. A value of zero written by the host into the devices Count field before issuing this command shall cause this feature to be disabled. Disabling this feature does not preclude the device from saving SMART data to non-volatile memory during some other normal operation such as during a power-on or power-off sequence or during an error recovery sequence. A value of F1h written by the host into the devices Count field before issuing this command shall cause this feature to be enabled. Any other meaning of this value or any other non-zero value written by the host into this field before issuing this command may differ from device to device. The meaning of any non-zero value written to this field at this time shall be preserved by the device across power cycles. If this command is not supported by the device, the device shall return command aborted upon receipt from the host. During execution of the autosave routine the device shall not set BSY to one nor clear DRDY to zero. If the device receives a command from the host while executing the autosave routine the device shall begin processing the command within two seconds.
200
December 11, 2006 7.52.3.3 Inputs Word 00h 01h Name Feature Count Description D2h - SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE Value 00h 01h-F0h F1h F2h-FFh 02h-04h LBA Bit 47:28 27:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Command 7.52.3.4 Normal Outputs See table 79. 7.52.3.5 Error Outputs 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved B0h Description Reserved N/A C24Fh N/A Description Disable attribute autosave Reserved Enable attribute autosave Reserved
T13/1699-D Revision 3f
Abort shall be set to one if SMART is not enabled, or if an input value is invalid. See table 100.
201
T13/1699-D Revision 3f 7.52.4 SMART ENABLE OPERATIONS - B0h/D8h, Non-data 7.52.4.1 Feature Set This command is mandatory for devices that implement the SMART feature set. 7.52.4.2 Description
This command enables access to all SMART capabilities within the device. Prior to receipt of this command SMART data are neither monitored nor saved by the device. The state of SMART (either enabled or disabled) shall be preserved by the device across power cycles. Once enabled, the receipt of subsequent SMART ENABLE OPERATIONS commands shall not affect any SMART data or functions. 7.52.4.3 Inputs Word 00h 01h 02h-04h Name Feature Count LBA Description D8h - SMART ENABLE OPERATIONS N/A Bit 47:28 27:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Command 7.52.4.4 Normal Outputs See table 79. 7.52.4.5 Error Outputs See table 100. 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved B0h Description Reserved N/A C24Fh N/A
202
December 11, 2006 7.52.5 SMART EXECUTE OFF-LINE IMMEDIATE - B0h/D4h, Non-data 7.52.5.1 Feature Set This command is optional for devices that implement the SMART feature set. 7.52.5.2 Description
T13/1699-D Revision 3f
This command causes the device to immediately initiate the optional set of activities that collect SMART data in an off-line mode and then save this data to the device's non-volatile memory, or execute a self-diagnostic test routine in either captive or off-line mode. Table 41 SMART EXECUTE OFF-LINE IMMEDIATE Subcommands Value 0 1 2 3 4 5-63 64-126 127 128 129 130 131 132 133-191 192-255 Description of subcommand to be executed Execute SMART off-line routine immediately in off-line mode Execute SMART Short self-test routine immediately in off-line mode Execute SMART Extended self-test routine immediately in off-line mode Execute SMART Conveyance self-test routine immediately in off-line mode Execute SMART Selective self-test routine immediately in off-line mode Reserved Vendor specific Abort off-line mode self-test routine Reserved Execute SMART Short self-test routine immediately in captive mode Execute SMART Extended self-test routine immediately in captive mode Execute SMART Conveyance self-test routine immediately in captive mode Execute SMART Selective self-test routine immediately in captive mode Reserved Vendor specific
7.52.5.3 Off-line mode The following describes the protocol for executing a SMART EXECUTE OFF-LINE IMMEDIATE subcommand routine (including a self-test routine) in the off-line mode. 1) The device shall execute command completion before executing the subcommand routine. 2) The device shall remain ready to receive a new command during execution of the subcommand routine. 3) If the device is in the process of performing the subcommand routine and is interrupted by any new command from the host except a SLEEP, SMART DISABLE OPERATIONS, SMART EXECUTE OFF-LINE IMMEDIATE, or STANDBY IMMEDIATE command, the device shall suspend or abort the subcommand routine and service the host within two seconds after receipt of the new command. After servicing the interrupting command from the host the device may immediately re-initiate or resume the subcommand routine without any additional commands from the host (see 7.52.6.6). 4) If the device is in the process of performing a subcommand routine and is interrupted by a SLEEP command from the host, the device may abort the subcommand routine and execute the SLEEP command. If the device is in the process of performing any self-test routine and is interrupted by a SLEEP command from the host, the device shall abort the subcommand routine and execute the SLEEP command. 5) If the device is in the process of performing the subcommand routine and is interrupted by a SMART DISABLE OPERATIONS command from the host, the device shall suspend or abort the subcommand routine and service the host within two seconds after receipt of the command. Upon receipt of the next SMART ENABLE OPERATIONS command the device may, either re-initiate the subcommand routine or resume the subcommand routine from where it had been previously suspended. 6) If the device is in the process of performing the subcommand routine and is interrupted by a SMART EXECUTE OFF-LINE IMMEDIATE command from the host, the device shall abort the subcommand routine and service the host within two seconds after receipt of the command. The device shall then service the new SMART EXECUTE OFF-LINE IMMEDIATE subcommand. Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) 203
T13/1699-D Revision 3f
7) If the device is in the process of performing the subcommand routine and is interrupted by a STANDBY IMMEDIATE or IDLE IMMEDIATE command from the host, the device shall suspend or abort the subcommand routine, and service the host within two seconds after receipt of the command. After receiving a new command that causes the device to exit a power saving mode, the device shall initiate or resume the subcommand routine without any additional commands from the host unless these activities were aborted by the host (see 7.52.6.2). 8) While the device is performing the subcommand routine it shall not automatically change power states (e.g., as a result of its Standby timer expiring). 9) If a test failure occurs while a device is performing a self-test routine the device may discontinue the testing and place the test results in the Self-test execution status byte (see table 42). 7.52.5.4 Captive mode When executing a self-test in captive mode, the device executes the self-test routine after receipt of the command. At the end of the routine the device places the results of this routine in the Self-test execution status byte (See table 42) and reports command completion. If an error occurs while a device is performing the routine the device may discontinue its testing, place the results of this routine in the Self-test execution status byte, and complete the command. 7.52.5.5 SMART off-line routine This routine shall only be performed in the off-line mode. The results of this routine are placed in the Off-line data collection status byte (see table 43). 7.52.5.6 SMART Short self-test routine Depending on the value in the LBA field (7:0), this self-test routine may be performed in either the captive or the off-line mode. This self-test routine should take on the order of ones of minutes to complete (see 7.52.6.2). 7.52.5.7 SMART Extended self-test routine Depending on the value in the LBA field (7:0), this self-test routine may be performed in either the captive or the off-line mode. This self-test routine should take on the order of tens of minutes to complete (see 7.52.6.2). 7.52.5.8 SMART Conveyance self-test routine Depending on the value in the LBA field (7:0), this self-test routine may be performed in either the captive or the off-line mode. This self-test routine is intended to identify damage incurred during transporting of the device. This self-test routine should take on the order of minutes to complete (see 7.52.6.2). 7.52.5.9 SMART Selective self-test routine The SMART Selective self-test routine is an optional self-test routine. If the routine is implemented, all features of the routine shall be implemented. Support for the routine is indicated in off-line data collection capabilities (see 7.52.6.6). When the value in the LBA field (7:0) is 4 or 132, the Selective self-test routine shall be performed. This self-test routine shall include the initial tests performed by the Extended self-test routine plus a selectable read scan. The host should not write the Selective self-test log while the execution of a Selective self-test command is in progress. The user may choose to do read scan only on specific areas of the media. To do this, user shall set the test spans desired in the Selective self-test log and set the flags in the Feature flags field of the Selective self-test log to indicate do not perform off-line scan. In this case, the test spans defined shall be read scanned in their entirety. The Selective self-test log is updated as the self-test proceeds indicating test progress. When all specified test spans have been completed, the test is terminated and the appropriate self-test execution status is reported in the SMART READ DATA response depending on the occurrence of errors. Figure 9 shows an example of a Selective self-test definition with three test spans defined. In this example, the test terminates when all three test spans have been scanned.
204
T13/1699-D Revision 3f
User LBA space LBA 0 Test span 1 Starting LBA for test span 1 Test span 2 Starting LBA for test span 2 Ending LBA for test span 2 Test span 3 Starting LBA for test span 3 Ending LBA for test span 3
LBA max
Figure 9 Selective self-test span example After the scan of the selected spans described above, a user may wish to have the rest of media read scanned as an off-line scan. In this case, the user shall set the flag to enable off-line scan in addition to the other settings. If an error occurs during the scanning of the test spans, the error is reported in the self-test execution status in the SMART READ DATA response and the off-line scan is not executed. When the test spans defined have been scanned, the device shall then set the off-line scan pending and active flags in the Selective self-test log to one, the span under test to a value greater than five, the self-test execution status in the SMART READ DATA response to 00h, set a value of 03h in the off-line data collection status in the SMART READ DATA response and shall proceed to do an off-line read scan through all areas not included in the test spans. This off-line read scan shall completed as rapidly as possible, no pauses between block reads, and any errors encountered shall not be reported to the host. Instead error locations may be logged for future reallocation. If the device is powered-down before the off-line scan is completed, the off-line scan shall resume when the device is again powered up. From power-up, the resumption of the scan shall be delayed the time indicated in the Selective self-test pending time field in the Selective self-test log. During this delay time the pending flag shall be set to one and the active flag shall be set to zero in the Selective self-test log. Once the time expires, the active flag shall be set to one, and the off-line scan shall resume. When the entire media has been scanned, the off-line scan shall terminate, both the pending and active flags shall be cleared to zero, and the off-line data collection status in the SMART READ DATA response shall be set to 02h indicating completion. During execution of the Selective self-test, the self-test executions time byte in the Device SMART Data Structure may be updated but the accuracy may not be exact because of the nature of the test span segments. For this reason, the time to complete off-line testing and the self-test polling times are not valid. Progress through the test spans is indicated in the selective self-test log. When bit 3 in the Selective self-test feature flags field is set to one (see A.13), a device shall continue processing the Selective self-test after processing a hardware reset or a software reset. When bit 3 in the Selective self-test feature flags field is cleared to zero, a device shall abort the Selective self-test during processing a hardware reset or a software reset. If a device receives a SMART EXECUTE OFF-LINE IMMEDIATE command with the Abort off-line test routine subcommand, then the device shall abort the Selective self-test. If a device receives a SMART EXECUTE OFF-LINE IMMEDIATE command specifying that the device perform a self-test while a selective self-test is in progress, the device shall abort the selective self-test process the specified self-test.
205
T13/1699-D Revision 3f 7.52.5.10 Inputs Word 00h 01h 02h-04h Name Feature Count LBA Description D4h - SMART EXECUTE OFF-LINE IMMEDIATE N/A Bit 47:28 27:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Command 7.52.5.11 Normal Outputs See table 90. 7.52.5.12 Error Outputs 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved B0h
Description Reserved N/A C24Fh Table 41 defines the subcommand that shall be executed
ID Not Found shall be set to one if SMART data sector was not found could not be found. Abort shall be set to one if SMART is not enabled or if a self-test fails while executing a sequence in captive mode. See table 110.
206
December 11, 2006 7.52.6 SMART READ DATA - B0h/D0h, PIO data-in 7.52.6.1 Feature Set This command is optional for devices that implement the SMART feature set. 7.52.6.2 Description This command returns the Device SMART data structure to the host.
T13/1699-D Revision 3f
Table 42 defines the 512 bytes that make up the Device SMART data structure. All multi-byte fields shown in this structure follow the byte ordering described in 3.2.8. Table 42 Device SMART data structure Byte 0-361 362 363 364-365 366 367 368-369 370 F/V X V X V X F F F Description Vendor specific Off-line data collection status Self-test execution status byte Total time in seconds to complete off-line data collection activity Vendor specific Off-line data collection capability SMART capability Error logging capability 7-1 Reserved 0 1=Device error logging supported Vendor specific Short self-test routine recommended polling time (in minutes) Extended self-test routine recommended polling time (7:0) in minutes. If FFh, use bytes 375 and 376 for the polling time. Conveyance self-test routine recommended polling time (in minutes) Extended self-test routine recommended polling time (7:0) in minutes Extended self-test routine recommended polling time (15:8) in minutes Reserved Vendor specific Data structure checksum
X F F F F F R X V
Key: F = the content of the byte is fixed and does not change. V = the content of the byte is variable and may change depending on the state of the device or the commands executed by the device. X = the content of the byte is vendor specific and may be fixed or variable. R = the content of the byte is reserved and shall be zero.
207
The value of the off-line data collection status byte defines the current status of the off-line activities of the device. Table 43 lists the values and their respective definitions. Table 43 Off-line data collection status byte values Value 00h or 80h 01h 02h or 82h 03h 04h or 84h 05h or 85h 06h or 86h 07h-3Fh 40h-7Fh 81h 83h 87h-BFh C0h-FFh Definition Off-line data collection activity was never started. Reserved Off-line data collection activity was completed without error. Off-line activity in progress. Off-line data collection activity was suspended by an interrupting command from host. Off-line data collection activity was aborted by an interrupting command from host. Off-line data collection activity was aborted by the device with a fatal error. Reserved Vendor specific Reserved Reserved Reserved Vendor specific
7.52.6.4 Self-test execution status byte The self-test execution status byte reports the execution status of the self-test routine. a) Bits (3:0) (Percent Self-Test Remaining) The value in these bits indicates an approximation of the percent of the self-test routine remaining until completion in ten percent increments. Valid values are 9 through 0. A value of 0 indicates the self-test routine is complete. A value of 9 indicates 90% of total test time remaining. b) Bits (7:4) (Self-test Execution Status) The value in these bits indicates the current Self-test Execution Status (see table 44). Table 44 Self-test execution status values Value 0 1 2 3 4 5 6 7 8 9-14 15 Description The previous self-test routine completed without error or no self-test has ever been run The self-test routine was aborted by the host The self-test routine was interrupted by the host with a hardware or software reset A fatal error or unknown test error occurred while the device was executing its self-test routine and the device was unable to complete the self-test routine. The previous self-test completed having a test element that failed and the test element that failed is not known. The previous self-test completed having the electrical element of the test failed. The previous self-test completed having the servo (and/or seek) test element of the test failed. The previous self-test completed having the read element of the test failed. The previous self-test completed having a test element that failed and the device is suspected of having handling damage. Reserved. Self-test routine in progress.
7.52.6.5 Total time to complete off-line data collection The total time in seconds to complete off-line data collection activity word specifies how many seconds the device requires to complete the sequence of off-line data collection activity. Valid values for this word are from 0001h to FFFFh. 208 Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS)
T13/1699-D Revision 3f
The following describes the definition for the off-line data collection capability bits. If the value of all of these bits is cleared to zero, then no off-line data collection is implemented by this device. Table 45 Offline Data Collection Capabilities Bit 7 6 5 Description Reserved Selective self-test implemented - If this bit is cleared to zero, the device does not implement the Selective self-test routine. If this bit is set to one, the device implements the Selective self-test routine. Conveyance self-test implemented - If this bit is cleared to zero, the device does not implement the Conveyance self-test routines. If this bit is set to one, the device implements the Conveyance self-test routines. Self-test implemented - If this bit is cleared to zero, the device does not implement the Short and Extended self-test routines. If this bit is set to one, the device implements the Short and Extended self-test routines. Off-line read scanning implemented - If this bit is cleared to zero, the device does not support off-line read scanning. If this bit is set to one, the device supports off-line read scanning. Abort/restart off-line by host - If this bit is set to one, then the device shall abort all off-line data collection activity initiated by an SMART EXECUTE OFF-LINE IMMEDIATE command upon receipt of a new command within 2 seconds of receiving the new command. If this bit is cleared to zero, the device shall suspend off-line data collection activity after an interrupting command and resume off-line data collection activity after some vendor-specified event. Vendor specific. EXECUTE OFF-LINE IMMEDIATE implemented - If this bit is set to one, then the SMART EXECUTE OFF-LINE IMMEDIATE command is implemented by this device. If this bit is cleared to zero, then the SMART EXECUTE OFF-LINE IMMEDIATE command is not implemented by this device.
3 2
1 0
7.52.6.7 SMART capabilities The following describes the definition for the SMART capabilities bits. a) Bit 0 - If this bit is set to one, the device saves SMART data prior to going into a power saving mode (Idle, Standby, or Sleep) or immediately upon return to Active or Idle mode from a Standby mode. If this bit is cleared to zero, the device does not save SMART data prior to going into a power saving mode (Idle, Standby, or Sleep) or immediately upon return to Active or Idle mode from a Standby mode. b) Bit 1 - This bit shall be set to one to indicate that the device supports the SMART ENABLE/DISABLE ATTRIBUTE AUTOSAVE command. c) Bits (15:2) (Reserved). 7.52.6.8 Self-test routine recommended polling time The self-test routine recommended polling time shall be equal to the estimated number of minutes that is the minimum recommended time before which the host should first poll check for test completion status. Actual test time could be several times this value. The host should wait at least this long before sending the first SMART READ DATA command to check for test completion status. Polling Checking before this time could extend the self-test execution time or abort the test depending on the state of bit 2 of the offline data capability bits. Subsequent checking by the host should be at a vendor specific interval. 7.52.6.9 Data structure checksum The data structure checksum is the two's complement of the sum of the first 511 bytes in the data structure. Each byte shall be added with unsigned arithmetic, and overflow shall be ignored. The sum of all 512 bytes shall be zero when the checksum is correct. The checksum is placed in byte 511.
209
T13/1699-D Revision 3f 7.52.6.10 Inputs Word 00h 01h 02h-04h Name Feature Count LBA Description D0h - SMART READ DATA N/A Bit 47:28 47:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Command 7.52.6.11 Normal Outputs See table 79. 7.52.6.12 Error Outputs 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved B0h Description Reserved N/A C24Fh N/A
Uncorrectable Error shall be set to one if SMART data is uncorrectable. ID Not Found shall be set to one if SMART data sector was not found could not be found or a data structure checksum occurred. Abort shall be set to one if SMART is not enabled, or if field values are invalid. The device may return error status if an Interface CRC error has occurred. See table 118. NOTE 15 There is no defined mechanism for a device to return an ICRC error status that may have occurred during the last data block of a PIO-in data transfer; there may be other mechanisms in which a host may verify that an Interface CRC error occurred in these cases.
210
December 11, 2006 7.52.7 SMART READ LOG - B0h/D5h 7.52.7.1 Feature Set This command is optional for devices that implement the SMART feature set. 7.52.7.2 Description
T13/1699-D Revision 3f
This command returns the specified log to the host. See table 127 for the list of SMART log pages. See Annex A for the defintion of SMART log pages. 7.52.7.3 Inputs Word 00h 01h 02h-04h Name Feature Count LBA Bit 47:28 27:24 23:8 7:0 Description Reserved N/A C24Fh Log Address - Specifies the log to be read as described in table 127. See 7.28.3.3 for more information. Description D5h - SMART READ LOG Specifies the number of 512-byte blocks of data to be read from the specified log. The log transferred by the drive shall start at the first block in the specified log, regardless of the Count requested. A value of zero is illegal and shall result in command aborted. Bits 15:8 shall be cleared to zero.
05h
Device Bit 15 14 13 12 11:8 Command 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved B0h
7.52.7.4 Normal Outputs See table 79. 7.52.7.5 Error Outputs Uncorrectable Error shall be set to one if SMART data is uncorrectable. ID Not Found shall be set to one if SMART data sector was not found could not be found or a data structure checksum occurred. Abort shall be set to one if SMART is not enabled, if the count field is cleared to zero, or if field values are invalid. See table 118.
211
T13/1699-D Revision 3f 7.52.8 SMART RETURN STATUS - B0h/DAh, Non-data 7.52.8.1 Feature Set This command is mandatory for devices that implement the SMART feature set. 7.52.8.2 Description
This command causes the device to communicate the reliability status of the device to the host. If a threshold exceeded condition is not detected by the device, the device shall set the LBA field (15:8) to 4Fh and the LBA field (23:16) to C2h. If a threshold exceeded condition is detected by the device, the device shall set the LBA field (15:8) to F4h and the LBA field (23:16) to 2Ch. 7.52.8.3 Inputs Word 00h 01h 02h-04h Name Feature Count LBA Description DAh - SMART RETURN STATUS N/A Bit 47:28 27:24 23:8 7:0 Description Reserved N/A C24Fh Specifies the log to be returned as described in table 127. If this command is implemented, all address values for which the contents are defined shall be implemented and all address values defined as host vendor specific shall be implemented. The host vendor specific logs may be used by the host to store any data desired. If a host vendor specific log has never been written by the host, when read the content of the log shall be zeros. Device vendor specific logs may be used by the device vendor to store any data and need only be implemented if used.
05h
Device Bit 15 14 13 12 11:8 Command 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved B0h
7.52.8.4 Normal Outputs See table 91. 7.52.8.5 Error Outputs Abort shall be set to one if SMART is not enabled. See table 100.
212
December 11, 2006 7.52.9 SMART WRITE LOG - D6h, PIO data-out 7.52.9.1 Feature Set This command is optional for devices that implement the SMART feature set. 7.52.9.2 Description
T13/1699-D Revision 3f
This command writes the specified number of 512-byte block of data to the specified log. 7.52.9.3 Inputs 7.52.9.3.1 Overview The Feature field shall be set to D6h. The Count field shall specify the number of 512-byte blocks of data that shall be written to the log number specified by the LBA field (7:0). The LBA field (15:8) shall be set to 4Fh. The LBA field (23:16) shall be set to C2h. Word 00h 01h Name Feature Count Description D6h - SMART WRITE LOG Specifies the number of 512-byte blocks of data that shall be written to the specified log. The log transferred to the drive shall be stored by the drive starting at the first block in the specified log. A value of zero is illegal and shall result in command aborted. Bits 15:8 shall be cleared to zero Bit 47:28 27:24 23:8 7:0 Description Reserved N/A C24Fh Log Address - Specifies the log to be written as described in table 127. See 7.52.9.3.2 for more information.
02h-04h
LBA
05h
Device Bit 15 14 13 12 11:8 Command 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved B0h
7.52.9.3.2 Log Address A device may support a subset of the available logs. Support for individual logs is determined by support for the associated feature set. Support of the associated log(s) is mandatory for devices implementing the associated feature set. If this command is implemented, all address values defined as host vendor specific shall be implemented, see A.8 for more information on Host Vendor Specific logs. See A.9 for information regarding Device Vendor Specific logs. If the host attempts to write to a read only (RO) log address, the device shall return command aborted. 7.52.9.4 Normal Outputs See table 79. 7.52.9.5 Error Outputs ID Not Found shall be set to one if SMART log sector was not found could not be found. Abort shall be set to one if SMART is not enabled, if the log sector address is not implemented, or if the count field is cleared to zero. The device may return error status if an Interface CRC error has occurred. See table 109.
213
T13/1699-D Revision 3f
214
T13/1699-D Revision 3f
215
T13/1699-D Revision 3f
216
December 11, 2006 7.55.3 Inputs 7.55.3.1 Overview Word 00h Name Feature Bit 15:8 7:0 01h Count Bit 15:8 7:0 02h-04h LBA Bit 47:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Command 7.55.3.2 Security_Protocol 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved 5Ch Description Reserved Transfer_Length (7:0) Description Description Reserved Security_Protocol (see 7.55.3.2)
T13/1699-D Revision 3f
Description Reserved Sp_Specific - Security Protocol Specific (see 7.55.6) Transfer_Length (15:8)
The Security_Protocol field identifies which security protocol is being used. This determines the format of the command block parameters and of the data that is transferred (see table 46). If the Security_Protocol field is set to a reserved value, the device shall return command aborted. Table 46 TRUSTED RECEIVE Security_Protocol field description Value 00h 01h 06h 07h 1Fh 20h 21h-EDh EEh EFh F0h FFh Description Return security protocol information (see 7.55.6) Defined by TCG, see 7.55.6 Reserved. Reserved for T10 Reserved Defined by IEEE P1667 Reserved for T10 Vendor Specific.
The meaning of the security protocol-specific fields are defined by each security protocol. 7.55.4 Normal outputs See table 79
217
The device shall return command aborted if the command is not supported or if an unrecoverable error occurred during the execution of the command. The amount of data transferred is indeterminate. See table 100. 7.55.6 Command Block Parameters for Security_Protocol 00h - 06h 7.55.6.1 Overview The SP_Specific field provides Security_Protocol field specific information. The meaning of these fields are defined by each security protocol. For Security_Protocol field set to 00h, see 7.55.6.2. The Transfer_Length field contains the number of 512-byte blocks of data to be transferred. (One means 512 bytes, two means 1024 bytes, etc.) A Transfer_Length value of zero specifies that no data shall be transferred. This condition shall not be considered an error. The total data length shall conform to the Transfer_Length field requirements (e.g. the total data length shall be a multiple of 512). Pad bytes shall be added as needed to meet this requirement. Pad bytes shall have a value of 00h. If the length of the TRUSTED RECEIVE parameter data is greater than the Transfer_Length, then the device shall return the TRUSTED RECEIVE parameter data truncated to the requested Transfer_Length. 7.55.6.2 Security_Protocol 00h Description The purpose of Security_Protocol 00h is to return basic information about the device. A TRUSTED RECEIVE using Security_Protocol field set to 00h is not linked to an earlier TRUSTED SEND command. When the Security_Protocol field is set to 00h, the SP_Specific field is shown in table 47. Table 47 Security_Protocol 00h - SP_Specific field descriptions for Protocol 00h SP_Specific 0000h 0001h 0002h-FFFFh Description Return supported security protocol list Return a certificate Reserved Reference Support Mandatory Mandatory
If the SP_Specific field is set to a reserved value, the command shall be aborted. Each time a TRUSTED RECEIVE command with Security_Protocol field set to 00h is received, the device shall transfer the data starting with byte 0.
218
T13/1699-D Revision 3f
When the Security_Protocol field is set to 00h, and SP_Specific is set to 0000h in a TRUSTED RECEIVE command, the parameter data shall have the format shown in table 48. Table 48 TRUSTED RECEIVE parameter data for SP_Specific=0000h Bit Byte 0 1 2 3 4 5 6 7 8 M M+1 511 7 6 5 4 Reserved Reserved Reserved Reserved Reserved Reserved (MSB List Length Supported Security_Protocol List Pad bytes (if any) (LSB 3 2 1 0
The List Length field indicates the total length, in bytes, of the supported security protocol list. The Supported Security_Protocol List field shall contain a list of all supported Security_Protocol field values. Each byte indicates a supported Security_Protocol field value. The values shall be in ascending order starting with 00h. The total data length shall be 512 bytes. Pad bytes are appended as needed to meet this requirement. Pad bytes shall have a value of 00h. 7.55.6.4 Certificate data description 7.55.6.4.1 Certificate overview A certificate is either an X.509 Attribute Certificate or an X.509 Public Key Certificate depending on the capabilities of the device. When the Security_Protocol field of the TRUSTED RECEIVE command is set to 00h, and SP_Specific is 0001h, the parameter data shall have the format shown in table 49. Table 49 TRUSTED RECEIVE parameter data for SP_Specific=0001h Bit Byte 0 1 2 3 4 M M+1 511 7 6 5 4 Reserved Reserved (MSB) (MSB) CERTIFICATE LENGTH (M - 3) X.509 certificate bytes Pad bytes (if any) (LSB) 3 2 1 0
219
T13/1699-D Revision 3f
The CERTIFICATE LENGTH indicates the total length, in bytes, of the certificate(s). This length includes one or more certificates. If the device doesn't have a certificate to return, the certificate length is set to 0000h and only the 4 byte header and 508 pad bytes are returned. The contents of the certificate fields are defined in table 7.55.6.4.2 and table 7.55.6.4.3. The total data length shall conform to the Transfer_Length field requirements. 7.55.6.4.2 Public Key certificate description RFC 3280 defines the certificate syntax for certificates consistent with X.509v3 Public Key Certificate Specification. 7.55.6.4.3 Attribute certificate description RFC 3281 defines the certificate syntax for certificates consistent with X.509v2 Attribute Certificate Specification.
220
T13/1699-D Revision 3f
See 7.55.3 for a description of the inputs to this command 7.56.4 Normal Outputs See 7.55.4 for the normal outputs of this command 7.56.5 Error Outputs See 7.55.5 for the error outputs of this command.
221
T13/1699-D Revision 3f
222
December 11, 2006 7.57.3 Inputs 7.57.3.1 Overview Word 00h Name Feature Bit 15:8 7:0 01h Count Bit 15:8 7:0 02h-04h LBA Bit 47:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Command 7.57.3.2 Security_Protocol 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved 5Eh Description Reserved Transfer_Length (7:0) Description Description Reserved Security_Protocol (see 7.57.3.2)
T13/1699-D Revision 3f
Description Reserved Sp_Specific - Security Protocol Specific (see 7.57.6) Transfer_Length (15:8)
The Security_Protocol field identifies which security protocol is being used. This determines the format of the command block parameters and of the data that is transferred. (see table 50). If the Security_Protocol field is set to a reserved value, the device shall return command aborted. Table 50 TRUSTED SEND - Security_Protocol field description Value 00h 01h 06h 07h-1Fh 20h 21h EDh EEh EFh F0h FFh Description Reserved Defined by TCG Reserved Reserved for T10 Reserved Defined by IEEE P1667 Reserved for T10 Vendor Specific
The meaning of the security protocol-specific fields are defined by each security protocol. For Security_Protocol values 01h-06h, see 7.57.6.
223
T13/1699-D Revision 3f 7.57.4 Normal outputs See table 79 7.57.5 Error outputs
The device shall return command aborted if the command is not supported or if an unrecoverable error occurred during the execution of the command. The amount of data transferred is indeterminate. See table 100. 7.57.6 Command Block Parameters for Security_Protocol 01h - 06h 7.57.6.1 Overview The Transfer_Length Field contains the number of 512-byte blocks of data to be transferred. (One means 512 bytes, two means 1024 bytes, etc.). Pad bytes are appended to the valid data as needed to meet this requirement. Pad bytes shall have a value of 00h. A value of zero specifies that no data transfer shall take place, and shall not be considered to be an error. The SP_Specific field provides Security_Protocol field specific information. The meaning of this field is defined by each security protocol.
224
T13/1699-D Revision 3f
See 7.57.3 for a description of the inputs to this command 7.58.4 Normal Outputs See 7.57.4 for the normal outputs of this command 7.58.5 Error Outputs See 7.57.5 for the error outputs of this command.
225
T13/1699-D Revision 3f
226
T13/1699-D Revision 3f
Device
227
T13/1699-D Revision 3f
Device
228
T13/1699-D Revision 3f
Device
229
T13/1699-D Revision 3f
T13/1699-D Revision 3f
When the transfer of all requested data has occurred without error, the field content shall be as shown below. See table 88 for the layout of the Normal Outputs data structure. Release shall be cleared to zero, Input/Output Shall be set to one, Command/Data shall be set to one. 7.63.5 Error Outputs The Count field contains the Tag for this command if the device supports the TCQ feature set. The device shall return command aborted if the command is not supported. The device shall return command aborted if the device supports the TCQ feature set and the Tag is invalid. An unrecoverable error encountered during the execution of this command results in the termination of the command and the logical sector where the first unrecoverable error occurred is returned. Bits 47:48 of logical sector where the first unrecoverable error occurred shall be cleared to zero. If write cache is enabled unrecoverable errors may not be reliably reported as they may occur after the completion of the command. If a queue existed, the unrecoverable error shall cause the queue to abort. See table 123.
231
T13/1699-D Revision 3f
T13/1699-D Revision 3f
When the transfer of all requested data has occurred without error, the field content shall be as shown below. See table 94 for the layout of the Normal Outputs data structure. Release shall be cleared to zero, Input/Output Shall be set to one, Command/Data shall be set to one. 7.64.5 Error Outputs The Interrupt Reason field contains the Tag for this command if the device supports the TCQ feature set. The device shall return command aborted if the command is not supported. The device shall return command aborted if the device supports the TCQ feature set and the Tag is invalid. An unrecoverable error encountered during the execution of this command results in the termination of the command and the logical sector where the first unrecoverable error occurred is returned. If write cache is enabled unrecoverable errors may not be reliably reported as they may occur after the completion of the command. If a queue existed, the unrecoverable error shall cause the queue to abort. The device may remain BSY for some time when responding to these errors. See table 123.
233
T13/1699-D Revision 3f
234
T13/1699-D Revision 3f
7:0 3Fh
235
T13/1699-D Revision 3f
236
T13/1699-D Revision 3f
Device
237
T13/1699-D Revision 3f
occurred. The amount of data transferred is indeterminate. LBA field Bits 47:28 shall be cleared to zero. The device may return error status if an Interface CRC error has occurred. See table 122.
238
T13/1699-D Revision 3f
Device
239
T13/1699-D Revision 3f
occurred. The amount of data transferred is indeterminate. The device may return error status if an Interface CRC error has occurred. See table 111.
240
T13/1699-D Revision 3f
Device
241
T13/1699-D Revision 3f
Device
242
T13/1699-D Revision 3f
Device
243
T13/1699-D Revision 3f
The number of logical sectors to be transferred. A value of 0000h indicates that 65536 logical sectors are to be transferred. (MSB) Address of first logical sector to be transferred. (LSB) Bit 15 14 13 12 11:8 Description Obsolete Shall be set to one Obsolete Transport Dependent - See 6.1.9 Reserved 3Ah
Device
Command
7:0
7.73.3.2 Write Continuous (WC) WC specifies whether the Write Continuous mode is enabled or disabled. If WC is set to one, then: a) the device shall not stop processing the command due to errors; b) if an error occurs during data transfer or while writing data to media before command completion or before the amount of time allowed for command completion based on the setting of CCTL (see 7.36.3.2) or Default CCTL (see 7.9.3) is reached, then the device: 1) shall continue to transfer the amount of data requested; 2) may continue writing data to the media; 3) shall report command completion after all data for the command has been transferred; and 4) shall save the error information in the Write Streaming Error log; or c) if the amount of time allowed for command completion based on the setting of CCTL (see 7.36.3.2) or Default CCTL (see 7.9.3) is reached, then the device: 244 Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS)
December 11, 2006 1) 2) 3) 4) shall stop processing the command; shall report command completion; shall set CCTO in the Write Streaming Error log to one; and may continue writing data to the media.
T13/1699-D Revision 3f
If WC is cleared to zero and an error occurs, then the device: a) shall stop processing the command and report command completion; and b) may continue writing data to the media. 7.73.3.3 Flush If Flush is set to one, Default CCTL is cleared to zero, and CCTL is cleared to zero, then the device shall write all data for the specified stream to the media before command completion is reported. If Flush is set to one and Default CCTL was not cleared to zero in the most recent CONFIGURE STREAM command (see 7.9) for the Stream ID, then the device shall report command completion within the time specified by Default CCTL (see 7.9.3.4). If Flush is set to one and CCTL is not cleared to zero, then the device shall report command completion within (CCTL * (IDENTIFY DEVICE data words (99:98)) microseconds. If Flush is set to one and either Default CCTL was not cleared to zero in the most recent CONFIGURE STREAM command (see 7.9) for the Stream ID, or CCTL is not cleared to zero, then device: a) shall measure the time before reporting command completion from command acceptance; b) shall set CCTO to one if all of the data for the command has been received by the device, but the device has not yet written all of the data to its media; and c) should continue writing data to its media after reporting command completion. 7.73.3.4 Stream ID Stream ID specifies the stream to be written. The device shall operate according to the parameters specified by the most recent successful CONFIGURE STREAM command specifying this Stream ID. Any write to the device media or internal device buffer management as a result of the Stream ID is vendor specific. 7.73.4 Normal Outputs See table 83 for the definition of Normal Outputs. 7.73.5 Error Outputs If a) WC was set to one in the command, and b) the device is able to accept the amount of data requested for the command (e.g., an error occurred while writing to the media); then the device shall set SE to one and clear ERR to zero. If: a) WC was set to one in the command, and b) the device is not able to return the amount of data requested for the command (e.g., an ICRC error shall be reported at command completion); then the device shall clear SE to zero and set ERR to one; If: a) WC was cleared to zero in the command; b) CCTL was not cleared to zero in the command, or CCTL was cleared to zero in the command and Default CCTL specified in the most recent CONFIGURE STREAM command (see 7.9) for the Stream ID was not cleared to zero; and c) the time specified for command completion by CCTL (see 7.36.3.2) or Default CCTL (see 7.9.3) has been reached;
245
T13/1699-D Revision 3f
then the device shall clear SE to zero, set ERR to one, and set ABRT to one whether or not all data has been flushed to media. If: a) WC was cleared to zero in the command; b) CCTL was cleared to zero in the command; and c) Default CCTL specified in the most recent CONFIGURE STREAM command (see 7.9) for the Stream ID was cleared to zero; then the device shall clear SE to zero, set ERR to one, and set ICRC, IDNF, and/or ABRT to one (i.e., indicating the error type). See table 112 for the definition of other Error Outputs.
246
T13/1699-D Revision 3f
247
T13/1699-D Revision 3f
248
December 11, 2006 7.75.3 Inputs Word 00h Name Feature Description
T13/1699-D Revision 3f
Count LBA
Bit Description 15:8 Reserved 7:0 Uncorrectable options Value Description 00h-54h Reserved 55h Create a pseudo-uncorrectable error with logging 56h-59h Reserved 5Ah Create a pseudo-uncorrectable error without logging 5Bh-A4h Reserved A5h Created a flagged error with logging A6h-A9h Reserved AAh Create a flagged error without logging ABh-FFh Reserved The number of sectors to be marked. A value of 0000h indicates that 65,536 sectors are to be marked. (MSB) Address of first sector to be marked. (LSB) Bit 15 14 13 12 11:8 Description Obsolete Shall be set to one Obsolete Transport Dependent - See 6.1.9 Reserved
Device
Command 7.75.4 Normal Outputs See table 79. 7.75.5 Error Outputs See table 100.
7:0 45h
249
T13/1699-D Revision 3f
250
T13/1699-D Revision 3f
251
A device shall terminate the processing an SCT command during the processing of a software reset, hardware reset, or power-on reset. This could result in partial command execution or data loss. There is no indication once the device becomes ready that the previous command was terminated. A device shall clear the SCT Status Response fields (i.e., Extended Status Code, Action Code, and Function Code) during the processing of a power-on reset and a hardware reset. A device shall only clear the Extended status code during processing of a hardware reset or a software reset (i.e., the other content of the SCT Status Response fields shall not be affected by the device processing the reset).
252
T13/1699-D Revision 3f
8.2.2 SCT capability identification Capability Identification is performed by the host issuing an IDENTIFY DEVICE command to determine if the SCT Command Transport feature set is enabled and which Action Codes are supported (see 7.16.7.62). 8.2.3 SCT command transfer Transfer of an SCT command occurs when a 512-byte data packet is created by the host and written to log page E0h. The 512-byte data packet contains a single command as defined in the SCT Command Transport feature set. Table 51 defines how a host should set the fields to issue a SMART WRITE LOG command to send an SCT command. Table 51 Fields to issue an SCT command using SMART WRITE LOG Word 00h 01h Name Feature Count Description D6h - SMART WRITE LOG Bit Description 15:8 Reserved 7:0 01h 02h-04h LBA Bit 47:28 27:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Command 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved B0h - SMART Description Reserved N/A C24Fh E0h - Log Address
253
T13/1699-D Revision 3f
Table 52 defines how a host should set the fields to issue a WRITE LOG EXT command to send an SCT command. Table 52 Fields to issue an SCT command using WRITE LOG (DMA) EXT Word 00h 01h 02h-04h Name Feature Count LBA Description Reserved 0001h Bit 47:32 31:16 15:8 7:0 05h Device Bit 15 14 13 12 11:8 Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved 0000h Reserved E0 - Log Address
Table 53 defines how a device shall set the fields after successful completion of an SCT command. Table 53 Successful SCT command response Word 00h Name Error Description Bit Description 15:8 Reserved 7:0 00h 01h 02h-04h 05h Count LBA Device Reserved Reserved Bit 15 14 13 12 11:8 Status 7:6 Transport Dependent - See 6.1.9. 5:1 N/A 0 Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
254
T13/1699-D Revision 3f
Table 54 defines how a device shall set the fields after an error occurred during processing of an SCT command. Table 54 SCT command error response Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h Count Bit Description 15:8 Reserved 7:0 Extended Status Code (7:0) (see table 55) 02h-04h LBA Bit 47:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Status 7:6 Transport Dependent - See 6.1.9. 5:1 N/A 0 1b (Error - See 6.1.2) Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved SCT Command dependent. Extended Status Code (15:8) (see table 55) Description Reserved N/A ID Not Found - See 6.2.4. N/A Abort - See 6.2.1. N/A Obsolete
255
T13/1699-D Revision 3f Table 55 Extended Status codes Extended Status Code 0000h 0001h 0002h 0003h 0004h 0005h 0006h 0007h 0008h 0009h 000Ah 000Bh 000Ch 000Dh 000Eh 000Fh 0010h 0011h 0012h 0013h 0014h 0015h 0016h-BEFFh BF00h-BFFFh C000h-FFEFh FFF0h-FFFEh FFFFh Description
Command complete without error Invalid Function Code Input LBA out of range Request 512-byte data block count overflow. The number of data blocks requested to transfer (Count field) in the read or write log command is larger than required by SCT command Invalid Function code in Error Recovery command Invalid Selection code in Error Recovery command Host read command timer is less than minimum value Host write command timer is less than minimum value Background SCT command was aborted because of an interrupting host command Background SCT command was terminated because of unrecoverable error Invalid Function code in SCT Read/Write Long command SCT data transfer command was issued without first issuing an SCT command Invalid Function code in Feature Control command Invalid Feature code in Feature Control command Invalid New State value in Feature Control command Invalid Option Flags value in Feature Control command Invalid SCT Action code Invalid Table ID (table not supported) Command was aborted due to device security being locked Invalid revision code in SCT data Foreground SCT operation was terminated because of unrecoverable error The most recent non-SCT command was completed with an error due to the SCT Read Command Timer or Write Command Timer timing out. Reserved Reserved for Serial ATA Vendor specific Reserved SCT command executing in background
8.2.4 SCT data transfer Once an SCT command for a data transfer has been issued, status is checked and data is transferred using log page E1h. Up to 255 512-byte blocks of data of data may be transferred at a time. If the SCT command requires more than 255 blocks of data transfer and SMART READ LOG or SMART WRITE LOG commands are used to transfer the data, the data may be written or read in up to 255 data block increments. If READ LOG EXT or WRITE LOG EXT commands are used to transfer data, up to 65,535 512-byte data blocks (i.e., approximately 33MB) may be transferred by a single command. If more than 65,535 data blocks are required, then multiple
256
T13/1699-D Revision 3f
READ LOG EXT or WRITE LOG EXT commands may be issued. Table 56 defines how a host should set the fields for data transfer using a SMART READ LOG or SMART WRITE LOG command. Table 56 SCT data transfer using SMART READ LOG or SMART WRITE LOG Word 00h 01h Name Feature Count Description D5h/D6h (SMART READ LOG/SMART WRITE LOG subcommand code) Bit Description 15:8 Reserved 7:0 Number of 512-byte data blocks to transfer 02h-04h LBA Bit 47:28 27:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved N/A C24Fh E1h - Log Address
257
T13/1699-D Revision 3f
Table 57 defines the fields for data transfer using a READ LOG EXT or WRITE LOG EXT command. Table 57 SCT data transfer using READ LOG (DMA) EXT or WRITE LOG (DMA) EXT Word 00h 01h 02h-04h Name Feature Count LBA Description Reserved Number of 512-byte data blocks to transfer Bit 47:32 31:16 15:8 7:0 05h Device Bit 15 14 13 12 11:8 Command Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved 0000h Reserved E1 - Log Address
7:0 2Fh - READ LOG EXT/47h - READ LOG DMA EXT/3Fh - WRITE LOG EXT/57h - WRITE LOG DMA EXT
8.2.5 SCT status Status for an SCT command may be read at any time by reading log page E0h. If the command involves data transfer, the host should check status before data is transferred to ensure that the device is ready. The host should also check status when the command is complete to confirm that the data was transferred successfully. When the command is complete, the host may check status a third time to determine if the command succeeded, failed, or partially succeeded. Once an SCT command has been issued, status is reported in the ATA fields. This status indicates that the command was accepted or that an error occurred. This ATA status return does not indicate successful completion of the SCT actions, except Foreground LBA Segment Access commands that require the completion of the SCT action (e.g., LBA Segment Access with function code 0101h and 0102h). Some commands may take several minutes or even hours to execute. In this case, the host determines execution progress by requesting SCT status. Some commands may require setup time before they a device is ready to receive data. SCT status is used to determine when the device is read to receive data. Reading log page E0h retrieves the status information. The SCT status may be acquired any time that the host is allowed to send a command to the device. This command shall not change the power state of the device, nor terminate any background activity, including any SCT command in progress. This means if the device is in the Standby or Idle state, then the log request shall succeed.
258
T13/1699-D Revision 3f
Table 58 defines how a host should set the fields for retrieving status using a SMART READ LOG command. Table 58 SCT status request using SMART READ LOG Word 00h 01h Name Feature Count Description D5h (SMART READ LOG subcommand code) Bit Description 15:8 Reserved 7:0 01h 02h-04h LBA Bit 47:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Command 7:0 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved B0h - SMART Description Reserved C24Fh E0h (Log Address)
Table 59 defines the fields for retrieving status using a READ LOG EXT command. Table 59 SCT status request using READ LOG (DMA) EXT Word 00h 01h 02h-04h Name Feature Count LBA Description Reserved 0001h Bit 47:32 31:16 15:8 7:0 05h Device Bit 15 14 13 12 11:8 Command 7:0 Description Obsolete Shall be set to one Obsolete Transport Dependent - See 6.1.9 Reserved 2Fh - READ LOG EXT/47h - READ LOG DMA EXT Description Reserved 0001h Reserved E0 (Log Address)
259
T13/1699-D Revision 3f
Table 60 defines the format of the status response information that shall be set by the device in log page E0h. Table 60 Format of SCT status response Byte 0-1 2-3 4-5 6-9 Type Word Word Word DWord Field Name Format Version SCT Version SCT Spec. Status Flags Description 0002h - Status Response format version number. Manufacturers vendor specific implementation version number 0001h - Highest level of ATA8-ACS supported. Bit 0: Segment Initialized Flag. If this bit is set to 1, a Write Same command to all logical blocks has completed without error. This bit shall be cleared to 0 when any user LBA is written, even if write cache is enabled. This bit is also cleared if the capacity of the device is changed via SETMAX, SETMAX EXT or DCO. This bit is preserved through a power cycle. Bits 1-31: Reserved 0 = Active waiting for a command 1 = Stand-by 2 = Sleep 3 = DST executing in background 4 = SMART Off-line Data Collection executing in background 5 = SCT command executing in background Status of last SCT command issued. FFFFh if SCT command executing in background (see table 55). Action code of last SCT command issued. If the Extended Status Code is FFFFh this is the Action Code of the command that is currently executing Function code of last SCT command issued. If the Extended Status Code is FFFFh this is the Function Code of the command that is currently executing Current LBA of SCT command executing in background. If there is no command currently executing in the background, this field is undefined. Current device HDA temperature in degrees Celsius. This is a 2s complement integer. 80h indicates that this value is invalid. Minimum HDA temperature in degrees Celsius seen this power cycle. This is a 2s complement integer. 80h indicates that this value is invalid. Maximum HDA temperature in degrees Celsius seen this power cycle. This is a 2s complement integer. 80h indicates that this value is invalid. Minimum HDA temperature in degrees Celsius seen for the life of the device. This is a 2s complement integer. 80h indicates that this value is invalid. Maximum HDA temperature in degrees Celsius seen for the life of the device. This is a 2s complement integer. 80h indicates that this value is invalid.
10
Byte
Device State
18-19
Word
Function Code
20-39 40-47
reserved LBA
202
Byte
Max Temp
203
Byte
204
Byte
260
December 11, 2006 Table 60 Format of SCT status response Byte 205 206-209 Type Byte DWord Field Name reserved Over Limit Count Description
T13/1699-D Revision 3f
210-213
DWord
Number of temperature recording Intervals since the last power-on reset where the recorded temperature was greater than Max Op Limit. See table 75 for information about this Interval. Number of temperature recording Intervals since the last power-on reset where the recorded temperature was less than Min Op Limit. See table 75 for information about this Interval.
214-479 480-511
261
T13/1699-D Revision 3f
2-3
Function Code
4-x x+1 - y
Table 62 SCT Action Codes Action Code 0000h 0001h 0002h 0003h 0004h 0005h 0006h 0007h 0007h-BFFFh C000h-FFFFh Description Reserved SCT Read/Write Long Write Same Error Recovery Control Features Control SCT Data Tables Vendor specific Reserved for Serial ATA Reserved Vendor specific
262
T13/1699-D Revision 3f
The function performed by the SCT Read/Write Long command is based on the obsolete ATA READ LONG/WRITE LONG capability, and has been extended beyond 28-bit addressing. The SCT Read/Write Long data format for both reads and writes is two blocks long (i.e., each block is 512 bytes long). The first block contains the user data. The second data block contains the error correction and detection bytes. The remainder of the second block should contain zeros. Once the SCT command has been issued and the status response indicates that the device is ready to transfer data, log page E1h should be read or written to transfer the data. SCT Read/Write Long commands cause a forced unit access to occur. Table 63 defines the format of an SCT Read/Write Long command written to log page E0h. Table 63 SCT Read/Write Long command Word 0 1 2 Name Action Code Function Code LBA Value 0001h 0001h 0002h QWord Description Read or Write a sector with full ECC or CRC data Read Long function Write Long function Logical sector to be read or written
263
T13/1699-D Revision 3f Table 64 defines the format of the status response for an SCT Read/Write Long command. Table 64 SCT Read/Write Long command status response Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h Count Bit Description 15:8 Reserved 7:0 Number of ECC/CRC bytes, (7:0) 02h-04h LBA Bit 47:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Status 7:6 Transport Dependent - See 6.1.9. 5:1 N/A 0 Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved 0002h Number of 512-byte data blocks requested Number of ECC/RCR bytes, (15:8) Description Reserved N/A ID Not Found - See 6.2.4. N/A Abort - See 6.2.1. N/A Obsolete
264
T13/1699-D Revision 3f
Table 65 defines the format of the data to be written to log E1h for an SCT Read/Write Long command. Table 65 SCT Read/Write Long Format Field User Data Description First Block 512 This is the data normally sent or returned by a read or write command. This data may be encoded. Second Block Vendor Specific Error correction and detection bytes in vendor-specific format. The number of bytes is returned as status response data on both read and write operations. Remainder of block All zeros Size
ECC/CRC Data
Reserved
265
The Write Same command provides the ability for the host to specify that the device shall write a specific pattern to its media. The Write Same command shall cause the device to begin writing logical sectors from the first logical sector specified by the command in the Start field (see table 66) in incrementing order until the number of logical sectors specified by the command in the Count field (see table 66) have been written. If the Count field contains all zeros, then the device shall write all logical sectors beginning with the logical sector specified by the Start field through the last user LBA on the device. If the Host Protected Area feature set is implemented by and enabled on the device, then this feature set shall determine the last user LBA. This command shall not write over a hidden partition when hidden partitions are enabled using the Host Protected Area feature set. Automatic sector reassignment is permitted during the operation of this function. If the Start field or the Start field plus the Count field specify an LBA greater than the last user LBA, then the device shall report an error and abort the command. If the Start field and the Count field contain zero, then the device shall write the specified pattern to all user logical blocks on the device. Any new command other than an SCT status request, including IDENTIFY DEVICE, received by the device while this command is in progress shall terminate the Write Same command. The device shall process the new command. While a background Write Same command is in progress, the SCT status error code shall be set to FFFFh. If the command completes without error, then the SCT status error code shall be set to 0000h. The SCT status error code shall be set to a value less than FFFFh and greater than 0000h if the command is terminated prematurely for any reason. Once the key data block has been issued, if the Function Code was 0002h and the input data structure indicates that the drive is ready to receive data, log page E1h should be written to transfer the data. For the Foreground SCT LBA Segment Access command with function code 0101h the Command Completion Status of the Write Log Address E0h shall indicate the success or failure of the LBA Segment Access command. For the Foreground SCT LBA Segment Access command with function Code 0102h the Command Completion Status of the Write Log Address E1h shall indicate the success or failure of the LBA Segment Access command. The Status and Error fields indicate the relevant status/error values as defined in ATA/ATAPI-7 specification. In the case of an error an SCT Status Request may be made using a Smart Read Log page E0h to obtain a more detailed analysis of the error. This command may change the Segment Initialized Flag. If the command writes all the user addressable sectors and completes without encountering an error or being aborted, then the Segment Initialized Flag (i.e., bit 0 of the Status Flags in the SCT status) shall be set to one. A write to any user addressable sector on the device, except one caused by another Write Same command with the Start field and the Count field set to zero (i.e., an Write Same command causing the device to write to all user logical blocks), shall cause the Segment Initialized Flag to be cleared. Reallocations as a result of reading data (foreground or background) shall not clear the Device Zeroed flag.
266
December 11, 2006 Table 66 defines the format of a Write Same command written to log page E0h. Table 66 Write Same command Word 0 1 Name Action Code Function Code
T13/1699-D Revision 3f
Value Description 0002h This action writes a pattern or 512-byte data block repeatedly to the media. 0001h Repeat write pattern 0002h Repeat write data block 0003h-0100h Reserved 0101h Repeat write pattern foreground 0102h Repeat write data block foreground 0103h-FFFFh Reserved QWord First LBA QWord Number of logical sectors to fill DWord If the Function Code is 0001h or 0003h, this field contains a 32-bit pattern that is written on the media starting at the location specified in words two through five.
267
T13/1699-D Revision 3f Table 67 defines the format of the status response for a Write Same command. Table 67 Write Same command status response Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h 02h-04h Count LBA Reserved Bit 47:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Status 7:6 Transport Dependent - See 6.1.9 5:1 N/A 0 Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved 0001h Number of data blocks requested Reserved Description Reserved N/A ID Not Found - See 6.2.4. N/A Abort - See 6.2.1. N/A Obsolete
268
T13/1699-D Revision 3f
The Error Recovery Control command is used to set time limits for read and write error recovery. For non-queued commands, these timers apply to command completion at the host interface. For queued commands where in-order data delivery is enabled, these timers begin counting when the device begins to execute the command, not when the command is sent to the device. These timers do not apply to streaming commands or to queued commands when out-of-order data delivery is enabled. Time limits for error recovery may be used in a data redundant RAID environment where it is more desirable to have the device report a data error rather than risk having it being dropped from the RAID. The typical usage for this command is when an ATA or SATA device has its write cache function enabled. With write cache enabled, the device cannot report an error on a write command. This is because the write command with which a device is experiencing difficulty is one for which the device has reported status (i.e., considered by the host to be complete). This leaves no recourse for the device other than to reallocate any sectors with which it is experiencing difficulty. Table 68 defines the format of an Error Recovery Control command written to log page E0h. Table 68 Error Recovery Control command Word 0 1 2 3 Name Action Code Function Code Selection Code Recovery Time Limit Value 0003h 0001h 0002h 0001h 0002h Description Set the read and write error recovery time Set New Value Return Current Value Read Command Timer Write Command Timer If the function code is 0001h then this field contains the recovery time limit in 100 ms units (i.e., a value of 1 = 100 ms, 2 = 200 ms, etc.). The tolerance is vendor specific.
The Read Command Timer sets an upper limit for the amount of time a device processes a read command. This limit is the amount of time the device shall process a read command in total but, in some cases, a read command requires more than one access to the media. The minimum value for the Read Command Timer is one. Setting this value to zero shall disable Read Command time-out, allowing the device to perform all available error recovery procedures without time limit. If the Read Command Timer is going to expire while the device is performing error recovery, the device shall stop processing the command and report an uncorrectable ECC error for the LBA that was causing error recovery to be invoked prior to timer expiration. Extended status code 0015h shall be returned if the read command timer expires. The LBA may be recoverable given more time for error recovery. At this point the host may reconstruct the data for the failing LBA from the other devices in a RAID and issue a write command to the target LBA, allowing the device to attempt vendor specific error recovery on the suspect LBA. The Write Command Timer sets the upper limit for the amount of time a device processes a write command. The minimum value for this command is one. Setting this value to zero shall disable Write Command time-out, allowing the device to perform all available error recovery procedures without a time limit. The Write Command Timer has the effect of controlling how aggressively the device reallocates write data when encountering write errors. A large Write Command Timer value allows the device to use more available error recovery procedures for dealing with write errors. A small Write Command Timer value forces the device to attempt to reallocate sectors that may have otherwise been written without error. If the timer is about to expire, then the device should attempt to reallocate the data before the timer expires. Extended status code 0015h shall be returned if the write command timer expires. If the device is unable to complete data reallocation before the timer expires then the devices fails the command when the timer expires. When write cache is enabled the operation of the timer is vendor specific. A host implementer should use the Write Command Timer with great caution as a very small timer value could cause a device to permanently reallocate good sectors as the result of temporary, external conditions (e.g., induced vibration).
269
T13/1699-D Revision 3f
Read and Write Command Timer values are set to default values at power-on but may be altered by an SCT command at any time. A device shall not change these settings while processing a hardware reset or a software reset. Table 69 defines the format of the status response for a Error Recovery Control command. Table 69 Error Recovery Control command status response Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h 02h-04h Count LBA Bit Description 47:8 Reserved 7:0 If the Function Code was 0002h, then this is the requested recovery limit (15:8). Otherwise, this field is Reserved. 05h Device Bit 15 14 13 12 11:8 Status 7:6 Transport Dependent - See 6.1.9 5:1 N/A 0 Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved N/A ID Not Found - See 6.2.4. N/A Abort - See 6.2.1. N/A Obsolete
If Function Code was 0002h, then this is the requested recovery limit (7:0). Otherwise, this field is Reserved.
270
T13/1699-D Revision 3f
The Feature Control command is used to determine and set the state (i.e., enabled or disabled) of the features specified by the command. Table 70 defines the format of a Feature Control command written to log page E0h. Table 70 Feature Control command Word 0 1 Name Action Code Function Code Value 0004h 0001h 0002h 0003h Description Set or return the state of device features defined in table 71 Set state for a feature Return the current state of a feature Return feature option flags See table 71 for definition of the Feature Code Feature Code dependent value Bit Description 15:1 Reserved 0 If the function code is 0001h, setting bit 0 to one shall cause the requested feature state change to be preserved across power cycles. If the function code is 0001h, setting bit 0 to zero shall cause the requested feature state change to be volatile. A hard reset causes the device to revert to default, or last non-volatile setting.
2 3
271
Feature Code State Definition 0001h If State is set to 0001h, then the SET FEATURES command shall determine the state of write cache (see 7.47.4). If State is set to 0002h, then write cache shall be enabled. If State is set to 0003h, then write cache shall be disabled. If State is set to 0002h or 0003h, then write cache shall be set to the specified state, and any attempt to change the write cache settings using a SET FEATURES command shall not result in an error but shall not change the operational state of the write cache. In all cases, IDENTIFY DEVICE data word 85 bit 5 shall reflect the current operational state of write cache (i.e., if set to one, then write cache is enabled, and if set to zero, then write cache is disabled. The default is State set to 0001h. 0002h If State is set to 0001h, then Write Cache Reordering shall be enabled (i.e., disk write scheduling may be reordered by the device). If State is set to 0002h, then Write Cache Reordering shall be disabled, and disk write scheduling is executed on a first-in-first-out (FIFO) basis. If write cache is disabled, then the current Write Cache Reordering state is remembered but has no effect on non-cached writes, which are always written in the order received. The state of Write Cache Reordering has no effect on queued commands. The default is State set to 0001h. 0003h The value in State sets the time interval for temperature logging. State set to 0000h is invalid. State may be set to 0001h to FFFFh to specify the temperature logging interval in minutes This value applies to the Absolute HDA Temperature History queue. Issuing this command shall cause the queue to be reset and any prior values in the queues shall be lost. Queue Index shall be set to zero and the first queue location for shall be set to the current value. All remaining queue locations are set to 80h. The Sample Period, Max Op Limit, Over Limit, Min Op Limit and Under Limit values are preserved. The default is State set to 0001h. 0004h-0005h Reserved for Serial ATA 0006h-CFFFh Reserved D000h-FFFFh Vendor Specific
272
December 11, 2006 Table 72 defines the format of the status response for a Feature Control command. Table 72 Feature Control command status response Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h Count Description Reserved N/A ID Not Found - See 6.2.4. N/A Abort - See 6.2.1. N/A Obsolete
T13/1699-D Revision 3f
If the Function Code was set to 0002h this is the Feature State (7:0) If the Function Code was set to 0003h this is the Option Flags (7:0) Otherwise this field is reserved Bit Description 47:8 Reserved 7:0 If the Function Code was set to 0002h this is the Feature State (15:8) If the Function Code was set to 0003h this is the Option Flags (15:8) Otherwise this field is Reserved
02h-04h
LBA
05h
Device Bit 15 14 13 12 11:8 Status 7:6 Transport Dependent - See 6.1.9 5:1 N/A 0 Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
273
T13/1699-D Revision 3f 8.3.6 SCT Data Table command The SCT Data Table command is used to read the specified data table. Table 73 defines the format of an SCT Data Table command written to log page E0h. Table 73 SCT Data Table command Word 0 1 2 Name Action Code Function Code Table ID Value 0005h 0001h Word Description Read a data table Read Table See Table 74 for a list of data tables
Table 74 SCT Data Tables (by Table Identifier) Table Id 0000h 0001h 0002h 0003h-0004h 0003h-CFFFh D000h-FFFFh Description Invalid Reserved HDA Temperature History Table (in absolute degrees C). (See Table 75) Reserved for Serial ATA Reserved Vendor Specific
Table 75 Absolute HDA Temperature Byte 0-1 2-3 Size Word Word Field Name Format Version Sampling Period Description 0002h - Data table format version
4-5
Word
Byte
Byte
Byte
Absolute HDA Temperature sampling period in minutes. This is how often the device samples its temperature sensor. This period takes precedence over new read or write operations, but does not interrupt operations in process. The Sampling Period may be smaller that the timer interval between entries in the history queue. A value of 0000h in this field indicates that sampling is disabled. Interval The timer interval between entries in the history queue. The default value of this field is vendor specific. This value should not be less than the Sampling Period. Max Op Limit Maximum recommended continuous operating temperature (see Note 3). This is a one byte twos complement number that allows a range from -127 C to +127 C to be indicated. 80h is an invalid value. This is a fixed value. Over Limit Maximum temperature limit. Operating the device above this temperature may cause physical damage to the device (see Note 3). This is a one-byte twos complement number that allows a range from -127 C to +127 C to be indicated. 80h is an invalid value. This is a fixed value. Min Op Limit Minimum recommended continuous operating limit (see Note 3). This is a one byte 2s complement number that allows a range from -127 C to +127 C to be indicated. 80h is an invalid value. This is a fixed value.
274
December 11, 2006 Table 75 Absolute HDA Temperature Byte 9 Size Byte Field Name Under Limit
T13/1699-D Revision 3f
Description Minimum temperature limit. Operating the device below this temperature may cause physical damage to the device (see Note 3). This is a one-byte twos complement number that allows a range from -127 C to +127 C to be indicated. 80h is an invalid value. This is a fixed value. Number of entry locations in history buffer. This number shall be in the range of 128 to 478. Last updated entry in buffer. CB Index is zero-based, so CB Index 0000h is the first location in the buffer (i.e., at offset 34). The most recent temperature entered in the buffer is at CB Index + 34 (see Note 1 and Note 2). This is a circular buffer of absolute HDA Temperature values. Other device activities, such as data transfer, take priority over writing this data to non-volatile storage. These are one-byte twos complement numbers that allow a range from -127 C to +127 C to be indicated. A value of 80h indicates an initial value or a discontinuity in temperature recording. The time between samples may vary because commands shall not be interrupted. The sampling period is the minimum time between samples (see Note 1). If the host changes the logging interval using the volatile option, then the interval between entries in the queue may change between power cycles with no indication to the host. Shall be zero.
CB
Byte reserved [512 - CB Size - 34] Note 1 - The Absolute HDA Temperature History is preserved across power cycles with the requirement that when the device powers up, a new entry is made in the history queue with a value of 80h (i.e., an invalid absolute temperature value). This allows an application viewing the history to see the discontinuity in temperature resulting from the device being turned off. If the device does not sample temperatures during a certain power state (e.g., Sleep or Standby), then a value of 80h is entered into the history queue to indicate that temperature sensing has resumed. Note 2 - When the Absolute HDA Temperature history is cleared (e.g., for new devices or after changing the Logging Interval) the Queue Index shall be set to zero and the first queue location shall be set to the current Absolute HDA Temperature value. All remaining queue locations shall be set to 80h. Note 3 - These values should take into account the accuracy of the temperature sensor. The placement, accuracy, and granularity of temperature sensors to support table 75 are vendor specific.
275
T13/1699-D Revision 3f Table 76 defines the format of the status response for an SCT Data Table command. Table 76 Feature Control command status response Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h 02h-04h Count LBA Reserved Bit 47:24 23:8 7:0 05h Device Bit 15 14 13 12 11:8 Status 7:6 Transport Dependent - See 6.1.9 5:1 N/A 0 Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved 0001h Number of data blocks requested Reserved Description Reserved N/A ID Not Found - See 6.2.4. N/A Abort - See 6.2.1. N/A Obsolete
276
T13/1699-D Revision 3f
(LSB)
Device
277
Table 78 Error Bit Defined For Normal Output Word 00h 01h 02h-04h 05h Name Error Count LBA Device Description N/A N/A N/A Bit 15 14 13 12 11:8 Status 7:6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. Device Fault See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete Shall be set to one Obsolete Transport Dependent - See 6.1.9 Reserved
278
T13/1699-D Revision 3f
Reference: 7.10.4, 7.10.2, 7.10.3, 7.10.5, 7.12, 7.14, 7.16, 7.17, 7.18, 7.19, 7.21.9, 7.23, 7.24, 7.30, 7.34, 7.38, 7.40, 7.41, 7.42, 7.43, 7.44, 7.45, 7.47, 7.48.5, 7.48.4, 7.48.6, 7.48.3, 7.50, 7.51, 7.52.2, 7.52.3, 7.52.4, 7.52.6, 7.52.7, 7.52.9, 7.53, 7.54, 7.55, 7.57, 7.59, 7.60, 7.68, 7.71, 7.75
Table 79 Generic Normal Output (No LBA Return Value) Word 00h 01h 02h-04h 05h Name Error Count LBA Device Description N/A N/A N/A Bit 15 14 13 12 11:8 05h Status 7:6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. Device Fault See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
Table 80 CFA Normal Output Word 00h 01h 02h-04h 05h Name Error Count LBA Device Description N/A N/A N/A Bit 15 14 13 12 11:8 Status 7:6 5:1 0 Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
279
Table 81 Media Card Type Normal Output Word 00h 01h 02h-04h Name Error Count LBA Description N/A 0055h Bit 47:28 27 26:24 Description Reserved Write Protect - shall be set to one if the device is write protected, Write Protect shall be cleared to zero if the device is not write protected. Media Type Value Description 000b Reserved 001b SD Memory Card 010b MMC Card 011b SD-IO Card 100b Smart Media Card 101b-111b Reserved Card specific Data Shall be set to AAh
Transport Dependent - See 6.1.9 Device Fault - See 6.1.3 N/A Error - See 6.1.2
280
T13/1699-D Revision 3f
Table 82 Check Power Mode Normal Output Word 00h 01h Name Error Count Description N/A Value 00h 40h 41h 80h FFh 02h-04h 05h LBA Device Reserved Bit 15 14 13 12 11:8 Status 7:6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Device is in Standby mode. Device is in NV Cache Power Mode and the spindle is spun down or spinning down. device is in NV Cache Power Mode and the spindle is spun up or spinning up. Device is in Idle mode. Device is in Active mode or Idle mode.
281
Table 83 Configure Stream Normal Word 00h 01h 02h-04h 05h Name Error Count LBA Device Description Reserved Reserved Reserved Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Stream Error - See 6.1.8 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
282
T13/1699-D Revision 3f
Table 84 Stream Normal Word 00h 01h 02h-04h 05h Name Error Count LBA Device Description Reserved Reserved Reserved Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Stream Error - See 6.1.8 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete Shall be set to one Obsolete Transport Dependent - See 6.1.9 Reserved
283
Table 85 Device Reset and Execute Diagnostics Word 00h 01h Name Error Count Bit 7:0 02h-04h LBA 47:24 23:16 15:8 7:0 General 01h Reserved 00h 00h 01h Packet 01h Reserved 14h EBh 01h Reserved for SATA 01h Reserved C3h 3Ch 01h Reserved for SATA 01h Reserved 96h 69h 01h Reserved for All other CE-ATA signatures Reserved for reserved CE-ATA Reserved AAh CEh Reserved for CE-ATA Description Diagnostic Results - The diagnostic code as described in table 20 is returned. This field shall be reserved for the DEVICE RESET command.
05h
Device Bit 15 14 13 12 11:8 Status 7:6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
284
T13/1699-D Revision 3f
Table 86 IDLE Unload Word 00h 01h 02h-04h Name Error Count LBA Description N/A N/A Bit 47:28 27:8 7:0 05h Device Bit 15 14 13 12 11:8 Status 7:6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved N/A C4h
285
Table 87 ATAPI Normal Output Word 00h 01h Name Error Interrupt Reason Description N/A Bit 7:3 2 1 0 Description Tag - See 6.3.4 Obsolete Input/Output - See 6.3.2. Command/Data - See 6.3.1. Shall be set to zero
02h-04h
LBA Bit 47:28 27:24 23:8 7:0 Description Reserved N/A Byte Count N/A
05h
Device Bit 15 14 13 12 11:8 Status 7 6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. N/A Obsolete Service - See 6.1.7. Transport Dependent - See 6.1.9. N/A Error - See 6.1.2. Shall be cleared to zero Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
286
T13/1699-D Revision 3f
Table 88 Queued Normal Output Word 00h 01h Name Error Interrupt Reason Description N/A Bit 7:3 2 1 0 N/A Bit 15 14 13 12 11:8 Status 7 6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. N/A Device Fault - See 6.1.3 Service - See 6.1.7. Transport Dependent - See 6.1.9 N/A Error - See 6.1.2. Shall be cleared to zero Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Tag - See 6.3.4. Release - See 6.3.3. Input/Output - See 6.3.2. Command/Data - See 6.3.1.
02h-04h 05h
LBA Device
287
Table 89 SETMAX Normal Output Word 00h 01h 02h 03h 04h 05h Name Error Count LBA Description N/A N/A (MSB) Max address (LSB) Device Bit 15 14 13 12 11:8 Status 7:6 5:1 0 Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
288
T13/1699-D Revision 3f
Table 90 SMART Off-Line Immediate Normal Output Word 00h 01h 02h-04h Name Error Count LBA Description N/A N/A Bit 47:24 23:8 Description Reserved Value C24Fh All Other Values 7:0 05h Device Bit 15 14 13 12 11:8 Status 7:6 5 4 3 2 1 0 Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved N/A Description Subcommand specified a captive self-test that has executed without failure. the subcommand specified an off-line routine including an off-line self-test routine.
289
Table 91 SMART Return Status Normal Output Word 00h 01h 02h-04h Name Error Count LBA Description N/A N/A Bit 47:28 27:24 23:8 Description Reserved N/A Value C24Fh 2CF4 Description The device has not detected a threshold exceeded condition The device has detected a threshold exceeded condition
N/A
Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A N/A Error - See 6.1.2
290
December 11, 2006 Reference: 7.15, 7.25, 7.28, 7.31, 7.35, 7.39, 7.61, 7.62, 7.66, 7.69, 7.70, 7.72
T13/1699-D Revision 3f
Table 92 Generic Extended Normal Output Word 00h 01h 02h-04h 05h Name Error Count LBA Device Description Reserved Reserved Reserved Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
291
Table 93 SETMAX Extended Normal Output Word 00h 01h 02h 03h 04h 05h Name Error Count LBA Description Reserved Reserved (MSB) Max address (LSB) Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5:1 0 Description Reserved Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
292
T13/1699-D Revision 3f
Table 94 Queued Extended Normal Output Word 00h 01h Name Error Interrupt Reason Description N/A Bit 7:3 2 1 0 Reserved Bit 15 14 13 12 11:8 Status 7 6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. N/A Device Fault - See 6.1.3 Service - See 6.1.7. Transport Dependent - See 6.1.9. N/A Error - See 6.1.2. Shall be cleared to zero Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Tag - See 6.3.4. Release - See 6.3.3. Input/Output - See 6.3.2. Command/Data - See 6.3.1.
02h-04h 05h
LBA Device
293
Table 95 NV Cache Normal Output Word 00h 01h 02h-04h 05h Name Error Count LBA Device Description Reserved Reserved Unpinned logical blocks remaining Bit 15 14 13 12 11:8 05h Status 7:6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. Device Fault See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
Reference: 7.21.4
Table 96 NV Cache Flush Normal Output Word 00h 01h 02h-04h 05h Name Error Count LBA Device Description Reserved Reserved Number of unflushed logical blocks remaining Bit 15 14 13 12 11:8 05h Status 7:6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. Device Fault See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
294
T13/1699-D Revision 3f
Table 97 CFA Erase Error Status Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h 02h 03h 04h 05h Count LBA N/A (MSB) Description Reserved N/A ID Not Found - See 6.2.4 N/A Abort - See 6.2.1 N/A Media Error - See 6.2.7
Address of first unrecoverable error Bits 47:28 shall be cleared to zero. Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
(LSB)
Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Error - See 6.1.2
295
Table 98 CFA Write Error Status Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h 02h 03h 04h 05h Count LBA N/A (MSB) Description Reserved N/A ID Not Found - See 6.2.4 N/A Abort - See 6.2.1 N/A Media Error - See 6.2.7
Address of first unrecoverable error Bits 47:28 shall be cleared to zero. Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
(LSB)
Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3:1 0 Description Reserved Transport Dependent - See 6.1.9 Device Fault - See 6.1.3 Transport Dependent - See 6.1.9 N/A Error - See 6.1.2
296
T13/1699-D Revision 3f
Table 99 CFA Abort Error Word 00h Name Error Description Bit 15:8 7:3 2 1:0 01h 02h-4h 05h Count LBA Device N/A N/A Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved N/A Abort - See 6.2.1 N/A
297
T13/1699-D Revision 3f
Reference: 7.7, 7.10.4, 7.10.2, 7.10.3, 7.12, 7.17, 7.18, 7.19, 7.23, 7.40, 7.41, 7.42, 7.43, 7.44, 7.45, 7.47, 7.50, 7.51, 7.52.2, 7.52.3, 7.52.4, 7.52.8, 7.53, 7.54, 7.55, 7.57, 7.59, 7.75
Table 100 Generic Abort Word 00h Name Error Description Bit 15:8 7 6:3 2 1:0 01h 02h-04h 05h Count LBA Device N/A N/A Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Interface CRC - See 6.2.6. N/A Abort - See 6.2.1. N/A
298
T13/1699-D Revision 3f
Table 101 Generic Abort w/o Device Fault Word 00h Name Error Description Bit 15:8 7 6:3 2 1:0 01h 02h-04h 05h Count LBA Device N/A N/A Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5:1 0 Description Reserved Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Interface CRC - See 6.2.6 N/A Abort - See 6.2.1 N/A
299
Table 102 Configure Stream Error Word 00h Name Error Description Bit 15:8 7:3 2 1 0 01h 02h-04h 05h Count LBA Device Reserved Reserved Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Stream Error - See 6.1.8 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved N/A Abort - See 6.2.1. N/A Obsolete
300
December 11, 2006 Reference: 7.14, 7.15 Table 103 Flush Cache Error Word 00h Name Error Description Bit 15:8 7:3 2 1:0 01h 02h-04h Count LBA Description Reserved N/A Abort - See 6.2.1 N/A
T13/1699-D Revision 3f
Flush Cache - N/A Flush Cache Ext - Reserved. (MSB) Address of first unrecoverable error (LSB)
05h
Device Bit 15 14 13 12 11:8 Status 7:6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
301
Table 104 Read DMA Error Word 00h Name Error Description Bit 15:8 7 6 5 4 3 2 1:0 01h 02h 03h 04h 05h Count LBA Description Reserved Interface CRC - See 6.2.6 Uncorrectable Error - See 6.2.9. Obsolete ID Not Found - See 6.2.4 Obsolete Abort - See 6.2.1 Obsolete
READ DMA - N/A READ DMA EXT - Reserved (MSB) Address of first unrecoverable error. (LSB)
Device Bit 15 14 13 12 11:8 Status 7:6 5 4 3 2:1 0 Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
302
T13/1699-D Revision 3f
Table 105 Read Log Ext Error Word 00h Name Error Description Bit 15:8 7 6 5 4 3 2 1 0 01h 02h-04h 05h Count LBA Device Reserved Reserved Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Interface CRC - See 6.2.6 Uncorrectable Error - See 6.2.9. N/A ID Not Found - See 6.2.4 N/A Abort - See 6.2.1. N/A Obsolete
303
Table 106 Read PIO Error Word 00h Name Error Description Bit 15:8 7 6 5 4 3 2 1:0 01h 02h 03h 04h 05h Count LBA N/A (MSB) Address of first unrecoverable error. (LSB) Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Interface CRC - See 6.2.6 Uncorrectable Error - See 6.2.9 Obsolete ID Not Found - See 6.2.4 Obsolete Abort - See 6.2.1 Obsolete
304
T13/1699-D Revision 3f
Table 107 Read Stream Error Word 00h Name Error Description Bit 15:8 7 6 5 4 3 2 1 0 01h Count Description Reserved Interface CRC - See 6.2.6 Uncorrectable Error - See 6.2.9. Obsolete ID Not Found - See 6.2.4 Obsolete Abort - See 6.2.1 Obsolete Command Completion Time Limit Out - See 6.2.2
LBA
Length of Stream Error - number of contiguous logical sectors containing potentially bad data, beginning with the LBA of the first logical sector with an uncorrectable error. (MSB) Address of first unrecoverable error. (LSB) Bit 15 14 13 12 11:8 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
Device
Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Stream Error - See 6.1.8. Deferred Write Error - See 6.1.6. Transport Dependent - See 6.1.9. N/A Error - See 6.1.2.
305
Table 108 Setmax Error Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h 02h-04h 05h Count LBA Device N/A N/A Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved N/A ID Not Found - See 6.2.4. N/A Abort - See 6.2.1. N/A Obsolete
306
T13/1699-D Revision 3f
Table 109 Write Log Error Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h 02h-04h 05h Count LBA Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9 Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9 N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved N/A ID Not Found - See 6.2.4. N/A Abort - See 6.2.1. N/A Obsolete
SMART WRITE LOG - N/A WRITE LOG EXT - Reserved SMART WRITE LOG - N/A WRITE LOG EXT - Reserved
307
308
T13/1699-D Revision 3f
Table 110 SMART Error Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h 02h-04h Count LBA Reserved Bit 47:24 23:8 Description Reserved Value C24Fh Description Subcommand specified a captive self-test and some error other than a self-test routine failure occurred (i.e., if the sub-command is not supported or field values are invalid) the subcommand specified a captive self-test routine which has failed during execution. the subcommand specified an off-line routine including an off-line self-test routine. Description Reserved N/A ID Not Found - See 6.2.4. N/A Abort - See 6.2.1. N/A Obsolete
2CF4h All Other Values 7:0 05h Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 N/A
Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2
309
Table 111 Write Extended Error Word 00h Name Error Description Bit 15:8 7 6 5 4 3 2 1 0 01h 02h 03h 04h 05h Count LBA Reserved (MSB) Address of first unrecoverable error. (LSB) Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Interface CRC - See 6.2.6 Write Protect - See 6.2.10. Obsolete ID Not Found - See 6.2.4 Obsolete Abort - See 6.2.1. Obsolete N/A
310
T13/1699-D Revision 3f
Table 112 Write Stream Error Word 00h Name Error Description Bit 15:8 7 6 5 4 3 2 1 0 01h Count Description Reserved Interface CRC - See 6.2.6 Write Protect - See 6.2.10. Obsolete ID Not Found - See 6.2.4 Obsolete Abort - See 6.2.1 Obsolete Command Completion Time Limit Out - See 6.2.2
LBA
Length of Stream Error - number of contiguous logical sectors containing potentially bad data, beginning with the LBA of the first logical sector with an uncorrectable error. (MSB) Address of first unrecoverable error. (LSB) Bit 15 14 13 12 11:8 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
Device
Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Stream Error - See 6.1.8. Deferred Write Error - See 6.1.6. Transport Dependent - See 6.1.9. N/A Error - See 6.1.2.
311
Table 113 DCO Set Error Word 00h Name Error Bit 15:8 7:3 2 Description Description Reserved N/A Abort - See 6.2.1. Abort shall be set to one if a DEVICE CONFIGURATION SET command has already modified the original settings as reported by a DEVICE CONFIGURATION IDENTIFY command, if DEVICE CONFIGURATION FREEZE LOCK is set, if any of the bit modification restrictions described in 7.10.5.2 are violated, or if a Host Protected Area has been established by the execution of a SET MAX ADDRESS or SET MAX ADDRESS EXT command, or if an attempt was made to modify a mode or feature that cannot be modified with the device in its current state. 1:0 N/A
01h 02h-04h
Count LBA
Vendor Specific Bit 47:28 27:24 23:16 Description Reserved N/A Word location - If the command was aborted because an attempt was made to modify a bit that cannot be modified with the device in its current state, this field shall contain the offset of the first word encountered that cannot be changed. If an illegal maximum LBA is encountered, the offset of word 3 shall be entered. If a checksum error occurred, the value FFh shall be entered. A value of 00h indicates that the Data Structure Revision was invalid. 15:0 15:0 Bit Location - If the command was aborted because an attempt was made to disable a mode or feature that cannot be disabled with the device in its current state, this field shall contain an array of bits that correspond to the device configuration overlay data structure listed in Table 11 relative to the word indicated in Word Location (23:16). A one in this array indicates that the requested mode or feature could not be disabled by the device. If not, the value shall be 0000h.
312
December 11, 2006 Table 113 DCO Set Error Word 05h Name Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
T13/1699-D Revision 3f
313
Table 114 NOP Error Word 00h Name Error Bit 15:8 7:3 2 1:0 01h 02h-04h 05h Count LBA Device Description Reserved N/A Abort - See 6.2.1. Obsolete Description
Initial Value Initial Value Bit 15 14 13 12 11:8 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2
314
T13/1699-D Revision 3f
Table 115 PACKET Command Error Word 00h Name Error Bit 7:4 3 2 1 0 01h Interrupt Reason Description Description Sense Key - See 6.2.8 N/A Abort - See 6.2.1 End of Media - See 6.2.3 Illegal Length Indicator - See 6.2.5
Description Tag - See 6.3.4 Release - See 6.3.3. Shall be cleared to zero Input/Output - See 6.3.2. Shall be set to one Command/Data - See 6.3.1. Shall be set to one
02h-04h 05h
LBA Device
Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. N/A Service - See 6.1.7. Transport Dependent - See 6.1.9. N/A Error - See 6.1.2.
315
Table 116 Read DMA Queued Error Word 00h Name Error Bit 15:8 7 6 5 4 3 2 1:0 01h Interrupt Reason Bit 7:3 2 1 0 02h 03h 04h 05h LBA (MSB) Description Tag - See 6.3.4. If the device supports the TCQ feature set, this field shall contain the Tag of the command being released. Release - See 6.3.3. Shall be cleared to zero Input/Output - See 6.3.2. Shall be set to one Command/Data - See 6.3.1. Shall be set to one Address of first unrecoverable error. Bits 47:28 shall be cleared to zero. Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Description Reserved Interface CRC - See 6.2.6 Uncorrectable Error - See 6.2.9 Obsolete ID Not Found - See 6.2.4 Obsolete Abort - See 6.2.1 Obsolete
(LSB)
Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 Service - See 6.1.7 Transport Dependent - See 6.1.9. N/A Error - See 6.1.2
316
T13/1699-D Revision 3f
Table 117 Read DMA Queued Extended Error Word 00h Name Error Bit 15:8 7 6 5 4 3 2 1:0 01h Interrupt Reason Description Description Reserved Interface CRC - See 6.2.6 Uncorrectable Error - See 6.2.9 Obsolete ID Not Found - See 6.2.4 Obsolete Abort - See 6.2.1 Obsolete
Description Reserved Tag - See 6.3.4. If the device supports the TCQ feature set, this field shall contain the Tag of the command being released. Release - See 6.3.3. Shall be cleared to zero Input/Output - See 6.3.2. Shall be set to one Command/Data - See 6.3.1. Shall be set to one
LBA
Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 Service - See 6.1.7 Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
317
Table 118 SMART Read Log/SMART Read Data Error Word 00h Name Error Description Bit 15:8 7 6 5 4 3 2 1 0 01h 02h-04h 05h Count LBA Device N/A N/A Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Interface CRC - See 6.2.6 Uncorrectable Error - See 6.2.9. N/A ID Not Found - See 6.2.4 N/A Abort - See 6.2.1. N/A Obsolete
318
T13/1699-D Revision 3f
Table 119 Read PIO Extended Error Word 00h Name Error Description Bit 15:8 7 6 5 4 3 2 1:0 01h 02h 03h 04h 05h Count LBA Reserved (MSB) Address of first unrecoverable error. (LSB) Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Interface CRC - See 6.2.6 Uncorrectable Error - See 6.2.9 Obsolete ID Not Found - See 6.2.4 Obsolete Abort - See 6.2.1 Obsolete
319
Table 120 Read Native Max Extended Error Word 00h Name Error Description Bit 15:8 7 6:3 2 1:0 01h 02h-04h 05h Count LBA Device Reserved Reserved Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5:1 0 Description Reserved Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete Shall be set to one Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Interface CRC - See 6.2.6 N/A Abort - See 6.2.1 N/A
320
T13/1699-D Revision 3f
Table 121 SETMAX Extended Error Word 00h Name Error Description Bit 15:8 7:5 4 3 2 1 0 01h 02h-04h 05h Count LBA Device Reserved Reserved Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved N/A ID Not Found - See 6.2.4. N/A Abort - See 6.2.1. N/A Obsolete
321
Table 122 Write Error Word 00h Name Error Description Bit 15:8 7 6 5 4 3 2 1 0 01h 02h 03h 04h 05h Count LBA N/A (MSB) Address of first unrecoverable error. (LSB) Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Interface CRC - See 6.2.6 Write Protect - See 6.2.10. Obsolete ID Not Found - See 6.2.4 Obsolete Abort - See 6.2.1. Obsolete N/A
322
T13/1699-D Revision 3f
Table 123 Write DMA Queued Error Word 00h Name Error Description Bit 15:8 7 6 5 4 3 2 1:0 01h Interrupt Reason Description Reserved Interface CRC - See 6.2.6 Write Protect - See 6.2.10 Obsolete ID Not Found - See 6.2.4 Obsolete Abort - See 6.2.1 Obsolete
Bit 7:3 2 1 0
Description Tag - See 6.3.4. If the device supports the TCQ feature set, this field shall contain the Tag of the command being released. Release - See 6.3.3. Shall be cleared to zero Input/Output - See 6.3.2. Shall be set to one Command/Data - See 6.3.1. Shall be set to one
LBA
Device Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 Service - See 6.1.7 Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved
323
Table 124 NV Cache Add Abort Word 00h Name Error Description Bit 15:3 2 1 0 01h 02h-04h 05h Count LBA Device N/A N/A Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Abort - See 6.2.1 Insufficient LBA Range Entries - See 6.2.13 Insufficient NV Cache space - See 6.2.12
324
T13/1699-D Revision 3f
Table 125 NV Cache Remove Abort Word 00h Name Error Description Bit 15:3 2 1 0 01h 02h-04h 05h Count LBA Device N/A N/A Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Abort - See 6.2.1 Reserved Attempted partial range removal from pinned set- See See 6.2.11
325
Table 126 Generic NV Cache Abort Word 00h Name Error Description Bit 15:3 2 1:0 01h 02h-04h 05h Count LBA Device N/A N/A Bit 15 14 13 12 11:8 Status Bit 15:8 7:6 5 4 3 2:1 0 Description Reserved Transport Dependent - See 6.1.9. Device Fault - See 6.1.3 N/A Transport Dependent - See 6.1.9. N/A Error - See 6.1.2 Description Obsolete N/A Obsolete Transport Dependent - See 6.1.9 Reserved Description Reserved Abort - See 6.2.1 Reserved
326
T13/1699-D Revision 3f
Annex A
(Normative)
GPL GPL
Key RO - Log is only read by the host. R/W - Log is read or written by the host. VS - Log is vendor specific thus read/write ability is vendor specific. GPL - General Purpose Logging SL - SMART Logging Command Abort shall be returned if a GPL command is used to access a log page that is marked with SL only. Command Abort shall be returned if an SL command is used to access a log page that is marked with GPL only.
327
T13/1699-D Revision 3f
The value of the General Purpose Logging Version word shall be 0001h. A value of 0000h indicates that no General Purpose log Directory exists. The logs at log addresses 80-9Fh shall each be defined as 16 512-byte blocks (8K) of data long.
328
T13/1699-D Revision 3f
All 28-bit entries contained in the Comprehensive SMART log, defined under section A.11, shall also be included in the Extended Comprehensive SMART error log with the 48-bit entries. Table 129 Extended Comprehensive SMART error log First 512-byte block of data Subsequent 512-byte blocks of data 0 SMART error log version Reserved 1 Reserved Reserved 2 Error log index (7:0) Reserved 3 Error log index (15:8) Reserved 4-127 First error log data structure Data structure 4n+1 128-251 Second error log data structure Data structure 4n+2 252-375 Third error log data structure Data structure 4n+3 376-499 Fourth error log data structure Data structure 4n+4 500-501 Device error count Reserved 502-510 Reserved Reserved 511 Data structure checksum Data structure checksum n is the logical block number within the log. The first 512-byte block of data is numbered zero A.3.2 Error log version The value of the SMART error log version byte shall be 01h. A.3.3 Error log index The error log index is the error log data structure number representing the most recent error. If there have been no error log entries, the error log index is cleared to zero. Valid values for the error log index are zero to 65,535. A.3.4 Extended Error log data structure A.3.4.1 Overview The error log is viewed as a circular buffer. When the last supported error log has been filled, the next error shall create an error log data structure that replaces the first error log data structure in block zero. The next error after that shall create an error log data structure that replaces the second error log data structure in block zero. The fifth error after the log has filled shall replace the first error log data structure in block one, and so on. The error log index indicates the most recent error log data structure. Unused error log data structures shall be filled with zeros. The content of the error log data structure entries is defined in Table 130. Table 130 Extended Error log data structure Byte n - n+17 n+18 - n+35 n+36 - n+53 n+54 - n+71 n+72 - n+89 n+90 - n+123 Description First command data structure Second command data structure Third command data structure Fourth command data structure Fifth command data structure Error data structure Byte
329
The fifth command data structure shall contain the command or reset for which the error is being reported. The fourth command data structure should contain the command or reset that preceded the command or reset for which the error is being reported, the third command data structure should contain the command or reset preceding the one in the fourth command data structure, etc. If fewer than four commands and resets preceded the command or reset for which the error is being reported, the unused command data structures shall be zero filled, for example, if only three commands and resets preceded the command or reset for which the error is being reported, the first command data structure shall be zero filled. In some devices, the hardware implementation may preclude the device from reporting the commands that preceded the command for which the error is being reported or that preceded a reset. In this case, the command data structures are zero filled. If the command data structure represents a command or software reset, the content of the command data structure shall be as shown in Table 131. If the command data structure represents a hardware reset, the content of byte n shall be FFh, the content of bytes n+1 through n+13 are vendor specific, and the content of bytes n+14 through n+17 shall contain the timestamp. Table 131 Command data structure Byte n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 n+9 n+10 n+11 n+12 n+13 n+14 n+15 n+16 n+17 Description Content of the Device Control field when the Command was initiated. Content of the Feature field (7:0) when the Command was initiated. Content of the Feature field (15:8) when the Command was initiated. Content of the Count field (7:0) when the Command was initiated. Content of the Count field (15:8) when the Command was initiated. Content of the LBA field (7:0) when the Command was initiated. Content of the LBA field (15:8) when the Command was initiated. Content of the LBA field (23:16) when the Command was initiated. Content of the LBA field (31:24) when the Command was initiated. Content of the LBA field (39:32) when the Command was initiated. Content of the LBA field (47:40) when the Command was initiated. Content of the Device field when the Command was initiated. Content written to the Command field when the command was initiated Reserved Timestamp (least significant byte) Timestamp (next least significant byte) Timestamp (next most significant byte) Timestamp (most significant byte)
Timestamp shall be the time since power-on in milliseconds when command acceptance occurred. This timestamp may wrap around.
330
T13/1699-D Revision 3f
The error data structure shall contain the error description of the command for which an error was reported as described in Table 132. If the error was logged for a hardware reset, the content of bytes n+1 through n+11 shall be vendor specific and the remaining bytes shall be as defined in Table 132. Table 132 Error data structure Byte n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 n+9 n+10 n+11 n+12 through n+30 n+31 n+32 n+33 Description Transport specific value when the Command was initiated. See the appropriate transport standard, reference Device Control register. Content of the Error field (7:0) after command completion occurred. Content of the Count field (7:0) after command completion occurred. Content of the Count field (15:8) after command completion occurred. Content of the LBA field (7:0) after command completion occurred. Content of the LBA field (15:8) after command completion occurred. Content of the LBA field (23:16) after command completion occurred. Content of the LBA field (31:24) after command completion occurred. Content of the LBA field (39:32) after command completion occurred. Content of the LBA field (47:40) after command completion occurred. Content of the Device field after command completion occurred. Content written to the Status field after command completion occurred. Extended error information State Life timestamp (least significant byte) Life timestamp (most significant byte)
Extended error information shall be vendor specific. State shall contain a value indicating the state of the device when the command was initiated or the reset occurred as described in Table 133. Table 133 State field values Value State x0h Unknown x1h Sleep x2h Standby x3h Active/Idle x4h Executing SMART off-line or self-test x5h-xAh Reserved xBh-xFh Vendor specific The value of x is vendor specific and may be different for each state. Sleep indicates the reset for which the error is being reported was received when the device was in the Sleep mode. Standby indicates the command or reset for which the error is being reported was received when the device was in the Standby mode. Active/Idle indicates the command or reset for which the error is being reported was received when the device was in the Active or Idle mode.
331
T13/1699-D Revision 3f
Executing SMART off-line or self-test indicates the command or reset for which the error is being reported was received when the device was in the process of executing a SMART off-line or self-test. Life timestamp shall contain the power-on lifetime of the device in hours when command completion occurred. A.3.5 Device error count The device error count field shall contain the total number of errors attributable to the device that have been reported by the device during the life of the device. These errors shall include Uncorrectable errors (See 6.2.9), ID Not Found errors (See 6.2.4) for which the address requested was valid, servo errors, write fault errors, etc. This count shall not include errors attributed to the receipt of faulty commands such as commands codes not implemented by the device or requests with invalid parameters or invalid addresses. If the maximum value for this field is reached, the count shall remain at the maximum value when additional errors are encountered and logged. A.3.6 Data structure checksum The data structure checksum is the twos complement of the sum of the first 511 bytes in the data structure. Each byte shall be added with unsigned arithmetic, and overflow shall be ignored. The sum of all 512 bytes shall be zero when the checksum is correct. The checksum is placed in byte 511.
332
T13/1699-D Revision 3f
The Self-test descriptor index indicates the most recent self-test descriptor. If there have been no self-tests, the Self-test descriptor index is set to zero. Valid values for the Self-test descriptor index are zero to 65,535. A.4.3 Self-test log data structure revision number The value of the self-test log data structure revision number shall be 01h. A.4.4 Extended Self-test log descriptor entry The content of the self-test descriptor entry is shown in Table 135. Table 135 Extended Self-test log descriptor entry Byte n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 n+9 n+10 n+11 - n+25 Description Content of the LBA field (7:0) Content of the self-test execution status byte. Life timestamp (least significant byte). Life timestamp (most significant byte). Content of the self-test failure checkpoint byte. Failing LBA (7:0). Failing LBA (15:8). Failing LBA (23:16). Failing LBA (31:24). Failing LBA (39:32). Failing LBA (47:40). Vendor specific.
Content of the LBA field (7:0) shall be the content of the LBA field (7:0) when the nth self-test subcommand was issued (see 7.52.5.2). Content of the self-test execution status byte shall be the content of the self-test execution status byte when the nth self-test was completed (see 7.52.6.4). Life timestamp shall contain the power-on lifetime of the device in hours when the nth self-test subcommand was completed. Content of the self-test failure checkpoint byte may contain additional information about the self-test that failed. The failing LBA shall be the LBA of the logical sector that caused the test to fail. If the device encountered more than one failed logical sector during the test, this field shall indicate the LBA of the first failed logical sector encountered. If the test passed or the test failed for some reason other than a failed logical sector, the value of this field is undefined. A.4.5 Data structure checksum The data structure checksum is the two's complement of the sum of the first 511 bytes in the data structure. Each byte shall be added with unsigned arithmetic, and overflow shall be ignored. The sum of all 512 bytes is zero when the checksum is correct. The checksum is placed in byte 511.
T13/1699-D Revision 3f
last successful completion of the READ LOG EXT command with LBA field (7:0) set to 22h. This error count may be greater than 31, but only the most recent 31 errors are represented by entries in the log. If the Read Stream Error Count reaches its maximum value, after the next error is detected the Read Stream Error Count shall remain at the maximum value. During processing of a READ LOG EXT command with the LBA field (7:0) set to 22h, a device shall clear the Read Stream Error Log and clear the Error Log Index and Read Stream Error Count to zero. A device shall clear the content of the Read Stream Error Log during processing of a power-on reset or a hardware reset. Table 136 Read Stream Error Log Byte 0 1 2-3 4-15 16-31 32-47 48-63 64-511 Content Structure Version Error Log Index Read Stream Error Log Count Reserved Read Stream Error Log Entry #1 Read Stream Error Log Entry #2 Read Stream Error Log Entry #3 Read Stream Error Log Entries #4 through #31
The Data Structure Version field shall contain a value of 02h indicating the second revision of the structure format. The Read Stream Error Log Count field shall contain the number of uncorrected logical sector entries currently reportable to the host. This value may exceed 31. The Error Log Index indicates the error log data structure representing the most recent error. Only values 1 through 31 are valid. Table 137 defines the format of each entry in the Read Stream Error Log. Table 137 Error Log Entry Byte 0 1 2 3 4 5 6 7 8 9 10-11 12 13 14 15 Value Feature (7:0) Feature (15:8) Status Error LBA (7:0) LBA (15:8) LBA (23:16) LBA (31:24) LBA (39:32) LBA (47:40) Reserved Count (7:0) Count (15:8) Reserved Reserved
Byte (1:0) (Feature field) contains the contents of the Feature field when the error occurred. This value shall be set to 0FFFFh for a deferred write error. Byte 2 (Status field) contains the contents of the Status field when the error occurred. Byte 3 (Error field) contains the contents of the Error field when the error occurred.
334
December 11, 2006 Bytes (9:4) (LBA field) indicate the starting LBA of the error.
T13/1699-D Revision 3f
Bytes (13:12) (Count field) indicate the length of the error. Each entry may describe a range of logical sectors starting at the given address and spanning the specified number of logical sectors.
The Data Structure Version field shall contain a value of 02h indicating the second revision of the structure format. The Write Stream Error Log Count field shall contain the number of WRITE STREAM command entries since the last power-on reset or hardware reset, or since this log was last read. The Error Log Index indicates the error log data structure representing the most recent error. Only values 1 through 31 are valid. Table 137 defines the format of each entry in the Error Log.
335
T13/1699-D Revision 3f
The value of the SMART Logging Version word shall be 01h if the drive supports multi-block SMART logs. If the drive does not support multi-block SMART logs, then log number zero is defined as reserved, and the drive shall return a command aborted response to the hosts request to read log number zero.
336
T13/1699-D Revision 3f
supports comprehensive error log (address 02h), then the summary error log duplicates the last five error entries in the comprehensive error log. The summary error log supports 28-bit addressing only. Table 140 SMART summary error log Byte 0 1 2-91 92-181 182-271 272-361 362-451 452-453 454-510 511 A.10.2 Error log version The value of the SMART summary error log version byte shall be 01h. A.10.3 Error log index The error log index indicates the error log data structure representing the most recent error. Only values 5 through 0 are valid. If there are no error log entries, the value of the error log index shall be zero. A.10.4 Error log data structure A.10.4.1 Overview An error log data structure shall be presented for each of the last five errors reported by the device. These error log data structure entries are viewed as a circular buffer. That is, the first error shall create the first error log data structure; the second error, the second error log structure; etc. The sixth error shall create an error log data structure that replaces the first error log data structure; the seventh error replaces the second error log structure, etc. The error log pointer indicates the most recent error log structure. If fewer than five errors have occurred, the unused error log structure entries shall be zero filled. Table 141 describes the content of a valid error log data structure. Table 141 Error log data structure Byte n - n+11 n+12 - n+23 n+24 - n+35 n+36 - n+47 n+48 - n+59 n+60 - n+89 A.10.4.2 Command data structure The fifth command data structure shall contain the command or reset for which the error is being reported. The fourth command data structure should contain the command or reset that preceded the command or reset for which the error is being reported, the third command data structure should contain the command or reset preceding the one in the fourth command data structure, etc. If fewer than four commands and resets preceded the command or reset for which the error is being reported, the unused command data structures shall be zero Working Draft AT Attachment 8 - ATA/ATAPI Command Set (ATA8-ACS) 337 Description First command data structure Second command data structure Third command data structure Fourth command data structure Fifth command data structure Error data structure Description SMART error log version Error log index First error log data structure Second error log data structure Third error log data structure Fourth error log data structure Fifth error log data structure Device error count Reserved Data structure checksum
T13/1699-D Revision 3f
filled, for example, if only three commands and resets preceded the command or reset for which the error is being reported, the first command data structure shall be zero filled. In some devices, the hardware implementation may preclude the device from reporting the commands that preceded the command for which the error is being reported or that preceded a reset. In this case, the command data structures are zero filled. If the command data structure represents a command or software reset, the content of the command data structure shall be as shown in table 142. If the command data structure represents a hardware reset, the content of byte n shall be FFh, the content of bytes n+1 through n+7 are vendor specific, and the content of bytes n+8 through n+11 shall contain the timestamp. Table 142 Command data structure Byte n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 n+9 n+10 n+11 Description Transport specific value when the Command was initiated. See the appropriate transport standard, reference Device Control register. Content of the Feature field when the Command was initiated. Content of the Count field when the Command was initiated. Content of the LBA field (7:0) when the Command was initiated. Content of the LBA field (15:8) when the Command was initiated. Content of the LBA field (23:16) when the Command was initiated. Content of the Device field when the Command was initiated. Content written when the Command was initiated Timestamp (least significant byte) Timestamp (next least significant byte) Timestamp (next most significant byte) Timestamp (most significant byte)
Timestamp shall be the time since power-on in milliseconds when command acceptance occurred. This timestamp may wrap around. A.10.4.3 Error data structure The error data structure shall contain the error description of the command for which an error was reported as described in Table 142. If the error was logged for a hardware reset, the content of bytes n+1 through n+7 shall be vendor specific and the remaining bytes shall be as defined in table 142. Table 143 Error data structure Byte n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 - n+26 n+27 n+28 n+29 Description Reserved Content of the Error field after command completion occurred. Content of the Count field after command completion occurred. Content of the LBA field (7:0) after command completion occurred. Content of the LBA field (15:8) after command completion occurred. Content of the LBA field (23:16) after command completion occurred. Content of the Device field after command completion occurred. Content written to the Status field after command completion occurred. Extended error information State Life timestamp (least significant byte) Life timestamp (most significant byte)
338
T13/1699-D Revision 3f
State shall contain a value indicating the state of the device when command was initiated or the reset occurred as described in table 144. Table 144 State field values Value State x0h Unknown x1h Sleep x2h Standby x3h Active/Idle x4h Executing SMART off-line or self-test x5h-xAh Reserved xBh-xFh Vendor specific The value of x is vendor specific and may be different for each state. Sleep indicates the reset for which the error is being reported was received when the device was in the Sleep mode. Standby indicates the command or reset for which the error is being reported was received when the device was in the Standby mode. Active/Idle indicates the command or reset for which the error is being reported was received when the device was in the Active or Idle mode. Executing SMART off-line or self-test indicates the command or reset for which the error is being reported was received when the device was in the process of executing a SMART off-line or self-test. Life timestamp shall contain the power-on lifetime of the device in hours when command completion occurred. A.10.5 Device error count The device error count field shall contain the total number of errors attributable to the device that have been reported by the device during the life of the device. These errors shall include UNC errors, IDNF errors for which the address requested was valid, servo errors, write fault errors, etc. This count shall not include errors attributed to the receipt of faulty commands such as commands codes not implemented by the device or requests with invalid parameters or invalid addresses. If the maximum value for this field is reached, the count shall remain at the maximum value when additional errors are encountered and logged. A.10.6 Data structure checksum The data structure checksum is the two's complement of the sum of the first 511 bytes in the data structure. Each byte shall be added with unsigned arithmetic, and overflow shall be ignored. The sum of all 512 bytes shall be zero when the checksum is correct. The checksum is placed in byte 511.
339
T13/1699-D Revision 3f
Comprehensive error log data structures shall not include errors attributed to the receipt of faulty commands such as command codes not supported by the device or requests with invalid parameters or invalid addresses. Table 145 Comprehensive error log Byte First 512-byte block of data 0 SMART error log version 1 Error log index 2-91 First error log data structure 92-181 Second error log data structure 182-271 Third error log data structure 272-361 Fourth error log data structure 362-451 Fifth error log data structure 452-453 Device error count 454-510 Reserved 511 Data structure checksum n is the nth 512-byte block of data within the log. numbered zero A.11.2 Error log version The value of the error log version byte shall be set to 01h. A.11.3 Error log index The error log index indicates the error log data structure representing the most recent error. If there have been no error log entries, the error log index is set to zero. Valid values for the error log index are zero to 255. A.11.4 Error log data structure The error log is viewed as a circular buffer. The device may support from two to 51 error log blocks. When the last supported error log block has been filled, the next error shall create an error log data structure that replaces the first error log data structure in logical block zero. The next error after that shall create an error log data structure that replaces the second error log data structure in block zero. The sixth error after the log has filled shall replace the first error log data structure in block one, and so on. The error log index indicates the most recent error log data structure. Unused error log data structures shall be filled with zeros. The content of the error log data structure entries is defined in A.10.4. A.11.5 Device error count The device error count field is defined in A.10.5. A.11.6 Data structure checksum The data structure checksum is defined in A.11.6. Subsequent 512-byte blocks of data Reserved Reserved Data structure 5n+1 Data structure 5n+2 Data structure 5n+3 Data structure 5n+4 Data structure 5n+5 Reserved Reserved Data structure checksum The first 512-byte block of data is
340
T13/1699-D Revision 3f
This log is viewed as a circular buffer. The first entry shall begin at byte 2, the second entry shall begin at byte 26, and so on until the twenty-second entry, that shall replace the first entry. Then, the twenty-third entry shall replace the second entry, and so on. If fewer than 21 self-tests have been performed by the device, the unused descriptor entries shall be filled with zeroes. A.12.2 Self-test log data structure revision number The value of the self-test log data structure revision number shall be 0001h. A.12.3 Self-test log descriptor entry The content of the self-test descriptor entry is shown in table 147. Table 147 Self-test log descriptor entry Byte n n+1 n+2 n+3 n+4 n+5 n+6 n+7 n+8 n+9 to n+23 Description Content of the LBA field (7:0). Content of the self-test execution status byte. Life timestamp (least significant byte). Life timestamp (most significant byte). Content of the self-test failure checkpoint byte. Failing LBA (7:0). Failing LBA (15:8). Failing LBA (23:16). Failing LBA (27:24). Vendor specific.
Content of the LBA field (7:0) shall be the content of the LBA field (7:0) when the nth self-test subcommand was issued (see 7.52.5.2). Content of the self-test execution status byte shall be the content of the self-test execution status byte when the nth self-test was completed (see 7.52.6.4). Life timestamp shall contain the power-on lifetime of the device in hours when the nth self-test subcommand was completed.
341
T13/1699-D Revision 3f
Content of the self-test failure checkpoint byte may contain additional information about the self-test that failed. The failing LBA shall be the LBA of the uncorrectable logical sector that caused the test to fail. If the device encountered more than one uncorrectable logical sector during the test, this field shall indicate the LBA of the first uncorrectable logical sector encountered. If the test passed or the test failed for some reason other than an uncorrectable logical sector, the value of this field is undefined. A.12.4 Self-test index The self-test index shall point to the most recent entry. Initially, when the log is empty, the index shall be set to zero. It shall be set to one when the first entry is made, two for the second entry, etc., until the 22nd entry, when the index shall be reset to one. A.12.5 Data structure checksum The data structure checksum is the two's complement of the sum of the first 511 bytes in the data structure. Each byte shall be added with unsigned arithmetic, and overflow shall be ignored. The sum of all 512 bytes is zero when the checksum is correct. The checksum is placed in byte 511.
342
T13/1699-D Revision 3f
The value of the data structure revision number filed shall be 01h. This value shall be written by the host and returned unmodified by the device. A.13.3 Test span definition The Selective self-test log provides for the definition of up to five test spans. The starting LBA for each test span is the LBA of the first logical sector tested in the test span and the ending LBA for each test span is the last LBA tested in the test span. If the starting and ending LBA values for a test span are both zero, a test span is not defined and not tested. These values shall be written by the host and returned unmodified by the device. A.13.4 Current LBA under test The Current LBA under test field shall be written with a value of zero by the host. As the self-test progresses, the device shall modify this value to contain the beginning LBA of the 65,536 logical sector block currently being tested. When the self-test including the off-line scan between test spans has been completed, a zero value is placed in this field. A.13.5 Current span under test The Current span under test field shall be written with a value of zero by the host. As the self-test progresses, the device shall modify this value to contain the test span number of the current span being tested. If an off-line scan between test spans is selected, a value greater then five is placed in this field during the off-line scan. When the self-test including the off-line scan between test spans has been completed, a zero value is placed in this field. A.13.6 Feature flags The Feature flags define the features of Selective self-test to be executed (see table 149). Table 149 Selective self-test feature flags Bit 0 1 2 3 4 5-15 Description Vendor specific When set to one, perform off-line scan after selective test. Vendor specific When set to one, off-line scan after selective test is pending. When set to one, off-line scan after selective test is active. Reserved.
Bit (1) shall be written by the host and returned unmodified by the device. Bits (4:3) shall be written as zeros by the host and the device shall modify them as the test progresses. A.13.7 Selective self-test pending time The selective self-test pending time is the time in minutes from power-on to the resumption of the off-line testing if the pending bit is set. At the expiration of this time, sets the active bit to one, and resumes the off-line scan that had begun before power-down. A.13.8 Data structure checksum The data structure checksum is defined in A.10.6.
343
T13/1699-D Revision 3f
16-511
Byte
A.14.2.2 Lifetime Power-On Resets A.14.2.2.1 Description Lifetime Power-On Resets is a counter which records the nummber of times that the drive has processed a power-on reset. A.14.2.2.2 Update Interval Lifetime Power-On Resets is incremented by one after processesing each Power-On Reset and the device is capable of recording this statistic. A.14.2.2.3 Measurment Units Lifetime Power-On Resets is incremented by one for each Power-On Reset event. A.14.2.2.4 Initialization Lifetime Power-On Resets shall be initialized to zero at the factory.
344
T13/1699-D Revision 3f
Annex B
(Informative)
Table B.1 Command Matrix 0x 1x 2x 3x 4x 5x 6x 7x 8x 9x Ax Bx Cx Dx Ex Fx Key: x0 C O C C C O S O V C C C F R C V x1 R E O O O C* S E V O C C V C C C x2 R E O O C R S E V C C R V M C C x3 C E O O R R S E V R R R V M C C x4 R E C C R R S E V E R R C M C C x5 R E C C C* R S E V E R R C R C C x6 R E C C R R S E V E R C* C R C C x7 R E C C C* C* S E F E R R C R C V x8 x9 xA xB xC xD xE xF C R R R R R R R E E E E E E E E R C C C R R R C C C C C O C C C R R R R R R R R R R R R C* C* C* C* R R R R R R R R E E E E E E E E V V V V V V V V E E V R R R R R R R R R R R R R A A A A A A A A C O C O C C C R R R O E E E O O C E C R C O O C C C V V V V V V M = Reserved for the Media Card Pass Through Command feature set. S = Reserved for Serial ATA * indicates that the entry in this table has changed from ATA/ATAPI-7, INCITS xxx-xxxx.
C = defined command. R = Reserved, undefined in current specifications. V = Vendor specific commands. O = Obsolete. E = retired command. F= If the device does not implement the CFA feature set, this command code is Vendor specific. A= Reserved for assignment by the CompactFlash Association
345
T13/1699-D Revision 3f
Table B.2 Command codes (sorted by command code) (part 1 of 3) Protocol Command ND ND DR NOP Reserved CFA REQUEST EXTENDED ERROR Reserved DEVICE RESET Reserved Obsolete Retired READ SECTOR(S) Obsolete READ SECTOR(S) EXT READ DMA EXT READ DMA QUEUED EXT READ NATIVE MAX ADDRESS EXT Reserved READ MULTIPLE EXT READ STREAM DMA EXT READ STREAM EXT Reserved READ LOG EXT WRITE SECTOR(S) Obsolete WRITE SECTOR(S) EXT WRITE DMA EXT WRITE DMA QUEUED EXT SET MAX ADDRESS EXT CFA WRITE SECTORS WITHOUT ERASE WRITE MULTIPLE EXT WRITE STREAM DMA EXT WRITE STREAM EXT Obsolete WRITE DMA FUA EXT WRITE DMA QUEUED FUA EXT WRITE LOG EXT READ VERIFY SECTOR(S) Obsolete READ VERIFY SECTOR(S) EXT Reserved WRITE UNCORRECTABLE EXT Reserved READ LOG DMA EXT Reserved Obsolete CONFIGURE STREAM General Feature Set O O N Packet Command Feature Set Code M 00h 01h-01h N 03h 04h-07h M 08h 09h-0Fh 10h 11h-1Fh M 20h 21h-23h N 24h N 25h N 26h N 27h 28h N 29h N 2Ah N 2Bh 2Ch-2Fh O 2Fh N 30h 31h-33h N 34h N 35h N 36h N 37h N 38h N 39h N 3Ah N 3Bh 3Ch N 3Dh N 3Eh O 3Fh N 40h 41h N 42h 43h-44h N 45h 46h O 47h 48h-4Fh 50h O 51H
M O O O O O O O O M O O O O O O O O O O O M O O O
ND
346
T13/1699-D Revision 3f
Table B.2 Command codes (sorted by command code) (part 2 of 3) Protocol Command DM Reserved WRITE LOG DMA EXT Reserved TRUSTED RECEIVE TRUSTED RECEIVE DMA TRUSTED SEND TRUSTED SEND DMA Reserved Obsolete Retired Vendor Specific CFA TRANSLATE SECTOR Vendor Specific EXECUTE DEVICE DIAGNOSTIC Reserved DOWNLOAD MICROCODE Reserved Retired Vendor Specific Reserved PACKET IDENTIFY PACKET DEVICE SERVICE Reserved SMART DEVICE CONFIGURATION OVERLAY Reserved NV Cache Reserved CFA ERASE SECTORS Vendor Specific READ MULTIPLE WRITE MULTIPLE SET MULTIPLE MODE READ DMA QUEUED READ DMA Obsolete WRITE DMA Obsolete WRITE DMA QUEUED CFA WRITE MULTIPLE WITHOUT ERASE WRITE MULTIPLE FUA EXT Reserved Reserved CHECK MEDIA CARD TYPE General Feature Set O O O O O Packet Feature Set O P P P P Command Code 52h-56h 57h 58h-5Bh 5Ch 5Dh 5Eh 5Fh 60h-6Fh 70h 71h-7Fh 80h-86h 87h 88h-8Fh 90h 91h 92h 93h 94h-99h 9Ah 9Bh-9Fh A0h A1h A2h A3h-AFH B0h B1h B2h-B5h B6h B7h-BFh C0h C1h-C3h C4h C5h C6h C7h C8h C9h CAh CBh CCh CDh CEh CFh D0h D1h
VS PI VS DD PO
O M O
N M N
P PI P/DMQ ND ND
N N O O O O F M M M O M M O O O
M M O N O N N N N N N N N N N N
ND VS PI PO ND DMQ DM DM DMQ PO PO
ND
347
T13/1699-D Revision 3f
Table B.2 Command codes (sorted by command code) (part 3 of 3) Protocol Command Reserved Obsolete Retired Obsolete Obsolete STANDBY IMMEDIATE IDLE IMMEDIATE STANDBY IDLE READ BUFFER CHECK POWER MODE SLEEP FLUSH CACHE WRITE BUFFER Retired FLUSH CACHE EXT Reserved IDENTIFY DEVICE Obsolete Obsolete SET FEATURES Vendor Specific SECURITY SET PASSWORD SECURITY UNLOCK SECURITY ERASE PREPARE SECURITY ERASE UNIT SECURITY FREEZE LOCK SECURITY DISABLE PASSWORD Vendor Specific READ NATIVE MAX ADDRESS SET MAX ADDRESS Vendor Specific ND = Non-data command PI = PIO data-in command PO = PIO data-out command DM = DMA command DMQ = DMA QUEUED command DR = DEVICE RESET command DD = EXECUTE DEVICE DIAGNOSTIC command P = PACKET command VS = Vendor specific General Feature Set O O O M M M M O M M M O O M O M O O O O O O O O Packet Feature Set O N N M M O O N M M O N N M N M O O O O O O O O Command Code D2h-D9h DAh DBh-DDh DEh DFh E0h E1h E2h E3h E4h E5h E6h E7h E8h E9h EAh EBh ECh EDh EEh EFh F0h F1h F2h F3h F4h F5h F6h F7h F8h F9h FAh-FFh
ND ND ND ND PI ND ND ND PO ND PI
ND VS PO PO ND PO ND PO ND ND VS Key:
M = Mandatory O = Optional N = Use prohibited V = Vendor specific implementation E = Retired B = Obsolete R = Reserved F = If the device does not implement the CFA feature set, this command code is Vendor specific.
348
T13/1699-D Revision 3f
Editors Note 2: The following table is not being maintained and will be updated when the document is forwarded for letter ballot. Table B.3 Command codes (sorted by command name) (part 1 of 3) Protocol Command ND ND PI PO PO ND ND ND ND PI ND PO DR PO DD ND ND ND PI PI ND ND ND ND ND ND CFA ERASE SECTORS CFA REQUEST EXTENDED ERROR CFA TRANSLATE SECTOR CFA WRITE MULTIPLE WITHOUT ERASE CFA WRITE SECTORS WITHOUT ERASE CHECK MEDIA CARD TYPE CHECK POWER MODE CONFIGURE STREAM DEVICE CONFIGURATION FREEZE LOCK DEVICE CONFIGURATION IDENTIFY DEVICE CONFIGURATION RESTORE DEVICE CONFIGURATION SET DEVICE RESET DOWNLOAD MICROCODE EXECUTE DEVICE DIAGNOSTIC FLUSH CACHE FLUSH CACHE EXT GET MEDIA STATUS IDENTIFY DEVICE IDENTIFY PACKET DEVICE IDLE IDLE IMMEDIATE MEDIA EJECT MEDIA LOCK MEDIA UNLOCK NOP Obsolete PACKET READ BUFFER READ DMA READ DMA EXT READ DMA QUEUED READ DMA QUEUED EXT READ LOG DMA EXT READ LOG EXT READ MULTIPLE READ MULTIPLE EXT READ NATIVE MAX ADDRESS READ NATIVE MAX ADDRESS EXT General feature set Command code 91H F N C0h O N 03h O N 87h O N CDh O N 38h O N D1h M M E5h O O 51H O O B1h O O B1h O O B1h O O B1h N M 08h O N 92h M M 90h M O E7h O N EAh O O DAh M M ECh N M A1h M O E3h M M E1h O N EDh O N DEh O N DFh O M 00h 10h, 21h-23h, 31h, 32h-33h, 3Ch, 41h, 50h, 70h, C9h, CBh, EEh N M A0h O N E4h M N C8h O N 25h O N C7h O N 26h O O 47h O O 2Fh M N C4h O N 29h O O F8h O N 27h Packet Feature Set
P PI DM DM DMQ DMQ DM PI PI PI ND ND
349
T13/1699-D Revision 3f
Table B.3 Command codes (sorted by command name) (part 2 of 3) Protocol Command PI PI DM PI ND ND READ SECTOR(S) READ SECTOR(S) EXT READ STREAM DMA EXT READ STREAM EXT READ VERIFY SECTOR(S) READ VERIFY SECTOR(S) EXT Reserved General Packet Command feature set Feature Set code M M 20h O N 24h O N 2Ah O N 2Bh M N 40h O N 42h 01h-02h, 04h-07h, 09h-0fh, 28h, 2Ch-2Eh, 43h-44h, 46h, 48h-4Fh, 52h-6Fh, 93h, 9Bh-9Fh, A3h-AFh, B2h-B5h, B7h-BFh,CFh-D0h, D2h-D9h, EBh O O B6h 11h-1Fh,71h-7Fh, 94h-99h, DBh-DDh, E9h O O F6h O O F3h O O F4h O O F5h O O F1h O O F2h O O A2h M M EFh O O F9h O N 37h M N C6h M M E6h O N B0h O N B0h O N B0h O N B0h O N B0h O N B0h O N B0h O N B0h M O E2h M M E0h 80h-8Fh,9Ah,C1-C3h,F0h,F7h,FA-FFh O N E8h M N CAh O N 35h O N 3Dh O N CCh O N 36h O N 3Eh
Reserved for e05106 Retired PO ND PO ND PO PO P/DMQ ND ND ND ND ND ND ND ND ND PI PI ND PO ND ND VS PO DM DM DM DMQ DMQ DMQ SECURITY DISABLE PASSWORD SECURITY ERASE PREPARE SECURITY ERASE UNIT SECURITY FREEZE LOCK SECURITY SET PASSWORD SECURITY UNLOCK SERVICE SET FEATURES SET MAX ADDRESS SET MAX ADDRESS EXT SET MULTIPLE MODE SLEEP SMART DISABLE OPERATIONS SMART ENABLE OPERATIONS SMART ENABLE/DISABLE AUTOSAVE SMART EXECUTE OFF-LINE IMMEDIATE SMART READ DATA SMART READ LOG SMART RETURN STATUS SMART WRITE LOG STANDBY STANDBY IMMEDIATE Vendor Specific WRITE BUFFER WRITE DMA WRITE DMA EXT WRITE DMA FUA EXT WRITE DMA QUEUED WRITE DMA QUEUED EXT WRITE DMA QUEUED FUA EXT
350
T13/1699-D Revision 3f
Table B.3 Command codes (sorted by command name) (part 3 of 3) Protocol Command DM PO PO PO PO PO PO DM PO ND Key: WRITE LOG DMA EXT WRITE LOG EXT WRITE MULTIPLE WRITE MULTIPLE EXT WRITE MULTIPLE FUA EXT WRITE SECTOR(S) WRITE SECTOR(S) EXT WRITE STREAM DMA EXT WRITE STREAM EXT WRITE UNCORRECTABLE EXT ND = Non-data command PI = PIO data-in command PO = PIO data-out command DM = DMA command DMQ = DMA QUEUED command DR = DEVICE RESET command DD = EXECUTE DEVICE DIAGNOSTIC command P = PACKET command VS = Vendor specific General feature set O O M O O M O O O O Packet Feature Set O O N N N N N N N N Command code 57h 3Fh C5h 39h CEh 30h 34h 3Ah 3Bh 45h
M = Mandatory O = Optional N = Use prohibited V = Vendor specific implementation E = Retired B = Obsolete R = Reserved F = If the device does not implement the CFA feature set, this command code is Vendor specific.
351
T13/1699-D Revision 3f
Table B.4 Historical Command Assignments (part 1 of 6) Opcode Command Name 00h NO-OP 01h 02h CFA REQUEST EXTENDED 03h ERROR 04h 05h 06h 07h ATAPI Soft Reset / DEVICE 08h RESET 09h 0Ah 0Bh 0Ch 0Dh 0Eh 0Fh 10h RECALIBRATE 11h RECALIBRATE 12h RECALIBRATE 13h RECALIBRATE 14h RECALIBRATE 15h RECALIBRATE 16h RECALIBRATE 17h RECALIBRATE 18h RECALIBRATE 19h RECALIBRATE 1Ah RECALIBRATE 1Bh RECALIBRATE 1Ch RECALIBRATE 1Dh RECALIBRATE 1Eh RECALIBRATE 1Fh RECALIBRATE 20h READ SECTORS READ SECTORS WITHOUT 21h RETRY 22h READ LONG 23h READ LONG WITHOUT RETRY 24h READ SECTORS EXT 25h READ DMA EXT 26h READ DMA QUEUED EXT READ NATIVE MAX ADDRESS 27h EXT 28h ATA1 C R R R R R R R R R R R R R R R C C C C C C C C C C C C C C C C C C C C R R R R R ATA2 C R R R R R R R R R R R R R R R C C C C C C C C C C C C C C C C C C C C R R R R R ATA3 C R R R R R R R C R R R R R R R C O O O O O O O O O O O O O O O C C C C R R R R R ATA4 C R R C R R R R C R R R R R R R O E E E E E E E E E E E E E E E C C O O R R R R R ATA5 C R R C R R R R C R R R R R R R O E E E E E E E E E E E E E E E C O O O R R R R R ATA6 C R R C R R R R C R R R R R R R O E E E E E E E E E E E E E E E C O O O C C C C R ATA7 C R R C R R R R C R R R R R R R O E E E E E E E E E E E E E E E C O O O C C C C R ATA8 C R R C R R R R C R R R R R R R O E E E E E E E E E E E E E E E C O O O C C C C R
352
December 11, 2006 Table B.4 Historical Command Assignments (part 2 of 6) Opcode 29h 2Ah 2Bh 2Ch 2Dh 2Eh 2Fh 30h 31h 32h 33h 34h 35h 36h 37h 38h 39h 3Ah 3Bh 3Ch 3Dh 3Eh 3Fh 40h 41h 42h 43h 44h 45h 46h 47h 48h 49h 4Ah 4Bh 4Ch 4Dh 4Eh 4Fh 50h 51h 52h 53h Command Name READ MULTIPLE EXT READ STREAM DMA READ STREAM ATA1 R R R R R R R C C C C R R R R R R R R C R R R C C R R R R R R R R R R R R R R C R R R ATA2 R R R R R R R C C C C R R R R R R R R C R R R C C R R R R R R R R R R R R R R C R R R ATA3 R R R R R R R C C C C R R R R R R R R C R R R C C R R R R R R R R R R R R R R C R R R ATA4 R R R R R R R C C O O R R R R C R R R O R R R C C R R R R R R R R R R R R R R O R R R ATA5 R R R R R R R C O O O O R R R C R R R O R R R C O R R R R R R R R R R R R R R O R R R
T13/1699-D Revision 3f
READ LOG EXT WRITE SECTORS WRITE SECTORS WITHOUT RETRY WRITE LONG WRITE LONG WITHOUT RETRY WRITE SECTORS EXT WRITE DMA EXT WRITE DMA QUEUED EXT SET NATIVE MAX ADDRESS EXT CFA WRITE SECTORS WITHOUT ERASE WRITE MULTIPLE EXT WRITE STREAM DMA WRITE STREAM WRITE VERIFY WRITE DMA FUA EXT WRITE DMA QUEUED FUA EXT WRITE LOG EXT READ VERIFY SECTORS READ VERIFY SECTORS WITHOUT RETRY READ VERIFY SECTORS EXT
ATA6 C R R R R R C C O O O C C C C C C R R O R R C C O C R R R R R R R R R R R R R O R R R
ATA7 C C C R R R C C O O O C C C C C C C C O C C C C O C R R R R R R R R R R R R R O C R R
ATA8 C C C R R R C C O O O C C C C C C C C O C C C C O C R R C* R C* R R R R R R R R O C R R 353
T13/1699-D Revision 3f Table B.4 Historical Command Assignments (part 3 of 6) Opcode 54h 55h 56h 57h 58h 59h 5Ah 5Bh 5Ch 5Dh 5Eh 5Fh 60h 61h 62h 63h 64h 65h 66h 67h 68h 69h 6Ah 6Bh 6Ch 6Dh 6Eh 6Fh 70h 71h 72h 73h 74h 75h 76h 77h 78h 79h 7Ah 7Bh 7Ch 7Dh 7Eh 7Fh 80h 81h Command Name ATA1 R R R R R R R R R R R R R R R R R R R R R R R R R R R R C C C C C C C C C C C C C C C C V V ATA2 R R R R R R R R R R R R R R R R R R R R R R R R R R R R C C C C C C C C C C C C C C C C V V ATA3 R R R R R R R R R R R R R R R R R R R R R R R R R R R R C O O O O O O O O O O O O O O O V V ATA4 R R R R R R R R R R R R R R R R R R R R R R R R R R R R C E E E E E E E E E E E E E E E V V ATA5 R R R R R R R R R R R R R R R R R R R R R R R R R R R R C E E E E E E E E E E E E E E E V V
TRUSTED RECEIVE TRUSTED RECEIVE DMA TRUSTED SEND TRUSTED SEND DMA SATA (reserved) SATA (reserved) SATA (reserved) SATA (reserved) SATA (reserved) SATA (reserved) SATA (reserved) SATA (reserved)
SEEK SEEK SEEK SEEK SEEK SEEK SEEK SEEK SEEK SEEK SEEK SEEK SEEK SEEK SEEK SEEK (vendor specific) (vendor specific)
ATA6 R R R R R R R R R R R R R R R R R R R R R R R R R R R R C E E E E E E E E E E E E E E E V V
ATA7 R R R R R R R R R R R R S S S S S S S S S S S S S S S S O E E E E E E E E E E E E E E E V V
ATA8 R R R C* R R R R C* C* C* C* S S S S S S S S S S S S S S S S O E E E E E E E E E E E E E E E V V
354
December 11, 2006 Table B.4 Historical Command Assignments (part 4 of 6) Opcode 82h 83h 84h 85h 86h 87h 88h 89h 8Ah 8Bh 8Ch 8Dh 8Eh 8Fh 90h 91h 92h 93h 94h 95h 96h 97h 98h 99h 9Ah 9Bh 9Ch 9Dh 9Eh 9Fh A0h A1h A2h A3h A4h A5h A6h A7h A8h A9h AAh ABh ACh ADh Command Name (vendor specific) (vendor specific) (vendor specific) (vendor specific) (vendor specific) (vendor specific) / CFA TRANSLATE SECTOR (vendor specific) (vendor specific) (vendor specific) (vendor specific) (vendor specific) (vendor specific) (vendor specific) (vendor specific) EXECUTE DEVICE DIAGNOSTICS INITIALIZE DEVICE PARAMETERS DOWNLOAD MICROCODE STANDBY IMMEDIATE IDLE IMMEDIATE STANDBY IDLE CHECK POWER MODE SLEEP (vendor specific) ATA1 V V V V V V V V V V V V V V C C R R C C C C C C V R R R R R R R R R R R R R R R R R R R ATA2 V V V V V V V V V V V V V V C C C R C C C C C C V R R R R R R R R R R R R R R R R R R R ATA3 V V V V V V V V V V V V V V C C C R C C C C C C V R R R R R C C C R R R R R R R R R R R ATA4 V V V V V F V V V V V V V V C C C R E E E E E E V R R R R R C C C R R R R R R R R R R R ATA5 V V V V V F V V V V V V V V C C C R E E E E E E V R R R R R C C C R R R R R R R R R R R
T13/1699-D Revision 3f
ATA6 V V V V V F V V V V V V V V C O C R E E E E E E V R R R R R C C C R R R R R R R R R R R
ATA7 V V V V V F V V V V V V V V C O C R E E E E E E V R R R R R C C C R R R R R R R R R R R
ATA8 V V V V V F V V V V V V V V C O C R E E E E E E V R R R R R C C C R R R R R R R R R R R 355
T13/1699-D Revision 3f Table B.4 Historical Command Assignments (part 5 of 6) Opcode AEh AFh B0h B1h B2h B3h B4h B5h B6h B7h B8h B9h BAh BBh BCh BDh BEh BFh C0h C1h C2h C3h C4h C5h C6h C7h C8h C9h CAh CBh CCh CDh CEh CFh D0h D1h D2h D3h D4h D5h D6h D7h D8h D9h DAh 356 Command Name ATA1 R R R R R R R R R R R R R R R R R R V V V V C C C R C C C C R R R R R R R R R R R R R R R ATA2 R R R R R R R R R R R R R R R R R R V V V V C C C R C C C C R R R R R R R R R R R R R R R ATA3 R R C R R R R R R R R R R R R R R R V V V V C C C R C C C C R R R R R R R R R R R R R R R ATA4 R R C R R R R R R R R R R R R R R R F V V V C C C C C C C C C C R R R R R R R R R R R R C ATA5 R R C R R R R R R R A A A A A A A A F V V V C C C C C O C O C C R R R R R R R R R R R R C
NV CACHE CFA (reserved) CFA (reserved) CFA (reserved) CFA (reserved) CFA (reserved) CFA (reserved) CFA (reserved) CFA (reserved) (vendor specific) / CFA ERASE SECTORS (vendor specific) (vendor specific) (vendor specific) READ MULTIPLE WRITE MULTIPLE SET MULTIPLE MODE READ DMA QUEUED READ DMA READ DMA WITHOUT RETRIES WRITE DMA WRITE DMA WITHOUT RETRIES WRITE DMA QUEUED CFA WRITE MULTIPLE WITHOUT ERASE WRITE MULTIPLE FUA EXT
ATA6 R R C C R R R R R R A A A A A A A A F V V V C C C C C O C O C C R R R C M M M R R R R R C
ATA7 R R C C R R R R R R A A A A A A A A F V V V C C C C C O C O C C C R R C M M M R R R R R C
ATA8 R R C C R R R R C* R A A A A A A A A F V V V C C C C C O C O C C C R R C M M M R R R R R O
CHECK MEDIA CARD TYPE Media Card Pass Thru Media Card Pass Thru Media Card Pass Thru
December 11, 2006 Table B.4 Historical Command Assignments (part 6 of 6) Opcode Command Name ACKNOWLEDGE MEDIA DBh CHANGE DCh BOOT POST BOOT DDh BOOT PRE BOOT DEh MEDIA LOCK DFh MEDIA UNLOCK E0h STANDBY IMMEDIATE E1h IDLE IMMEDIATE E2h STANDBY E3h IDLE E4h READ BUFFER E5h CHECK POWER MODE E6h SLEEP E7h FLUSH CACHE E8h WRITE BUFFER E9h WRITE SAME EAh FLUSH CACHE EXT EBh ECh IDENTIFY DEVICE EDh MEDIA EJECT EEh IDENTIFY DEVICE DMA EFh SET FEATURES F0h (vendor specific) F1h SECURITY SET PASSWORD F2h SECURITY UNLOCK F3h SECURITY ERASE PREPARE F4h SECURITY ERASE UNIT F5h SECURITY FREEZE LOCK SECURITY DISABLE F6h PASSWORD F7h (vendor specific) F8h READ NATIVE MAX ADDRESS F9h SET MAX ADDRESS FAh (vendor specific) FBh (vendor specific) FCh (vendor specific) FDh (vendor specific) FEh (vendor specific) FFh (vendor specific) Key: C = a defined command. E = a retired command. O = Obsolete. R = Reserved, undefined in current specifications. V = Vendor specific commands. ATA1 C C C C C C C C C C C C R C C R R C R R C V V V V V V V ATA2 C C C C C C C C C C C C R C C R R C C R C V V V V V V V ATA3 O O O C C C C C C C C C R C O R R C C C C V C C C C C C ATA4 E E E C C C C C C C C C C C E R R C C O C V C C C C C C ATA5 E E E C C C C C C C C C C C E R R C C O C V C C C C C C
T13/1699-D Revision 3f
ATA6 E E E C C C C C C C C C C C E C R C C O C V C C C C C C
ATA7 E E E C C C C C C C C C C C E C R C C O C V C C C C C C
ATA8 E E E O O C C C C C C C C C E C R C O O C V C C C C C C
V V V V V V V V V V V C C C C C V V V C C C C C V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V V A = Reserved for assignment by the CompactFlash Association F = If the device does not implement the CFA feature set, this command code is Vendor specific. M = Reserved for the Media Card Pass Through Command feature set. S = Reserved for Serial ATA *Indicates this definition is new to ATA8
357
T13/1699-D Revision 3f
Table B.5 Historical SET FEATURE Code Assignments (part 1 of 3) Feature Description Code 01h Enable 8-bit data transfers 02h Enable write cache 03h Set transfer mode based on value in the count field 04h Enable all automatic defect reassignment 05h Enable advanced power management 06h Enable Power-Up in Standby feature set 07h Power-up in Standby feature set device spin-up 09h Reserved for Address offset reserved boot area method technical report 0Ah Enable CFA power mode 1 20h Reserved for Technical Report (T13/DT1696) 21h Reserved for Technical Report (T13/DT1696) 31h Disable Media Status Notification 33h Disable retry 42h Enable Automatic Acoustic Management feature set 43h Set Maximum Host Interface Sector Times 44h Vendor specific length of ECC on read long/write long commands 54h Set cache segments to the count field value 55h Disable read look-ahead feature 5Dh Enable release interrupt 5Eh Enable SERVICE interrupt 66h Disable reverting to power on defaults 77h Disable ECC 81h Disable 8-bit data transfers 82h Disable write cache 84h Disable all automatic defect reassignment 85h Disable advanced power management 86h Disable Power-Up in Standby feature set 358 ATA1 C V C R R R R R ATA2 C V C R R R R R ATA3 O C C C R R R R ATA4 E C C O C R R R ATA5 F C C O C C C C ATA6 F C C O C C C C ATA7 F C C O C C C C ATA8 F C C O C C C C
R R R R V R R C
R R R R V R R C
R R R R C R R C
R R R C C R R O
C R R C O R R O
C R R C O R R O
C T T C O C C O
C T T O O C C O
V C R R C V C V R R R
V C R R C V C V R R R
C C R R C C O C C R R
O C C C C O E C O C R
O C C C C O F C O C C
O C C C C O F C O C C
O C C C C O F C O C C
O C C C C O F C O C C
T13/1699-D Revision 3f
Table B.5 Historical SET FEATURE Code Assignments (part 2 of 3) Feature Description Code 88h Enable ECC 89h Reserved for Address offset reserved boot area method technical report 8Ah Disable CFA power mode 1 90h Reserved for Serial ATA 95h Enable Media Status Notification 99h Enable retries 9Ah Set device maximum average current AAh Enable read look-ahead features ABh Set maximum prefetch using the count field value BBh 4 bytes of ECC apply on read long/write long commands C2h Disable Automatic Acoustic Management feature set CCh Enable reverting to power on defaults DDh Disable release interrupt DEh Disable SERVICE interrupt ATA1 V R ATA2 V R ATA3 C R ATA4 C R ATA5 C C ATA6 O C ATA7 O C ATA8 O C
R R R V R C V C R C R R
R R R V R C V C R C R R
R R R C C C C C R C R R
R R C O O C O O R C C C
C R C O O C O O R C C C
C R C O O C O O R C C C
F S C O O C O O C C C C
F S O O O C O O C C C C
359
T13/1699-D Revision 3f
Table B.5 Historical SET FEATURE Code Assignments (part 3 of 3) Feature Description Code E0h Vendor specific E1h Vendor specific E2h Vendor specific F0h F1h F2h F3h F4h F5h F6h F7h F8h F9h FAh FBh FCh FDh FEh FFh Key: C = a defined command. E = a retired command. O = Obsolete. R = Reserved, undefined in current specifications. V = Vendor specific commands. ATA1 ATA2 ATA3 ATA4 ATA5 ATA6 ATA7 ATA8
R R R R R R O O R R R R R R O O R R R R R R O O R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A R R R R A A A A A = Reserved for assignment by the CompactFlash? Association. F = If the device does not implement the CFA feature set, this command code is Vendor specific. M = Reserved for the Media Card Pass Through Command feature set. S = Reserved for Serial ATA. T = Reserved for Technical Report T13/DT1696 (Time-Limited Commands).
360
T13/1699-D Revision 3f
Annex C
(Informative)
Design and programming considerations for large physical sector devices C.1 Introduction
In ATA standards preceding ATA/ATAPI-7, interface the smallest addressable unit of data has been the 512 byte sector. In hard disk drives each sector has an associated error correcting code field to allow detection and correction of read errors. Over time, error correcting code fields have been lengthened to provide greater detection and correction capability. As a result, the proportion of device media devoted to ECC fields has risen. Increasing the length of data sectors on the media increases the efficiency of ECC by enabling better error detection and correction using a smaller proportion of media.
Media Layout
While allowing logical sector to be smaller than a physical sector maintains software compatibility it introduces 2048aByte Physical Sector 0 be avoided. Physical Sector 1must be written to the a potential performance issue, unaligned write, which must A physical sector Physical media in a single operation. To complete a write command that writes a fraction of a physical sector the device LBA0 LBA1 LBA2 LBA3 LBA5 LBA6 LBA 7data and then must read the entire physical sector into buffer memory update LBA4 the buffer memory with the write Sector write the entire physical sector to the media. This may incur a performance penalty of one media revolution or Device more. Write commands may begin mid physical sector and end mid physical sector resulting in two unaligned writes. In this case the device has to read both the beginning and ending physical sector of the write into the buffer. Unaligned Write Operation To avoid the performance penalty from an unaligned write all write operations must begin with the first sector of a physical sector and end with the last sector of a physical sector. LBA3 Figure 10 illustrates an unaligned write on a device with 2048 byte physical sectors. The first four logical sectors, LBA 3 Write LBA0 - LBA3, reside on physical sector 0. To write only LBA3 the host sends a conventional write command and the data for LBA3. On receipt of the write command the device seeks to the physical sector that contains LBA3, From Host which is physical sector 0. Physical sector 0 is read into the device buffer. Then the new write data for LBA3 is Physical placed in the buffer, overwriting a segment of the buffer. The buffer data is then written to the media, physical Physical Sector 0 Physical Sector 1 sector 0. Sector 0
361
T13/1699-D Revision 3f
362
T13/1699-D Revision 3f
Annex D
(Informative)
How to use SCT commands D.1 How to use SCT commands overview
SCT commands piggy-back on the standard ATA commands: SMART READ LOG and SMART WRITE LOG, or READ LOG EXT and WRITE LOG EXT. As viewed through an ATA protocol analyzer, an SCT command is seen as data being transferred by these commands; whereas from the perspective of a device that implements this feature set, this data would be interpreted as an SCT command request, an SCT command response, SCT command status, or SCT command data.
363
T13/1699-D Revision 3f
Figure D.1 is an example flowchart that shows how to process SCT commands using SMART READ LOG and SMART WRITE LOG commands:
Command to Drive
Command Register
Not B0
B0
D6
Feature Register
D5
Not D5 or D6
No Error
E0
Sector Number
E1
E1
Sector Number
E0
Not E0 or E1
Not E0 or E1
No
No
Smart Enabled
Yes
No Yes Process Write Logging Command Yes Process Read Logging Command
364
T13/1699-D Revision 3f
Device
Figure D.2 Example sequence for foreground write same with a repeating pattern Figure D.3 shows an example of a foreground write same with a repeating sector.
Device
365
T13/1699-D Revision 3f
Figure D.4 shows an example command sequence for writing data to a device using an SCT command with no background activity.
Device
Device
Read Log Address E0h (SCT Status) SCT Status (SCT Command Complete) Command Completion
Figure D.5 Example sequence for reading data using an SCT command with no background activity
366
T13/1699-D Revision 3f
Figure D.6 shows an example command sequence for issuing a Log page command that does not transfer data and has no background activity.
Device
Read Log Address E0h (SCT Status) SCT Status (SCT Command still in Progress) Command Completion
Figure D.6 Example Sequence for a non-data SCT command with no background activity
367
T13/1699-D Revision 3f
Figure D.7 shows an example command sequence for issuing an SCT command that writes data in the background.
Device
Read Log Address E0h (SCT Status) SCT Status (SCT Command still in Progress) Command Completion ... Read Log Address E0h (SCT Status) SCT Status (SCT Command still in Progress) Command Completion Read Log Address E0h (SCT Status) SCT Status (SCT Command Complete) Command Completion
Figure D.7 Example sequence for writing data using an SCT command with background activity
368
T13/1699-D Revision 3f
Figure D.8 shows an example command sequence for issuing an SCT command that executes in the background but does not require the transfer of data to or from the host.
Device
Read Log Address E0h (SCT Status) SCT Status (SCT Command still in Progress) Command Completion ... Read Log Address E0h (SCT Status) SCT Status (SCT Command still in Progress) Command Completion Read Log Address E0h (SCT Status) SCT Status (SCT Command Complete) Command Completion
Figure D.8 Example sequence for a non-data SCT command with background activity
369
The host issues the SCT command (see table 151 or table 152), and sends the key sector to the device. Table 151 SCT command using SMART WRITE LOG command Word 00h 01h 02h-04h Name Feature Count LBA Description D6h - SMART WRITE LOG 01h (Shall always be 01h Bit 47:2 4 23:8 7:0 05h Command B0h Description Reserved C24Fh E0h (Command port)
Table 152 SCT command using WRITE LOG EXT command Word 00h 01h 02h-04h Name Feature Count LBA Description Reserved 01h 1 sector for SCT commands Bit 47:32 31:16 15:8 7:0 05h Command 3Fh Description Reserved 00h There is no offset when commands are issued Reserved E0h
The device responds with successful status (see table 53). If the command is aborted (i.e., Status = 51h and Error = 04h), then either the key sector format is invalid, the task file contains an invalid value or the command encountered an execution error. The host checks the Count and LBA (7:0) fields for the error code (see table 54 and table 55). If the command was a write command, the command is terminated, there is no data transfer, and the host skips Step 3. However, if the command was a read command, there maybe partial output available. For example, on a sector read command, the data up to and including the sector in error is available. In this case, the host may proceed to Step 3 to get the partial data. In certain cases the error is not fatal and serves only as a warning. If the status is 50h, then the host checks the LBA Mid and LBA High fields. If the values are 0, then the command is complete, terminated without error, and the host proceeds to Step 4. If the values are greater than 0, then the host proceeds to Step 3. D.3.3 Step 3 - Transfer Data if Required To transfer data from the device to the host, the host issues a SMART READ LOG or READ LOG EXT command to address E1h (see table 56 and table 57). To transfer data from the host to the device, the host issues a SMART WRITE LOG or WRITE LOG EXT command to address E1h (see table 56 and table 57). The transfer request is in the range of 1 sector up to the total number of sectors not yet transferred. The number of sectors remaining was posted in the LBA (23:8) field in the previous step. If the requested number of sectors is larger than the number of the sectors remaining, the device reports an error. If the value is less then the number of sectors remaining, the host may repeat Step 3 until all sectors have been transferred.
370
T13/1699-D Revision 3f
For SCT commands that access the media, the device advances the sector pointer by the number of sectors transferred, and reports in the LBA (23:8) field the number of sectors remaining to be transferred. If both fields contain zero, then the command is complete, and the host proceeds to Step 4. The host has complete control over the number of sectors to transfer at a time. Note, if the number of sectors to be transferred is greater or equal to FFFFh, the device sets the LBA Mid and High fields to FFFFh. The value remains FFFFh until the number of sectors remaining drops below FFFFh. The exact number to be transferred is reported by the SCT Status command. Upon receiving the last block of data, the device performs the specified operation. In the case of very large amounts of data, such as Write Same, some data may be processed (e.g., written to the disk) prior to receiving all of the data from the host. D.3.4 Step 4 - Final Status/SCT Command Completion The host reads the SCT status response (see table 58, table 59, and table 60) to determine how the command completed. If the command has not completed (i.e., by reporting FFFFh in table 60 byte 14) then the host waits for some period of time and repeats Step 4 until the command is complete. For SCT commands that require transfer of data to the device (e.g., a write command), the command is not complete until the last block of data has been transferred to the device.
371