LeCroy USB Protocol Suite Advisor T3, Руководство пользователя

Страница: 311 / 388

USB Protocol Suite User Manual Chapter 11: Traffic Generation (2.0)
LeCroy Corporation
297
Endpoint Configuration
begin_config
HERE Defines the beginning of the region in the file used to
configure the endpoint types.
The configuration is necessary to determine the
default behavior of the NAK retry mechanism during
IntelliFrame operation.
Between the
begin_config=HERE and the
end_config=HERE statements is a series of
config_endpoint=xxx statements, which define each
endpoint's type and default retry behavior.
The config region must precede any actual packet or
bus condition statements.
For Device Emulation, the config region is mandatory.
It provides the mapping of the endpoints into their
corresponding segments of Analyzer memory, which
contain the traffic for those endpoints.
When exporting to a
.utg file from a trace file, these
sections are created automatically.
Syntax example:
begin_config=HERE
end_config
HERE Terminates the region in the file used for configuring
the endpoints.
See
begin_config .
Syntax example: end_config=HERE
config_endpoint
CONTROL
INTERRUPT
ISOCHRONOUS
BULK Begins a statement that defines a particular
endpoint's type, default retry behavior
(Host Generation only), and memory segment
(Device Emulation only).
Usage example:
config_endpoint=BULK addr=1
endp=3 direction=OUT retry=TRUE
retry_next_frame=FALSE
endp_mem_seg
1
2
3
4
5
6
7
8 Device Emulation Only.
Separates each endpoint function into a different
queue (also referred to as a Memory Segment) of
commands and responses.
There are a maximum of eight of these queues, and
each has a unique address/direction combination.
For control endpoints, one queue is shared by both
directions of the endpoint.
Traffic on the Default Endpoint (Address 0, Endpoint
0) shares the same queue as the endpoint 0 of the
selected device address (the address it gets from the
Host through the SetAddress request).
These always use
endp_mem_seg=1 .
These are all set automatically when exporting a trace
file to a Device Emulation
.utg file.
Key Code Format Description