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
178
Chapter 3: Reference
Error Messages
Hardware Initialization Failed
Please go to System Administration Tools and run the Self-Test Utility
(see page 108) on the logic analyzer. If you have failures, contact your
Agilent Technologies Sales Office for service or software upgrades.
Must assign another pod pair to specify actions
for flags
In state sampling mode, when there is only one pod pair assigned to an
analyzer, flags are not available. You must assign another pod pair to
the analyzer in order for flags to be available.
In the timing sampling mode, flags are are always available.
See Also “To assign pods to one or two analyzers” on page 57
No more Edge/Glitch resources available for
this pod pair
This error occurs when you have used more than 2 edges or glitches
per pod pair in the trigger specification.
Possible Solutions
• Phrase some of the edges as patterns.
For example, if you are looking for a rising edge on a read/write line, you
can check for R/W = 0 in one level followed by R/W = 1 in the next level.
• Move some of the edges to another pod pair.
Even if a label spans pod pairs, only the edge resources of the pod pair the
specific channel is on are used.