Teledyne LeCroy Voyager Exerciser Generation Script Language Manual - Manual (Page 63)

Teledyne LeCroy Voyager USB 3.0 Exerciser Generation Script Language Reference Manual
54
9.1.1 SendPipeCommand Instruction
This instruction sets up all transactions or transfers to be executed by the Transaction Engine.
Format
SendPipeCommand ( command, pipe type, total length, setup,
data pattern, asn, store data, send ERDY, transaction engine index )
{
PipeCommandData
{
Field = Value
...
}
}
SendPipeCommand has the following instruction parameters:

command: Defines the specific Pipe Command. Possible values are described in the
Pipe Command table below..

pipe type: Specifies the Pipe Type for the endpoint on which the command is being set up.
Possible values are described in the Pipe Type table below..

total length: Specifies the total length of data transfer associated with this Pipe Command.

setup: Equals 1 if the specified transaction is a Setup transaction. Equals 0 (zero) for all
other cases.

data pattern: Specifies which data pattern to use for seeding the payload, if one should be
included with this transaction/transfer. Possible values are described in the Data Pattern table
below.

asn: Automatic Sequence Number. Equals 1 for Transaction Engine to automatically handle
Sequence Numbers for the TPs and DPs that it generates for the specified endpoint.
Equals 0 (zero) to override Transaction Engine behavior, for example to create
Sequence Number errors. If asn = 0, specify the starting Sequence Number in the
PipeCommandData structure.

store data: Specifies whether the packets sent by the DUT during execution of this
Pipe Command are stored for processing by Firmware. Currently, there is no facility in the
Firmware to utilize stored packets, so the default value is 0 (zero), for no storage.

send ERDY: Only applicable to the Device Emulation mode. If set, the Trainer will start the
transfer for this Pipe Command by sending the ERDY TP to the host.

transaction engine index: Optional index of the Transaction Engine to execute this
command on. Current Exerciser supports two instances of the Transaction Engine, so the
value can be 0 or 1. Starting transfers on different Transaction Engines can be used to
achieve concurrent execution of the transfers in the same direction.