Teledyne LeCroy USB Chief - File Based Decode Manual - Manual (Page 11)

7
C OMPUTER A CCESS T ECHNOLOGY C ORPORATION USB R EQUEST D EFINITION (. REQ ) F ILES
Reference Manual
Decoding Definition strings: wValue , wIndex , and Data
A request definition may contain three optional decoding definition strings:
wValue , wIndex , and Data . wValue and wIndex define how the wValue and
wIndex fields of the request are decoded. Data specifies how Data fields are
decoded during the request's data stage. All three use the same definition format, as
follows:
<wValue, wIndex or Data>=
{
...
}
If one or more of the definition strings is omitted, then the Request Decoding
applies default decoding.
The contents of the decoding definitions can be built using one or more of these
three basic keywords:
WordValue , FormatValue , and Bitmap .
WordValue
Use the WordValue keyword when the field has a defined set of possible values,
and each value has a different meaning. The entries are formatted as an enumerated
list, as follows:
WordValue=
{
<wValue_0>=<Value_Meaning_0>
<wValue_1>=<Value_Meaning_1>
...
}
The possible values for wValue are represented numerically. The meanings are
generally represented as text strings. WordValue entries work similarly to if-then
statements: if wValue matches a wValue value in the WordValue list, then the
meaning will appear in the wValue trace field. If the value of wValue doesn't
match a value in the list, then, by default, its numeric value will be displayed in the
wValue trace field. However, this default can also be overridden with a different
type of decoding -- a
FormatValue entry (see “ FormatValue ” on page 8 for
details) or a Bitmap entry (see “ Bitmap ” on page 11 for more details).
The following example comes from the wValue entry of the hub.req
SetFeature request definition. The figure shows the output that results when
wValue is 0x0008 .
WordValue={
0x0001=PORT_ENABLE
0x0002=PORT_SUSPEND