Teledyne LeCroy Verification Script Engine (VSE) Manual - Manual (Page 32)

Teledyne LeCroy Verification Script Engine Reference Manual
Page 32 of 115
5.2.4 Transfer-specific Set of Members
in.XferType : Type of transfer. Repeats the trace event value for the transfer.
in.Addr : Device Address value for this USB transfer.
in.Endp : Device Endpoint Number value for this USB transfer.
in.Completed : Flag signaling if the transfer was completed.
in.Halted : Flag signaling if the transfer was halted (usually that means STALL handshake sent).
in.CtrlDirection : For a Control Transfer, represents the direction:
0 = Host-to-device
1 = Device-to-host
If the transfer is a Control Transfer, the following input context members provide values of the corresponding
fields of the USB Device Request:
in.ReqType
in.ReqRecipient
in.bRequest
in.wIndex
in.wValue
in.wLength
in.ClassicOnHigh : When set, indicates that this transfer was a classic speed transfer that was executed and
captured on a high speed branch (upstream from a high speed hub).
in.OTGHostId : For USB On-The-Go transfers, indicates if the A-device is acting as the host (value of 0) or the
B-device is acting as the host (value of 1).
in.PayloadLength : Length (in bytes) of the transfer payload. If zero, transfer does not have any payload.
Care should be taken not to request payload for the transfers that moved large amounts of data.
in.Payload : Bit source of the transfer payload. Note: You can extract any necessary information using the
GetNBits(), NextNBits(), or PeekNBits() function. (Refer to section 14 in the USBScriptDecodeManual.pdf.)
Note: Refer to the section
Script decoded fields retrieving functions for information about getting the script
decoded values at the Transfer level.