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
137
Chapter 3: Reference
Importing Netlist and ASCII Files
An eye finder measurement is currently running. Stop the eye finder
or wait for it to complete before running the eye finder.
The eye finder is already running on the other machine defined for
this analyzer. Eye finder cannot run on both machines at the same
time.
"Cannot run the Logic Analyzer at this time."
An eye finder measurement is currently running. Stop the eye finder
measurement or wait for it to complete before running the logic
analyzer measurement.
Eye finder uses the same hardware as an ordinary logic analyzer
measurement uses. Therefore, they cannot be performed at the same
time.
"Characterizer cannot be loaded"
This is an internal error. It means that a software unit responsible for
measuring one of the channels did not fit the hardware setup and the
other characterizers which were already loaded. Try running eye
finder on just one label (or one channel) at a time to attempt to clear it
up. Contact support if this persists.
"Complete: DATE"
The measurement completed successfully on the date and time given.
This time may also be accessed by expanding a label in the results
display and selecting the clock icon or selecting "Show Time Stamp" on
the popup menu raised by selecting the channel name in the results
display.
"Eye Finder only operates when the analyzer clocking is master clock (slave and/or
demux clocking are not supported)."
See the "Clock Setup" section of the "Sampling" tab in the analyzer
setup window.
"Eye Finder only operates when the analyzer is setup for state analysis."
See the "Pod Assignment" dialog accessed from the "Format" tab in the
analyzer setup window.