Teledyne Sierra M6-2, User Manual, Page: 382 / 538

Teledyne LeCroy Scenario Libraries
380 Sierra M6 ‐ 2 SAS/SATA Protocol Analyzer User Manual
After you enter the event or combined event, the interface prompts you for actions. An
action might be, for example, injecting a particular primitive or error into the traffic
stream. You can enter multiple actions, which take place simultaneously.
After defining the event and actions within the Global Rule area, you can save the
scenario and download it to a InFusion device.
Sequences
The Global Rules are all you need for simple test scenarios. However, a scenario also can
contain one or two sequences, which can define multiple states and allow branching
between states. With a sequence, you also can do looping, which allows you to repeat a
test state or to execute a test for a specified period of time.
As with Global Rules, the menu ‐ driven interface guides you in building a sequence. Some
of the prompts are different, however, because you now are encapsulating groups of
events and actions as distinct states. Recall that a state is a combination of events and
actions at a specific point in time. If the event or combined event defined by a state
occurs, the corresponding action or set of actions follows.
Figure 4.11: Global Rules and Sequence Areas of a Scenario
InFusion hardware provides the capacity to have up to two sequences co ‐ existing in a
scenario in addition to the Global Rules. Recall that both the Global Rules and any
sequences are active at all times. Each is a separate “state machine,” having the behavior
of a particular test state at any point in time. Because the Global Rules has the capacity
for only one state, you can view it as a “degenerative state machine.”
4.5 Scenario Libraries
You can create any number of scenarios, which you then can archive on your host
machine’s hard drive. You also can download up to ten scenarios to each InFusion device
for test execution. You can think of the libraries as windows that hold scenarios.
Recall that each library is a separate *.infdb file.