User's Manual
Table Of Contents
- Agilent Technologies 16750A/B Logic Analyzer
- Agilent Technologies 16750A/B Logic Analyzer
- Contents
- Getting Started
- Step 1. Connect the logic analyzer to the device under test
- Step 2. Choose the sampling mode
- Step 3. Format labels for the probed signals
- Step 4. Define the trigger condition
- Step 5. Run the measurement
- Step 6. Display the captured data
- For More Information...
- Example: Timing measurement on counter board
- Example: State measurement on counter board
- Task Guide
- Probing the Device Under Test
- Choosing the Sampling Mode
- To select transitional timing or store qualified
- Formatting Labels for Logic Analyzer Probes
- Setting Up Triggers and Running Measurements
- Displaying Captured Data
- Using Symbols
- Printing/Exporting Captured Data
- Cross-Triggering
- Solving Logic Analysis Problems
- Saving and Loading Logic Analyzer Configurations
- Reference
- The Sampling Tab
- The Format Tab
- Importing Netlist and ASCII Files
- The Trigger Tab
- The Symbols Tab
- Error Messages
- Must assign Pod 1 on the master card to specify actions for flags
- Branch expression is too complex
- Cannot specify range on label with clock bits that span pod pairs
- Counter value checked as an event, but no increment action specified
- Goto action specifies an undefined level
- Maximum of 32 Channels Per Label
- Hardware Initialization Failed
- Must assign another pod pair to specify actions for flags
- No more Edge/Glitch resources available for this pod pair
- No more Pattern resources available for this pod pair
- No Trigger action found in the trace specification
- Slow or Missing Clock
- Timer value checked as an event, but no start action specified
- Trigger function initialization failure
- Trigger inhibited during timing prestore
- Trigger Specification is too complex
- Waiting for Trigger
- Analyzer armed from another module contains no "Arm in from IMB" event
- Specifications and Characteristics
- Concepts
- Understanding Logic Analyzer Triggering
- Understanding State Mode Sampling Positions
- Getting Started
- Glossary
- Index

64
Chapter 2: Task Guide
Setting Up Triggers and Running Measurements
Setting Up Triggers and Running Measurements
The following information is a generic discussion about triggering in
logic analyzers. Depending on the logic analyzer type, and the state or
timing mode being used, some functionality may not be available.
• “Using Trigger Functions” on page 65
• “Using State Mode Trigger Features” on page 70
• “Editing the Trigger Sequence” on page 72
• “Editing Advanced Trigger Functions” on page 78
• “Saving/Recalling Trigger Setups” on page 85
• “Running Measurements” on page 86
In General...
Use trigger functions for basic measurements.
For more complicated measurements, where no trigger function exists,
start with a trigger function that's similar to the measurement you want
to make. Then, break down the trigger function and edit the advanced
trigger sequence levels.
Timing Analyzer
Triggers
Everything that looks like a button in the trigger definition gives you a
way to modify the trigger setup.
For example, to look for a edge instead of a pattern, select the button
that equates a label with a pattern and choose an edge comparison
instead.
State Analyzer
Triggers
For every state analysis sample, a logic analyzer needs to know two
things:
1. Should some action (like a trigger) be taken as a result of this sample?
2. What should be done with this sample? That is, should it be stored in logic
analyzer memory or should it be discarded? (This question doesn't need to
be asked when using a timing analyzer because all samples are stored.)
State analysis trigger definitions are made simpler with a default
storage qualifier. This makes it possible to ignore, at all trigger