beautypg.com

Usb request definition (.req) files, Structure, Able – Teledyne LeCroy USB File Based Decode Manual User Manual

Page 5: Ontents, Usb r, Req) f, Equest, Efinition, Iles

background image

1

C

OMPUTER

A

CCESS

T

ECHNOLOGY

C

ORPORATION

USB R

EQUEST

D

EFINITION

(.

REQ

) F

ILES

Reference Manual

USB R

EQUEST

D

EFINITION

(.req)

F

ILES

Request definition (.req) files are used to configure decoding of class- or vendor-
specific data of any protocol defined for USB. A .req file is a set of instructions that
contains definitions that describe, in USB-specific terms, how to take blocks of data
and break them into fields with consecutive decoding of each field. The data being
decoded can be data in a USB Device Request, or any formatted data that is sent on
an Interrupt or Bulk endpoint of a USB device.

The request definition files are text-based files that are identifiable by their .req ex-
tension. Customized decoding of USB requests is possible by editing files or
creating new definition files. This document describes the components of a .req file
and the format for writing or editing a .req file.

Please refer to the Universal Serial Bus Specification, version 1.1 for details about
USB protocol. The USB specification is available from the USB Implementers
Forum (USB-IF) at http://www.usb.org/.

Structure

A .req file has the following basic structure:

[Defines=
{

<Define_0>=<Define_Name_0>
<Define_1>=<Define_Name_1>
<Define_2>=<Define_Name_2>
...

}]

opt

GroupName=<name>
GroupType=<Standard, Class, or Vendor>

AllRequests=
{

<bRequest_0>=<bRequest_Name_0>
<bRequest_1>=<bRequest_Name_1>
<bRequest_2>=<bRequest_Name_2>
...

}