Readylink™ emulation, 6 notes on lfps signals – Teledyne LeCroy USB Protocol Suite User Manual (Voyager_Advisor T3_Mercury) User Manual
Page 25

USB Protocol Suite User Manual
25
Voyager M3/M3i Analyzer
Teledyne LeCroy Corporation
ReadyLink™ Emulation
The Teledyne LeCroy Voyager USB 3.0 Exerciser features ReadyLink Emulation Mode. The
ReadyLink feature handles all USB 3.0 link training and link flow control, allowing the
emulator to operate at full line rate and respond to the DUT as defined by the
specification. The ReadyLink Emulation Mode helps simplify development of USB 3.0 test
scenarios.
By default, ReadyLink Emulation Mode automatically manages:
Header Packet Acknowledgements (L_GOOD_n)
Buffer Credit (L_CRD_x)
SKIPs at required intervals (SKP)
Link Synchronization
Responds to LFPS (Polling.LFPS)
Responds to polling sequence (Polling.RxEQ)
Responds to TS1 / TS2 handshaking sequence
Responds to SS.Inactive (with RX.Detect)
Power Management Link Commands
Responds to LGO_Un (with LAU)
Responds to LAU (with LMPA)
Test scripts can customize ReadyLink Emulation Mode to include error scenarios, such as:
Header LBADs
Invalid link commands
8B10B / CRC Error
Running Disparity Error
Corrupt Link Commands
Corrupt Flow Control (Wrong L_CRD_x, Wrong L_GOOD_n, Drop L_Good_n)
Corrupt Header Packet acknowledgement (Send LBAD, LRTY)
Corrupt Packet Framing (SHP, SDP, END)
At the packet level, you can send customized data payloads anywhere within the stream
to insert logic errors, perform corner‐case, or do stress testing. Commands, such as the
Set ErrWrongLCRD command, allow link‐layer error injection anywhere within the script.
1.2.6
Notes on LFPS Signals
Voyager Exerciser requires received “Ping” LFPS signals to be a minimum of
150 nanoseconds to be reliably recognized.
Voyager Analyzer can recognize “Ping” LFPS signals above 60 nanoseconds and report
their durations to ±15 nanoseconds of accuracy.