Teledyne LeCroy USBTracer_Trainer - Users Manual - Manual (Page 309)

USB Protocol Suite User Manual Chapter 11: Traffic Generation (2.0)
LeCroy Corporation
295
Table 1: Support Keys for Defining Fields within a Packet
Key Code Format Description
File Control Keys
file_type
UPAS
CHIEF This must be included at the beginning of the file to
determine the speed of packets to be generated.
Value must be file_type=UPAS to allow for High
speed traffic, IntelliFrame operation, expected_pid
and device_pid key support.
Full and Low speed traffic, and Bitstream operation
are supported on all file_type= values.
If this statement does not appear in the file, the
default is file_type=CHIEF, allowing backward
compatibility with older USB Chief™ .usb files.
file_version integer This must be included after the file_type= key to
determine the version of this file. Value is currently 3.
Usage: file_version=3
file_mode HOST
DEVICE Sets generation mode to host or device.
For generation to work, this must match the selection
found in the Recording Options > Misc dialog.
file_speed HIGH
HI
FULL
LOW This must be included after the file_version= key to
determine the speed of packets to be generated.
Values are HIGH, HI, FULL, or LOW.
Example: file_speed=FULL.
Only one file_speed= is allowed per .utg file, but low
speed traffic on a full speed bus can be created by
adding the speed=LOW key to a low speed packet in
a file defined as file_speed=FULL. No other mixing
of speeds is allowed.
HI is the same as HIGH and was added to conform to
the USB terms.
loop_count
wrap_count 0 through 16382
or "infinite" These two terms are interchangeable.
Host Emulation Only.
This key defines the loop count for each memory
segment.
Examples: loop_count=INFINITE or wrap_count=9
wrap
loop HERE This key marks the wrap point in the traffic.
When generation is in Repeat mode, all the traffic
before the wrap point is going to be sent once. All the
traffic after the wrap point is going to be repeated in a
loop.
The usage of the keyword is wrap=HERE or
loop=HERE.
For Device Emulation, the value would be a memory
segment number, so that the looping is associated
with only that one endpoint, such as wrap=4.