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

University of New Hampshire
InterOperability Laboratory
Test 6.7.1.17: No Common Speeds
Purpose
To verify that the DUT behaves properly when it does not share any common speeds with
the link partner.
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: Updated for new standard release (Michael Davidson).
Discussion
If a phy participates in a valid SNW-3 and parity is good, then the phy shall participate in
a Train-SNW utilizing the highest commonly settings based on the outgoing and incoming SNW-
3 settings bits.
They phy shall consider SNW-3 to be valid if it supports SNW-3 and receive at least one
phy capabilities bit set to one. If the phy does not support SNW-3 or does not receive at least one
phy capabilities bit set one tone, it shall consider SNW-3 to be invalid.
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 no
support for any speeds or SSC settings. The DUT is expected to transmit it's Phy
UNH-IOL SAS 2.0 Speed Negotiation
37 of 49