Teledyne LeCroy SAS Verification Test Descriptions - Manual (Page 171)

University of New Hampshire
InterOperability Laboratory
Test 6.7.1.16: Receive Bad Parity
Purpose
To verify that the DUT properly handles reception of an improperly set parity bit during
SNW-3.
References
●
6.7.4.2.3.3 SAS Standard
Resource Requirements
●
A Protocol Generator/Analyzer capable of transmitting and receiving SAS OOB signals
and SAS 2.0 Speed Negotiation.
Modification Record
●
06-25-2007: Initial Draft (Michael Davidson).
●
06-29-2007: Fixed references, changed title numbering (Michael Davidson).
●
07-20-2007: Expanded procedure (Michael Davidson).
●
08-01-2007: Removed irrelevant information from the discussion. Corrected
title/discussion for new capabilities naming conventions.
Discussion
The PARITY bit provides for error detection of all the SNW-3 phy capabilities bits. The
PARITY bit shall be set to one or zero such that the total number of SNW-3 phy capabilities bits
that are set to one is even including the START bit and the PARITY bit. If the Parity bit received
is incorrect based upon the received bits, then the parity is bad and the phy shall consider a phy
reset problem.
Test Setup
●
The DUT and the Testing Station are physically connected the the DUT is powered off.
Procedure
1. Power on the DUT.
2. The testing station is instructed to transmit COMINIT/COMRESET to the DUT.
3. The DUT is expected to respond with COMINIT/COMRESET.
4. The testing station is instructed to transmit COMSAS to the DUT.
5. The DUT is expected to respond with COMSAS.
6. Upon reception of COMSAS from the DUT, the Testing station is instructed to transmit
D.C. Idle for one RCDT. The DUT is expected to do the same.
7. Following RCDT, the testing station is instructed to transmit ALIGN(0) primitives at 1.5
Gbps for one SNTT. If the DUT supports 1.5 Gbps signaling, it is expected to do the
same. If the DUT does not support 1.5 Gbps signaling, it should continue to transmit
D.C. Idle.
8. The Testing station is then instructed to transmit D.C. Idle for one RCDT. If the DUT
supports 3.0 Gbps. The DUT is expected to do the same.
9. Following RCDT, the testing station is instructed to transmit ALIGN(1) primitives at 3.0
Gbps for one SNTT. If the DUT supports 3.0 Gbps signaling, it is expected to the same.
10. The Testing Station is then instructed to transmit D.C. Idle for one RCDT. The DUT is
expected to do the same.
11. The Testing Station is the instructed to transmit its Phy Capabilities bits indicating
support for all speeds and SSC settings. The Testing Station is instructed to transmit an
UNH-IOL SAS 2.0 Speed Negotiation
35 of 49