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

196
Chapter 4: Concepts
Understanding Logic Analyzer Triggering
time. Two sequence levels can never be used to specify two events that
happen simultaneously.
For example, consider the following trigger sequence:
1. If ADDR = 1000 then Go to 2
2. If DATA = 2000 then Trigger
If the following samples were acquired, the logic analyzer would trigger
on sample #7.
Sample # ADDR DATA
1 1000 2000 <- This sample meets the condition in Sequence level #1
2 1010 3000
3 1020 4000
4 1030 5000
5 1040 6000
6 1050 7000
7 1060 2000 <- This is where the logic analyzer triggers
Note that the logic analyzer will not trigger on Sample #1 because a
new sample is acquired between the time that the condition in
Sequence level 1 is met and when the condition in Sequence Level #2 is
tested. A good way to think of this trigger sequence is “Find ADDR =
1000 followed by DATA = 2000 and then trigger”. Multiple sequence
levels in a trigger sequence imply a “followed by”.
Once a logic analyzer triggers, it does not trigger again. In other words,
even if more than one sample meets the trigger condition, the logic
analyzer still only triggers once. For example, using “ADDR=1000” as
our trigger, if the logic analyzer acquires the following samples, it will
trigger on Sample #2 and only on Sample #2.
Sample # ADDR
1 0000
2 1000 <- The logic analyzer triggers here
3 2000
4 1000 <- The logic analyzer does NOT trigger again here
5 1040
A frequently asked question is “What happens if the conditions in a
sequence level are not met?” For example, if there is a condition that
says “If ADDR = 1000 Then Trigger”, what happens if the current
sample has ADDR = 2000? The logic analyzer simply acquires the next
sample and tries to execute this sequence level again. In essence, if the
trigger condition is “ADDR = 1000”, this is equivalent to “Keep
acquiring more samples until you find one that has ADDR=1000”.
Therefore, if you set up a trigger condition that is never met, the logic