BIST-SCT Command Proposal

Similar documents
SATA-IO Commands for ATA-8

ATA Command Pass-Through

ATA Command Pass-Through

SCT LBA Segment Access Command Extension Proposal

Table 1 Revision History

ACS Proposal - Device Internal Status Log

ATA Command Pass-Through

TRIM DRAT / RZAT clarifications for ATA8-ACS2

ACS Proposal Template

24 October r2 SAS-2 Support multiple STP affiliations

External Path Protection

10.2 SCSI application layer

Block Data is the data transferred to or from the device using SCT Command Transport feature set capabilities.

White Paper Western Digital Comments on Sector Sizes Larger than 512 Bytes

Information Technology - SMART Command Transport (SCT)

Information Technology - SMART Command Transport (SCT)

SCT LBA Segment Access Command Extension Proposal October Revision 0

T10/06-119r0 SAS-2 BREAK_REPLY 28 February 2006

ATA Power Management SATA Device Initiated Power Management (DIPM)

ACS Proposal - Device Crashdump Collection

Technical Note. SMART Command Feature Set for the M500DC. Introduction. TN-FD-26: M500DC SSD SMART Implimentation. Introduction

Technical Note. SMART Command Feature Set for the M510DC. Introduction. TN-FD-33: M510DC SSD SMART Implementation. Introduction

Serial ATA Interoperability Program Revision 1.4 JDSU MOI for Device Digital Tests (ASR, GTR, NCQ, SSP, IPM and DOF)

06-378r0: SAT - Miscellaneous changes 18 August 2006

Technical Note. SMART Command Feature Set for the Introduction. TN-FD-34: 5100 SSD SMART Implementation. Introduction

16 June 2007 e07129r1 ATA8-ACS Endianness clarifications

Extended Power Conditions (EPC)

2 September r0 SAT-2 ATA PASS-THROUGH sense data format

8 January r3 SAS-2 More counters

r5 09 December 2008

04-340r0 SAS-1.1 OPEN_REJECT BAD DESTINATION handling 18 October 2004

04-172r1 SAS-2 More counters 11 September 2005

Serial ATA International Organization

SATA-IP Host reference design on KC705 manual

ACS Coordinating Device Maintenance

2 May r2 SAS-2 WWN-based Attached Device Name for SATA

Figure 1 SATA Communitcation Layer

26 April r0 SAT-2 WRITE LONG to WRITE UNCORRECTABLE EXT

4 November r4 SAS-2 Far-end retimed loopback phy test function

Proposal For A General Purpose Logging Feature Set

ACS-2 PUIS Update to Power Management States

Revision History Revision 0 (09 December 2007) first revision

04-340r1 SAS-1.1 OPEN_REJECT BAD DESTINATION handling 24 December 2004

Revision history Related documents Overview Suggested changes to SAT Approved references

1 Overview. 2 Changes to SPC-4. T10/ revision 5

04-352r0 SAS-1.1 Phy test functions for SMP 29 October 2004

Assignments for Trusted Computing Group

9 January r0 SAS-2 SPC-4 Enabling and disabling Transport Layer Retries

1 Overview. T10/ revision 0

Renice X2 1.8 micro SATA SSD DATA Sheet

SATA AHCI-IP reference design manual Rev1.3 1-Mar Overview

InnoDisk SATADOM i100 Datasheet

Product Specification

TrustedFlash Security System Mapping for ATA-ACS8

Table 180 REPORT GENERAL request. Byte\Bit SMP FRAME TYPE (40h) 4 (MSB) CRC (LSB)

Table 21. OOB signal transmitter requirements Idle time minimum. maximum 175 ns

SASTracer / Trainer. SASTracer/Trainer Overview

SFF Committee Specification for. Self-Monitoring, Analysis and Reporting Technology (S.M.A.R.T.) SFF-8035i Revision 2.0

2.5 Solid State Disk. Description. Features. Placement. Dimensions. Transcend Information Inc. Side Millimeters Inches

SMART Self-Test Reference for P400e SATA SSDs

Silicon Media Limited. C4 2.5 SATA Solid State Drive Specification (7mm & 9mm height compatible) SMSS325MxxxG-C4-x

Serial ATA core with cryptography support. Bc. Martin Chloupek

Sanitize Device Ext Command

Technical Note. Client SATA SSD SMART Attribute Reference. Introduction. TN-FD-22: Client SATA SSD SMART Attribute Reference.

Table 21. OOB signal transmitter requirements Idle time minimum. maximum 175 ns

1.8 Solid State Drive

06-078r3 SAS-2 Expander Route Table (REPORT EXPANDER ROUTE TABLE) 21 June 2006

SATA PHY Design Manual

SQFlash CFast Card (SLC) CFast Card (SLC) Datasheet

