Specifications

SATA-IO Confidential 90
1. First read of the copy, comes from the original data source, not the PUT
2. The first write, using the data from the first read is written to the PUT
3. The second read comes from the first write data on the PUT
4. The second write comes from the second read, but writes to a 2
nd
file location on the PUT
5. ….
6. The 39
th
read comes from the 38
th
write data on the PUT
7. The 40
th
write comes from the 39
th
read on the PUT, but writes to the 40
th
file location on the PUT.
8. The 40
th
read comes from reading the file on the PUT to generate the MD5 signature for comparison.
3.2.2.8. ATAPI Data Pattern set
For a ATAPI PUT a single data pattern set is defined as follows:
1. 8 KB file – read and signature verified 40 times
2. 64 BK file – read and signature verified 40 times
3. 256 KB file – read and signature verified 40 times
4. 1 MB file – read and signature verified 40 times
5. 16 MB file – read and signature verified 40 times
3.2.2.9. Test duration
The System Interoperability test shall repeat the data pattern set until a minimum of 9 minutes of execution time has
been reached for each of the required configurations with error checking continuously enabled.
3.2.2.10. Stop on Error
The System Interoperability test may stop on first error or count/indicate error and continue to complete the test
duration.
3.2.3. System Interop Pass / Fail Criteria
• The test tool shall count and report each data error (retried or not)
• One or more data errors fails that that configuration and no time or transfer size shall be reported
• A product under test must pass a minimum of 4 of the 5 configurations
Table 15 – System Interop Test Name matrix
Loops or errors
# MBi (1024 * 1024 bytes)
Time (sec)
Config 1
SYS-01a
SYS-01b
SYS-01c
Config 2
SYS-01a
SYS-01b
SYS-01c
Config 3
SYS-01a
SYS-01b
SYS-01c
Config 4
SYS-01a
SYS-01b
SYS-01c
Config 5
SYS-01a
SYS-01b
SYS-01c
3.3. System Interoperability Test Tool Validation requirements
A certified System Interoperability test tool (test tool) shall be validated on all applicable hosts (maximum of 3 different
hosts is required, more is allowed), using a minimum of 3 device products from each supported device type.
See section 3.2.2.4 for data pattern size definitions
3.3.1. SYT-01 – Data pattern validation
3.3.1.1. Device Expected Behavior
The test tool shall present the 8KB Long COMP data pattern on the SATA interface.
Measurement Requirements
• While reading a single 8KB Long COMP data pattern file:
- With a SATA bus analyzer validate Long COMP data pattern is correct and complete
- Generate a MD5 checksum while the data file is being read