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
167
Chapter 3: Reference
The Symbols Tab
NOTE: If you use section definitions in a GPA symbol file, any subsequent function or
variable definitions must be within the address ranges of one of the defined
sections. Functions and variables that are not within the range are ignored.
Format
[SECTIONS]
section_name start..end attribute
section_name A symbol representing the name of the section.
start The first address of the section, in hexadecimal.
end The last address of the section, in hexadecimal.
attribute (optional) Attribute may be one of the following:
NORMAL (default) - The section is a normal, relocatable section, such as
code or data.
NONRELOC - The section contains variables or code that cannot be
relocated. In other words, this is an absolute segment.
Example
[SECTIONS]
prog 00001000..00001FFF
data 00002000..00003FFF
display_io 00008000..0000801F NONRELOC
FUNCTIONS
Use FUNCTIONS to define symbols for program functions, procedures
or subroutines.
Format
[FUNCTIONS]
func_name start..end
func_name A symbol representing the function name.
start The first address of the function, in hexadecimal.
end The last address of the function, in hexadecimal.
Example
[FUNCTIONS]
main 00001000..00001009
test 00001010..0000101F