Overview The OOB timing requirements need to be more precise, listing the transmit burst time and specifying receiver tolerances.

SERIAL ATTACHED SCSI (SAS) CONSORTIUM

Serial ATA International Organization

Revision 6: Red text Incorporate comments from January 5, 2004 conference call. Minor wording changes.

INTERNATIONAL STANDARD

SATA-IP Device reference design manual

Series. Customer. InnoDisk. Approver. Approver. Customer: Customer. Part Number: InnoDisk. Part Number: InnoDisk.

4 General. 4.1 Architecture. T10/ revision 1

T10/01-134r Page 1 of 13

4 General. 4.1 Architecture. T10/ revision 4

03-346r2 SAS-1.1 Pathway recovery priority corrections 3 November 2003

INT 13 command: SCSI Pass Through Proposal

Serial Attached SCSI Link layer part 2

04-247r0 SAS-1.1 XL6 and idle dwords 8 September 2004

CFast Module. Industrial Design and Durability. Made in the USA 5/8/2014. Version 1.0 Page 1

ADT Frame Format Notes (Paul Suhler) ADI ADT Frame Format Proposal (Rod Wideman)

Stratix4 GX SATA3 RAID Demo Instruction Rev Oct-12

ExpressSAS Host Adapter 6Gb v2.30 Windows

Storage Protocol Analyzers: Not Just for R & D Anymore. Brandy Barton, Medusa Labs - Finisar

4 July r1 SAS-2 Enable and disable zoning

FORESEE SATAIII 2.5 inch SSD S900 Datasheet

ExpressSAS Host Adapter 6Gb v2.10 Windows

BIOS Enhanced Disk Drive Specification. June 24, 1999

The T13 Committee held and Ad Hoc Teleconference on September 19, 2003 at 9:00 am PDT.

Design Challenges Using the New Device Sleep (DevSlp) Standard

Industrial SATA Flash Module. Product Data Sheet

TCG Storage Interface Interactions Specification (SIIS) Specification Version 1.02 Revision December, 2011 TCG

Intel Storage System JBOD 2000S3 Product Family

Figure 1 SATA Communication Layer

6 May 2008 T10/08-018r3

ADATA Technology Corp.

Transcription:

BIST-SCT Command Proposal Revision 1 Technical Editor: Curtis E. Stevens Western Digital 20511 Lake Forest Lake Forest, Ca. 92630 USA Phone: 949-672-7933 E-Mail: Curtis.Stevens@WDC.com

Revision History Date Revision Description 12-Oct-04 0 1. Initial Draft 7-Dec-04 1 1. Removed references to SATA phy counters 2. Changed language to refer to ATA/ATAPI-7 3. Reformatted proposed log page to include a Tag and test time. 4. Made it clear that gathering of BIST Statistics was not required 5. Made it clear that the BIST Statistics Log Page is optional T13/e04148r0 Page ii

Table of Contents 1 INTRODUCTION...1 2 SCOPE...1 2.1 DEFINITION OF TERMS... 1 2.1.1 No Terms Yet... 1 3 OVERVIEW...2 4 SCT BIST ACTIVATE...3 4.1 DESCRIPTION... 3 4.2 INPUTS... 4 4.3 OUTPUTS... 5 5 BIST COUNTERS LOG PAGE...5 T13/e04148r0 Page iii

List of Figures Figure 1 - BIST Initiation... 2 List of Tables Table 1 - BIST Statistics Log Page... 5 T13/e04148r0 Page iv

1 Introduction ATA/ATAPI-7 has defined a serial based transport for ATA devices. This transport provides capabilities similar to the Parallel interface for ATA devices. The serial transport has new management capabilities that address the serial nature of the bus. This proposal provides a way to trigger the self-test capabilities (BIST & BERT) that are built into SATA devices. 2 Scope The purpose of this specification is to provide a standard way to initiate the Built-In Self-Test (BIST) and Bit Error Rate Test (BERT) capabilities of SATA devices, and to return the results of the test. 2.1 Definition of Terms 2.1.1 No Terms Yet T13/e04148r0 Page 1

3 Overview BIST allows ATA/ATAPI-7 SATA HBA and an ATA/ATAPI-7 SATA device to test the physical connections by entering a loopback or transmit mode. If the ATA/ATAPI-7 SATA HBA is testing its link with the device, the host driver instructs the HBA to issue a BIST HD FIS to the device. When the device receives the FIS, it responds with R_OK. After some handshaking, the HBA will then begin sending a repeating data pattern when loopback mode was selected. The drive shall return the pattern to the HBA according to the requirements specified in the BIST FIS. This test requires that a driver be able to cause the HBA to issue a BIST HD FIS and that the attached SATA device be able to act on the BIST HD FIS. There are occasions where the device needs to initiate BIST in the HBA. This capability allows the device to validate the connections on both sides as well as the HBA Link and HBA phy. There is currently no standard way to cause the device to send a BIST DH FIS. This specification documents a method for initiating BIST mode in an HBA using an ATA/ATAPI-7 SATA device. Figure 1 shows the communication required for performing device initiated BIST: Host Figure 1 - BIST Initiation Device SCT Request BIST DH FIS SATA R_OK SATA Register DH FIS Status = 50h SATA R_OK SATA BIST DH FIS SATA R_OK SATA Sync SATA Sync (optional) BIST Data COMRESET/COMINIT T13/e04148r0 Page 2

