The Voyager USB 3.2 Exerciser allows you to create USB3 traffic generation scenarios for Voyager USB 3.2 Exerciser devices.
This document describes the commands of the Voyager USB 3.2 Exerciser.
You can start the Voyager USB 3.2 Exerciser script editor by clicking that button in the USB Protocol Suite application to display an editor user interface, in which you can create and edit generation script files, as well as reuse codes.
Voyager ReadyLink™ Emulation
The Teledyne LeCroy Voyager USB 3.2 Exerciser features ReadyLink Emulation Mode. The ReadyLink feature handles all USB 3.2 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.2 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 Set ErrWrongLCRD, allow link-layer error injection anywhere within the script.