Specifications

SATA-IO Confidential 89
3.2.2. SYS-01: System Interoperability Test Requirements
3.2.2.1. Data Pattern
The data pattern used by System Interoperability test shall exactly reproduce the Long COMP pattern on the SATA
interface. The host typically scrambles and encodes the data before it is transmitted on the SATA interface. The
source data pattern shall be designed to take this into consideration such that the Long COMP pattern is still
presented on the SATA interface.
3.2.2.2. FIS Alignment and size
The System Interoperability test shall present (for writes) or request (for reads) the first byte of each data pattern be
the first byte of a data FIS. Subsequent data FIS alignment is highly suggested but not required. Usage of 8KB data
FISs is highly suggested but not required. The reason is the Long COMP data pattern is 8KB and 8KB FIS usage
keeps the designed pre-disparity pre-scrambling intact.
3.2.2.3. Serror and Sstatus host registers
The System Interoperability test should monitor, if possible, the host Serror and Sstatus registers.
• SERROR: If any bit in the Serror register (Bit W shall be excluded), it shall be counted as an error and
cleared.
• SSTATUS: Any change on the Sstatus:SPD bits shall be counted as an error.
3.2.2.4. Data Pattern sizes
The data pattern shall use all of the following pattern sizes in the prescribed combination. The 8 KB (Kilo Bytes) data
pattern is one complete Long COMP data pattern as defined above. Each additional pattern size is defined as exact
repeating multiples of the 8 KB data pattern. Each size represents a binary value NOT a decimal value (i.e. 8 KB = 8 *
1024 = 8192 Bytes, 1 MB = 1 * 1024 * 1024 = 1048576 Bytes)
• 8 KB
• 64 KB
• 256 KB
• 1 MB
• 16 MB
The purpose of using multiple size files is to strike a balance between guaranteed being 8 KB FIS aligned and
increased data throughput that is gained with larger file sizes. In addition, the smaller file sizes have a high likelihood
of being cached on many products, and thus achieving higher burst transfer rates, whereas the larger files increase
the devices media access interactions
3.2.2.5. Host caching and retries
The System Interoperability test must be configured such that:
1) No host caching of data is performed. All transfer requests shall be presented on the SATA interface.
2) The host is only allowed to retry non-data FIS’s without notification to the test tool
3) The host shall NOT retry data without notification to the test tool
3.2.2.6. Data file signatures
Each data file shall have a stored industry standard 128-bit MD5 signature that shall be used for data validity
verification. The test tool shall use MD5 signatures supplied by the SATA-IO.
3.2.2.7. HDD Data Pattern set
For a HDD PUT a single data pattern set is defined as follows:
1. 8 KB file - 40 generational copies, last file signature verified
2. 64 KB file – 40 generational copies, last file signature verified
3. 256 KB file – 40 generational copies, last file signature verified
4. 1 MB file – 40 generational copies, last file signature verified
5. 16 MB file – 40 generational copies, last file signature verified
A generational copy is defined as follows: