Teledyne LeCroy Sierra M6-1 SAS_SATA Protocol Analyzer User Manual - Manual (Page 238)

Teledyne LeCroy InFusion Scenarios
236 Sierra M6‐1 SAS/SATA Protocol Analyzer User Manual
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 host machine’s hard drive. Scenario library files names are in the
following format:
.infdb
Creating InFusion scenarios is easy, but it requires an understanding of the following
terms defined in Table 1.
TABLE 4.1: Key Scenario Terms
Term Definition
Action InFusion response to an event.
Event Condition that is detectable by InFusion.
Combined Event Logical OR association of events (for example, event A OR event
B).
Global Rules Portion of a scenario that can define a single InFusion test state.
You can think of the Global Rules and each sequence as a
separate test routine or program operating within the scenario.
Each operates independently and in parallel with the others. The
purpose of each is to detect events and then respond with the
appropriate action or set of actions. In essence, you can operate
up to three test states simultaneously within InFusion.
Sequence Portion of a scenario that can define multiple InFusion test states.
More flexible than the Global Rules, a sequence allows more
powerful scenarios that include branching and looping between
test states (Global Rules can define only a single test state, so
there is no branching).
State “Behavior” of the Global Rules or a sequence at any point in time.
In terms of InFusion testing, behavior is “waiting” for a set of
events and responding with a set of actions.