1 trace event-independent set of members, Chapter 5, Verification script engine input context members – Teledyne LeCroy SAS_SATA Protocol Suite Verification Script Engine Reference Manual User Manual
Page 16: Race, Vent, Independent, Et of, Embers, Input context variables

16
Chapter 5: Verification Script Engine Input Context
Members
All verification scripts have input contexts –special structures whose members are filled by the
application and can be used inside of the scripts. (For more details about input contexts, refer
to the CATC Script Language(CSL) Manual.. The verification script input contexts have two
sets of members:
o
Trace event-independent set of members
o
Trace event-dependent set of members
5.1 Trace Event-independent Set of Members
This set of members is defined and can be used for any event passed to script:
in.Level
Logical level of the trace event: 0 = Link, 1 = Transport, 2 =
Application.
in.Index
Index of the event in the trace file: frame number for frames,
sequence number for sequences.
in.Time
Time of the event: type = list, having format
2 sec 125 ns -> [2 , 125]
. (See
in.Duration
Duration: time that packet contains.
in.Channel
Channel where the event occured: may be _CHANNEL_1 (1) or
_CHANNEL_2 (2), indicating which direction of the SAS/SATA link
the event occurred)
in.TraceEvent
Type of trace event: application predefined constants are used.
See the list of
in.Notification
Type of notification: application predefined constants are used.
Currently, no notifications are defined.
in.LinkSpeed
Speed of the trace event: may be _LINK_SPEED_1_5 (1.5 Gbps) or
_LINK_SPEED_3_0 (3Gbps) or _LINK_SPEED_6_0 (6Gbps)
*Gbps – Giga Bits per second
in.ProtocolErrorMask
A bitmask pattern contains detected errors on the specified event:
Each bit on this mask demonstrates a possible error. To know about
error bit position look at See
In.DWORDS
All DWORDs of current packet: type = list of list, having format
DWORD: SOF, count : 1, Error: no error -> [“SOF”, 1, 0]
DWORD: 50E80050, count : 1, Error: Has an error -> [“50E80050”, 1,
1]
…
…..
[[“SOF”, 1, 0], [“50E80050”, 1, 1], …]
Note: For SATA/STP frame, if trace has been captured with M6-4, M6-2 or M6-1, “Host” and
“Device” are coming sequentially one after other: [ [Host], [Device], [Host], [Device], ….]