Teledyne LeCroy Sierra M124 User Manual User Manual
Page 234
Teledyne LeCroy
InFusion Scenarios
232
Sierra M124 SAS/SATA Protocol Analyzer User Manual
In Global Rules, if a Counter is used for Event counting, 2 extra actions are consumed. 2
more actions are required for "Every Nth occurrence" option.
In Sequences, If a Counter is used for Event counting, 3 extra actions are consumed. 3
more actions are required for "Every Nth occurrence" option.
Regarding limits on any of the above mentioned connections, i.e., x timers + y monitors
are allowed per state where x+y=n:
There are a lot of big/small rules checked by the scenario compiler, but as a rule of
thumb:
8 actions per state are available
12 counters globally are available, each assigned permanently to a certain job
6 available timers per scenario
12 programmable multi‐purpose resources for DWORD comparison/substitution/capture
are available. If a pattern detector uses 3 of these resources to trigger on a specific frame
on the bus, only 9 more resources are available for other tasks. Frame/FIS type detectors
are excluded from this rule, because they use their own dedicated resources.
8 primitive detectors are available
If you want to trigger on a pattern (Frame/FIS) and change/capture a dword(s) before the
last offset of a detected pattern (e.g., changing the Frame Type of a SAS Frame with Data
Offset == 11223344), you are limited to a maximum of 9 dword offset (i.e., if you trigger
on the 20th payload of a Data FIS, you can change/capture the 12th dword onwards. 11th
payload dword and preceding dwords are not accessible for change/capture)
You can not change a state based on back‐to‐back events. At 6G speed, there should be at
least one dword between the triggering event of two consecutive states. At other speeds,
back‐to‐back dword state transitions might rarely be missed, so best practice is to never
assume back‐to‐back dword events.
As described later in this chapter, you can create any number of scenarios and store them
in libraries on the PC hard drive. Scenario library files names are in the following format:
<filename>.infdb
Creating InFusion scenarios is easy, but it requires an understanding of the following
terms defined in
.