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
197
Chapter 4: Concepts
Understanding Logic Analyzer Triggering
analyzer will never trigger.
When the conditions are met in a sequence level, it is clear which
sequence level will be executed next when a “Go To” action is used, but
it is not necessarily clear if there is no “Go To”. On some logic
analyzers, if there is no “Go To”, this means that the next sequence
level should be executed. On other logic analyzers, it means the same
sequence level should be executed again. Because of this confusion, it
is good practice to always use a “Go To” action rather than relying on
the default. The new Agilent Technologies 16715/16/17/18/19A state
and timing modules deal with this problem by automatically including a
“Go To” or “Trigger” action in every sequence level. For example:
If ADDR = 1000 and DATA = 2000 then
Go to 1 <- This is automatically added on the Agilent 16715/16/17/18/19A
Next: “Boolean Expressions” on page 197
Boolean Expressions
While multiple sequence levels imply a “followed by”, within a
sequence level Boolean expressions can be used. An example is:
If ADDR = 1000 and DATA = 2000
This expression means that for this expression to be met, ADDR must
equal 1000 in the same sample that DATA equals 2000. In other words,
ADDR equals 1000 at the same time that DATA equals 2000. Therefore,
if you want to trigger on two events that occur at the same time, a
Boolean expression should be used.
It's a common mistake to try to use two sequence levels when a
Boolean expression should be used or to use a Boolean expression
when two sequence levels should be used.
NOTE: Boolean expressions are used for events that happen at the same time, and
multiple sequence levels are used when one event follows another.
Next: “Branches” on page 198