Teledyne LeCroy USB Protocol Suite User Manual (Voyager_Advisor T3_Mercury) - Manual (Page 337)

USB Protocol Suite User Manual 337
Format of Traffic Generation Files Teledyne LeCroy Corporation
retry_next_frame TRUE
FALSE Host Generation Only.
Determines when a retry will be attempted
after a failed match of an expected_pid.
This statement only applies if a retry=TRUE
statement also exists.
If TRUE, the Exerciser waits until the current
frame completes, issues a start of frame, and
then retries the transaction.
If FALSE, the Exerciser waits 1/10th of a frame
before retrying the transaction.
Before each retry attempt, the Exerciser checks
to see where in the frame interval it is. If it is too
close to the EOF, it automatically generates the
next start‐of‐frame before performing the retry.
If it is not too close to the EOF, it performs the
retry without generating a new frame.
This statement can also be used in conjunction
with any pid=xxx statement in the .utg file. This
can be done to override the configured or
default retry behavior.
Syntax example: retry_next_frame=FALSE
ping_on_retry TRUE
FALSE Host Generation Only.
Determines whether an OUT transaction is
retried by repeating the OUT‐DATAx sequence,
or whether a PING sequence should be
initiated.
If TRUE, the Exerciser automatically generates
PINGs (and retries) before going through a Retry
Loop. PINGs are repeated until an ACK is
received, and then the original OUT‐DATAx
transaction Sequence is attempted. During the
PING retries, the Exerciser automatically
generates frames. When the original Retry
Sequence receives its expected_pid, the
Exerciser generates a new frame before
continuing with the Gen File.
If FALSE, the original transaction is always
retried.
This statement can also be used in conjunction
with any pid=xxx statement in the .utg file. This
can be done to override the configured or
default retry behavior.
Syntax example: ping_on_retry=TRUE
Key Code Format Description