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
203
Chapter 4: Concepts
Understanding Logic Analyzer Triggering
1. If DATA = 005E then Trigger
Else If ADDR in range 5000 to 6FFF then
Store Sample
Go to 1
Else If ADDR not in range 5000 to 6FFF then
Don't Store Sample
Go to 1
Alternatively, if the default storage is set to “Store Everything”, use the
following:
1. If DATA = 005E then Trigger
Else If ADDR not in range 5000 to 6FFF then
Don't Store Sample
Go to 1
In summary, Sequence Level Storage always overrides the Default
Storage, but only for the conditions specifically mentioned in the
Sequence Level Storage. You must be very careful that you account for
the interaction between Default Storage and Sequence Level Storage.
Next: “Strategies for Setting Up Triggers” on page 203
Strategies for Setting Up Triggers
• “Trigger Functions” on page 203
• “Setting Up Complex Triggers” on page 206
• “Document Your Trigger Sequences” on page 206
Trigger Functions
While setting up logic analyzer triggers can be difficult, trigger
functions can greatly simplify the process. Trigger functions are
commonly-needed building blocks that can be combined to set up a
trigger. Because the functions cover most common triggers, you can set
up your trigger simply by selecting the appropriate function and filling
in the data. The Agilent Technologies 16715A logic analyzer trigger
user interface is shown in the following figure. Note that trigger
functions are prominently located at the top of the screen.