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

USB Protocol Suite User Manual 329
Voyager M3x USB 2.0 Script Limitations Teledyne LeCroy Corporation
4. Click OK to close the Recording Options dialog and apply the changes. The
generation settings take effect as soon as you execute a script.
11.10.3 Run the Traffic Generation Script File
1. Connect the system's port B (either Hi Speed or Classic Speed) to the Host.
2. Open the Traffic Generation .utg file.
3. Begin traffic generation by clicking .
When execution begins, the system reads the entire generation file and then parses the
generation commands into groups according to their endpoints. Each of the parsed
groups of commands are then written into dedicated memory segments in the generator.
Up to eight memory segments can be created for the various endpoints. In the case of
Endpoint 0 or any Control endpoints, a single memory segment is created.
Each memory segment can be thought of as a queue of the commands and responses for
a particular endpoint that occur in the generation file.
Commands are stored sequentially within each memory segment as they occur in the
generation file. For example, if a generation file has a sequence of command X and Y for
the Endpoint 1, the commands are extracted in this order and placed in the Endpoint 1
memory segment.
When the host calls for a particular device endpoint response, the first command listed in
that endpoint memory segment is then executed. With each subsequent call to the same
endpoint, commands are executed sequentially down the list as they occur in the
memory segments. For example, if three calls were made to Endpoint 0 IN, then the first
three commands in that endpoint's memory segment would then execute.
Note:
Each of the endpoint memory segments execute independently: there are no behavioral
interactions between the individual endpoints.
11.11 Voyager M3x USB 2.0 Script Limitations
Due to architectural changes in the Voyager M3x design, some features previously
available on USBTracer and Voyager M3/M3i have been limited.
USB 2.0 scripts are now more limited in size. Host scripts are limited to 64KBytes
(approximately 16K lines).
Device Emulation Scripts are limited to 4KBytes per endpoint (approximately 1K lines per
endpoint), with the exception that Endpoint 0 (the control endpoint) can handle more: it
is limited to 64KBytes (approximately 16K lines).
In addition, on the Voyager M3x, the ability to create arbitrary bit streams (using
raw_data, raw_data_bits, and bit_stuff key codes) is not supported for Hi Speed traffic.
Finally, slow speed (divide by 40, divide by 80, etc.) generation for Hi Speed traffic is also
not supported.