5 verification script engine input context members, 1 trace event-independent set of members, Verification script engine input context members – Teledyne LeCroy Verification Script Engine (VSE) Manual User Manual
Page 17: Race, Vent, Independent, Et of, Embers, 5verification script engine input context members
Teledyne LeCroy
Verification Script Engine Reference Manual
Page 17 of 115
5
Verification Script Engine Input Context Members
All verification scripts have input contexts, special structures that can be used inside of the scripts. The
application fills their members. The verification script input contexts have two sets of members:
Trace event-independent set of members
Trace event-dependent set of members
Note: All input context members have integer type values unless their types are explicitly specified.
If possible values for input context members are not explicitly specified, they should comply with the current USB
specifications.
5.1 Trace Event-independent Set of Members
This set of members is defined and can be used for any event passed to a script:
in.Level
: Transaction level of the trace event. It can be one of the following constants:
_PKT: Packet level (value = 0)
_TRA: Transaction level (value = 1)
_SPL_TRA: Split Transaction level (value = 2)
_XFER: Transfer level (value = 3)
in.Index
: Index of the event in the trace file (packet number for packets etc).
in.Time
: Time of the event (type = list, having format = 2 sec 125 ns -> [2 , 125]. For more information, see
In.Channel
: Indicates on which channel the event occured. It can be one of the following constants:
_USB2: USB2 traffic (value = 1)
_USB3_RX: USB3 Host Receive traffic (Upstream, value = 2)
_USB3_TX: USB3 Host Transmit traffic (Downstream, value = 3)
in.Speed
: Indicates the speed for the trace event. It can be one of the following constants:
_FS: USB2 Full Speed (value = 1)
_LS: USB2 Low Speed (value = 2)
_HS: USB2 High Speed (value = 3)
_SS: USB3 Super Speed (value = 4)
in.Direction
: Indicates the direction for the trace event. It can be one of the following constants:
_IN: Direction is from Host to Device (value = 2)
_OUT: Direction is from Device to Host (value = 3)
_BOTH: Trace event involves traffic in both directions (value = 4)
in.TraceEvent
: Type of trace events. (Application predefined constants are used. See list of possible events
in
Chapter 7. Verification Script Engine Events
in.Notification
: Type of notifications. (Application predefined constants are used. Currently no notifications
are defined.)