LeCroy Corporation
Primitive and Frame Definitions
392
Sierra M6
‐
2 SAS/SATA Protocol Analyzer User Manual
These commands should be configured either in the
Setting.inc
file or at the beginning of
the traffic generation file as a global statement.
Primitive and Frame Definitions
Five other
Include
files are provided that define the most of the known templates for
Primitives and Frames. The five are:
PrimitivesDecl.inc
AddressFramesDecl.inc
SSPFramesDecl.inc
SMPFramesDecl.inc
STPFramesDecl.inc
Each of the Frame templates defines header and field structure.
The default value for all Frame fields is zero.
Special Conditions for Frames
There are three conditions about Frames that need to be kept in mind when configuring
Frame generation:
1.
Frame
delimiters
need
to
agree
‐
At the present time, when defining a Frame, make
sure that the Frame Prologue and Frame Epilogue agree. Do not mix types. For
example, do not mix a SAS Start of Frame (SOF) with a SAS End of Address Frame
(EOAF).
A SAS SOF should be matched to a SAS EOF. A SAS SOAF should be matched to a SAS
EOAF. If generating SATA traffic, a SATA_SOF should be matched to a SATA_EOF.
At the present time, if you mix different types of prologues and epilogues for any
given Frame, the Frame is ignored.
2.
Data
Length
Fields
can
be
fixed
‐
length
or
variable
‐
By default, data frames are of a
fixed length. If you want to generate variable length frames, place an asterisk in the
Data definition field in the
SSPFramesDecl.inc
file:
Data
:
*
If you replace the asterisk with a value, then the field becomes fixed length.
3.
CRC
Calculations
are
calculated
unless
told
otherwise
‐
If the CRC is not explicitly
set in the traffic generation file, the application assumes that you want it and
calculates and displays it in front of the generated frames.
If you provide a CRC value, the application uses that value, even if it is incorrect. This
gives you the option of configuring the generator to create errors.