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
95
Chapter 2: Task Guide
Using Symbols
Using Symbols
You can use symbol names in place of data values when:
• Setting up triggers
• Displaying captured data
• Searching for patterns in Listing displays
• Setting up pattern filters
• Setting up ranges in the System Performance Analyzer
Symbol names can be: variable names, procedure names, function
names, source file line numbers, etc.
You can load symbol name definitions into the logic analyzer from a
program's object file or from a general-purpose ASCII format symbol
file, or you can define symbol names in the logic analyzer.
• “To load object file symbols” on page 96
• “To adjust symbol values for relocated code” on page 97
• “To create user-defined symbols” on page 98
• “To enter symbolic label values” on page 99
• “To create an ASCII symbol file” on page 100
• “To create a readers.ini file” on page 101
See Also To go to a pattern in the Listing (see the Listing Display Tool help
volume)
To modify the Source Viewer trace setup (see the Listing Display Tool
help volume)
To define System Performance Analyzer state interval ranges (see the
System Performance Analyzer help volume)