Teledyne LeCroy Sierra M6-2 SAS_SATA Protocol Analyzer User Manual - Manual (Page 109)

Sierra M6‐2 SAS/SATA Protocol Analyzer User Manual 107
Projects Teledyne LeCroy
Figure 2.73: Protocol Errors Dialog
Check the Protocol Errors that you want the Analyzer to ignore.
When “RD Error” and “Code violation Error” are set as trigger events: 
“RD Error” or “Code violation Error” can occur right after the OOB sequence.
“RD Error” or “Code violation Error” can occur right after the recovery from the PM state.
These errors are mainly caused by the long synchronization time of the analyzer. If these
errors, caused by the Analyzer, become triggers, you cannot detect some other errors
that you really need to detect. To NOT detect the above two errors, enable the software
setting Disable ‘Disparity Error’ and ‘Symbol Violation’ during Speed negotiation. After
this, the code violation is not triggered during the speed negotiation phase, but is
triggered if the violation happens after the speed negotiation phase.
External Trig Out Setting
The Analyzer can send a Low or High external signal when a trigger occurs. Under Setup
select External Trig Setting to choose External Trig Out Setting: High Active, Low Active, or
Toggle from High to Low or Low to High once (3.3 V output). Enter the External TrigOut
pulse width.
The pulse width is programmable in the software. The Voltage level is 0 to +3.3 Volt. The
trigger out is derived by NL17SZ126 buffer. The delay for OOB traffic external trigger out is
330 ns. The delays for non OOB external trigger out are:
 6G ~ 370 ns
 3G ~ 540 ns
 1.5G ~ 850 ns
The delays for external trigger out with OOB traffic is 330 ns.