Offset(...), Descriptor definitions, Decoding definition strings – Teledyne LeCroy USB Chief - File Based Decode Manual User Manual
Page 33
29
C
OMPUTER
A
CCESS
T
ECHNOLOGY
C
ORPORATION
USB D
ESCRIPTOR
D
EFINITION
(.
DSC
) F
ILES
Reference Manual
AllOffsets=
{
2=Example1
4=Example2
}
Note: it's not necessary for the numeric
Offset
values to start from zero or to
increase sequentially. In addition, the numeric values may be in decimal or hexa-
decimal.
Offset(...)
Offset(...)
defines an offset listed in the
AllOffsets
entry. Offset defini-
tions follow the format
Offset(<Offset_value>)=
{
...
}
The value of <
Offset_value
> should match the numeric value assigned to the
offset in the
AllOffsets
entry. For example:
Offset(2)=
{
...
}
Offset(4)=
{
...
}
Descriptor definitions
Just as the bulk of a request definition file is made up of
Request(...)
entries,
the main portion of a descriptor definition file is composed of
Offset(...)
entries, which contain the actual descriptor definitions. They are structured very
similarly to
Request(...)
entries; therefore, only their differences will be
detailed here.
Decoding Definition Strings
Unlike request definitions, descriptor definitions do not use the keywords
wValue
,
wIndex
and
Data
, since all of the descriptor information is data. Instead, the def-
initions are in the form of the contents of a
Data
entry.