Keysight Technologies U4301, User Manual

Page: 58 / 204

6 Setting Up Triggers
58 Keysight U4301 PCIe Gen3 Analyzer User’s Guide
acquiring data until the memory depth is full. If you do not select any option from the list,
then the filtering is considered Off and all the acquired data is stored in memory when the
trigger condition is met.
d Drag events you would like to trigger on from the left-side pane to the Trigger on any of these
events box.
The left-side pane contains an event hierarchy that can be expanded or collapsed.
To edit events in the trigger box, click the underlined event name.
To remove events from the trigger box, click the "X" to the left of the event name.
e Drag events you'd like to exclude from the trigger to the While ignoring any of these events box.
f Click Apply or OK .
See Also
• “To select which links the trigger is for" on page 64
• “To set the trigger position" on page 64
• “To save/recall favorite triggers" on page 64
• “To clear the current trigger" on page 65
NOTE
Triggering on L1 Substates
In the Trigger dialog box, you can use the CLKREQ# event under the Physical Layer Triggers
group to set up a trigger on assertion, deassertion, or changes in the CLKREQ# signal.
To trigger on CLKREQ#, the
Store CLKREQ# Transitions field must be set to Enabled .
When CLKREQ# is used as the trigger event, the U4301 module triggers on encountering the
CLKREQ# asserted/deasserted packet (as the case maybe as per the trigger condition). The
timestamp of this trigger is recorded and displayed as the time of the first PCIe packet seen
after sampling the CLKREQ# assertion. The following figure illustrates an example of
triggering on the deassertion of the CLKREQ# signal.