Scenario Events - Teledyne Sierra M6-2 User Manual

Scenario Events

where the HOLD causes the other device to send HOLDA. (The bus engine FIFOs must be
deep enough to hold all the traffic that the other device sends while the HOLD
propagates. The port drops all incoming HOLDA conditions, so HOLDAs are never put in
the FIFOs or made visible to the sequencers.)
After this, the port that had been receiving the HOLD stops sending HOLDA and attempts
to read data from the FIFO. The termination of HOLD propagates through the bus engine
and then causes the other device to restart transmission, which puts data into the FIFO.
Note:
If both sides send HOLD primitives that overlap, the receivers drop the HOLD conditions to avoid
overflowing the FIFOs.
If you turn off the Smart Hold option, the port does not send HOLDA when it detects a
HOLD primitive during a SATA frame.
4.7 Scenario Events
A scenario is a script you create using simple mouse clicks and text entries. As you work,
the script takes shape in the scenario area of the application display. You can think of the
scenario area itself as consisting of two subareas: A Global Rules area at the top, where
you create the Global Rules, and a Sequence area beneath the Global Rules, where you
create any sequences. Whether you are creating Global Rules or a Sequence, the menu‐
driven interface prompts you to specify the event(s) for which you want to trigger actions
(see
Sierra M6‐2 SAS/SATA Protocol Analyzer User Manual
Figure 4.17 on page 386).
Teledyne LeCroy
385