5 notes on lfps signals – Teledyne LeCroy USBTracer_Trainer - Users Manual User Manual
Page 25

USB Protocol Suite User Manual
Chapter 1: Overview
LeCroy Corporation
11
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.5 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.