4 SCT BIST Request 4.1 Description When the device initiates the BIST process by sending a BIST DH FIS to the host, if the device supports the gathering of error statistics, the device shall clear the statistics prior to sending the first BIST data. Once BIST starts, the statistics may be updated using the BIST data transfer information. If the BIST timer expires, the statistics may be saved in Log Page A0h - BIST Statistics Log Page (See Section 5). The device shall then issue COMINIT to cause the host to exit BIST mode and enter the idle mode. If the host initiates a device driven test with a non-zero timeout, the BIST Statistics Log Page reflects the true test statistics. If BIST is terminated by COMRESET at any time, the statistics may be saved in the BIST Statistics Log Page, but the statistics may include a random number of errors caused by the COMRESET process. Both COMRESET and timer expiration properly terminate BIST and allow the statistics to be saved. If BIST is aborted by removing power from the device, then BIST was terminated improperly and the BIST Statistics Log page is not updated to reflect the new statistics. If an Asynchronous Signal Loss (ASL) occurs, Asynchronous Signal Recovery (ASR) shall not be performed. The device shall not attempt to issue COMINIT until the timeout timer has expired. The HBA shall not exit BIST until a COMINIT is received or the HBA is instructed to exit BIST by the host. ASL may cause inaccurate statistics reporting. T13/e04148r0 Page 3

4.2 Inputs Byte Name Value Description 00h Action Code C001h Begin Self-Test 02h Function Code 0001h Request BIST FIS 04h Modes DWord Bit (1) Description 31:8 Reserved 7 Far End Transmit Only 6 Align Bypass (Only checked when Bit 7=1) 5 Bypass Scrambling (Only checked when Bit 7=1) 4 Far End Retimed Loopback (2) 3 Far End Analog Loopback (2) 2 Primitive Bit (Only checked when Bit 7=1) 1 Reserved 0 Vendor Specific Notes (1) ATA/ATAPI-7 Volume 3 clause 16.5.7 for the definition of how these bits are used. (2) ATA/ATAPI-7 Volume 3 clause 14.4 for a description of some standard loopback patterns 08h Pattern 1 DWord Pattern 1 (Only used when Bit 7=1) 0Ch Pattern 2 DWord Pattern 2 (Only used when Bit 7=1) 10h Timeout DWord 14h Tag DWord Test time in seconds. If this field is 0, the device shall perform the requested test until it receives a COMRESET, or a power cycle occurs. Test Tag. Test Tag is provided by the host to identify test results. When BIST is terminated the results are reported in the BIST Statistics Log Page if the drive supports the storing of BIST statistics in a log page. Test Tag is stored in the log page to identify to the host that BIST was terminated in a manner that allowed the test statistics to be stored. T13/e04148r0 Page 4

4.3 Outputs Field Name Error Sector Count LBA Low LBA Mid LBA High Device Status See ATA/ATAPI-7 See ATA/ATAPI-7 Value 5 BIST Statistics Log Page Western Digital has assigned Vendor Specific Log Page A0h as a holding place for the optional BIST Statistics Log Page. See Table 1 for the formatting of this log page. The statistics are reported in a vendor specific format. If the BIST was properly terminated (by timeout or COMRESET), then the phy/link statistics are reported as they were at the receipt of the last BIST data and are stored in the BIST Statistics Log Page. Note that if BIST is terminated by COMRESET that the COMRESET process may skew BIST statistics. If power is removed from the device prior to BIST completion, then the BIST Statistics Log Page is not updated. The values in the BIST Statistics Log Page shall always reflect the result of the last properly terminated BIST, even across power cycles. If no BIST has been performed on the device, the BIST Statistics Log Page shall be initialized with all zeros. This condition shall remain until a properly terminated BIST has been performed. Table 1 - BIST Statistics Log Page Byte Type Description 503:0 Byte BIST Statistics. 504 bytes are allocated to the reporting of BIST statistics in a vendor specific format 507:504 DWord Test Time. Test Time is the number of seconds that BIST was performed 511:508 DWord Test Tag. Test Tag is the Tag provided by the host in the SCT BIST Request T13/e04148r0 Page 5