Specifications

SATA-IO Confidential 92
• With a bus analyzer demonstrate a complete (no missing or additional) data pattern set for each device type is
transferred on the SATA bus for each test tool request. Traces that filter the user data, but still indicate the FIS
structure are acceptable. Reads of non-data set (file system reads) are allowed, but should be minimized
Pass/Fail Criteria
• A complete data pattern set for each device type is transferred on the SATA bus for each test tool request.
• Any additional data files will indicate a fail (i.e. reading the data for the copy and reading the same data for
signature generation is a tool failure).
3.3.6. SYT-06 - Data file signatures
The test tool shall provide documentation (signature file or code snippet with MD5 signatures) showing only the
SATA-IO Logo MD5 data file signatures are used for data integrity validation.
Pass/Fail Criteria
• All MD5 signatures used must match the SATA-IO Logo MD5 signatures
3.3.7. SYT-07 - Data Pattern set
The test tool shall provide documentation showing the proper data pattern set is used for all supported device types.
Pass/Fail Criteria
• Provide log files or test code showing the proper data pattern set is used for each supported device type
3.3.8. SYT-08 - Test duration
The test tool shall demonstrate on one supported device type and provide documentation for all other supported
device types showing the tests executed for a minimum of 9 minutes for all supported device types.
Pass/Fail Criteria
• For each of the supported device types, provide time stamped log files (with embedded starting and end
times) showing a minimum of 9 minute execution time.
3.3.9. SYT-09 – System Configuration
The test tool must support all possible system configurations and only the test tool generated traffic shall be
sent/received to/from the PUT.
The OS can NOT access the PUT once the test has begun (i.e. the swap file can not be on the PUT).
Test tool code may be located on the PUT as long as it is completely loaded from the PUT before the test is started
and all accesses to the PUT are the previously defined System Interop Framed COMP pattern until the test is
complete.
All log files shall be written to a non-PUT media or stored in RAM until all tests are complete.
Pass/Fail Criteria
• Command level bus traces showing only Framed COMP pattern transfers for the complete test period.
3.3.10. SYT-10 – OS Install
All test tool validation shall be performed after the OS has been installed. If the OS is installed on the PUT, then the
validation shall be done on every PUT (i.e. the OS and driver combination used during test tool validation shall be the
same as that used during the PUT validation). If any OS or driver updates are made, the test tool is required to be re-
validated. No OS or driver updates are allowed between tool validation and PUT validation.