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
141
Chapter 3: Reference
Importing Netlist and ASCII Files
than 5 nsec and the clock period is greater than 10 nsec (slower than
100 MHz).
Eye Finder Load/Save Messages. These messages can appear when
saving or loading eye finder data.
"... (at line XX in the file)"
Indicates where the error occurred in the file being read. Since eye
finder data files are ASCII text, you can use a text editor to examine
the file at the indicated line to determine how to repair the problem.
"Bad assignment for XXX"
The numerical value for the item XXX could not be read.
"Cannot load Eye Finder data for a different module type. Data in file is from a
OTHERMODEL. This module is a THISMODEL."
"Cannot load Eye Finder data for a module installed in different slots. Data in file is
from a module installed in slots B A C. This module is installed in slots E D F".
"Cannot load Eye Finder data from a different instrument. Data in file is from
OTHERINSTRUMENT. This instrument is THISINSTRUMENT."
"Channel name in the data file ("OTHERNAME") does not match the expected
channel name ("THISNAME")."
"Channel number in the data file (NN) does not match the expected channel number
(MM).",
"Did not find: XXX (Search began at line LLL)"
The eye finder data file has a nested block structure. The next block
(or item) to be read was XXX, but it was not found before the end of
the file. The line after the last item successfully read was LLL.
"Error in writing"
Disk is probably full.