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
199
Chapter 4: Concepts
Understanding Logic Analyzer Triggering
“not in range” function as well. Ranges are a convenient shortcut so
that you don't have to specify “ADDR >= 1000 and ADDR <= 2000”.
Next: “Flags” on page 199
Flags
Flags are Boolean variables that are used to send signals from one
module to another. They can be set when a condition occurs in one
module and tested later by another module. In the example below, flag
1 is used to keep track of what happens in the trigger sequence of
Module 1 so that this information can be used in Module 2.
Trigger Sequence for Module 1
1. If ADDR < 5000 then
Set Flag 1
Trigger and fill memory
Trigger Sequence for Module 2
1. If DATA = 5000 and Flag 1 is set then Trigger
Else if DATA = 1000 and not Flag 1 then Trigger
Next: “Occurrence Counters and Global Counters” on page 199
Occurrence Counters and Global Counters
Occurrence Counters are used in situations where you want to find the
Nth occurrence of an event. For example, if you want to trigger on the
5th time that ADDR = 1000, you could set up the trigger as:
If ADDR = 1000 occurs 5 times then Trigger
Global Counters are like integer variables. They are more flexible than
Occurrence Counters because they can be used to count complex
events such as an edge followed by another edge. Global Counters can
be incremented, tested, and reset. By default, Global Counters begin
with zero and don't need to be reset unless they have already been
used in the trigger sequence. In general, Occurrence Counters should