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
170
Chapter 3: Reference
Error Messages
Error Messages
• “Analyzer armed from another module contains no "Arm in from IMB"
event” on page 185
• “Branch expression is too complex” on page 171
• “Cannot specify range on label with clock bits that span pod pairs” on
page 176
• “Counter value checked as an event, but no increment action specified” on
page 177
• “Goto action specifies an undefined level” on page 177
• “Hardware Initialization Failed” on page 178
• “Maximum of 32 Channels Per Label” on page 177
• “Must assign another pod pair to specify actions for flags” on page 178
• “Must assign Pod 1 on the master card to specify actions for flags” on
page 171
• “No more Edge/Glitch resources available for this pod pair” on page 178
• “No more Pattern resources available for this pod pair” on page 179
• “No Trigger action found in the trace specification” on page 179
• “Slow or Missing Clock” on page 180
• “Timer value checked as an event, but no start action specified” on
page 180
• “Trigger function initialization failure” on page 181
• “Trigger inhibited during timing prestore” on page 182
• “Trigger Specification is too complex” on page 182
• “Waiting for Trigger” on page 184