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
165
Chapter 3: Reference
The Symbols Tab
The address or address range must be a hexadecimal number. It must
appear on the same line as the symbol name, and it must be separated
from the symbol name by one or more blank spaces or tabs. Address
ranges must be in the following format:
beginning address..ending address
The following example defines two symbols that correspond to address
ranges and one symbol that corresponds to a single address.
main 00001000..00001009
test 00001010..0000101F
var1 00001E22 #this is a variable
For more detailed descriptions of GPA file records and associated
symbol definition syntax, refer to the following topics:
• “SECTIONS” on page 166
• “FUNCTIONS” on page 167
• “VARIABLES” on page 168
• “SOURCE LINES” on page 168
• “START ADDRESS” on page 169
• “Comments” on page 169
GPA Record Format Summary
Format
[SECTIONS]
section_name start..end attribute
[FUNCTIONS]
func_name start..end
[VARIABLES]
var_name start [size]
var_name start..end
[SOURCE LINES]
File: file_name
line# address