user 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
79
Chapter 2: Task Guide
Setting Up Triggers and Running Measurements
2. Enter a time duration value.
The event must be present for the specified period of time before the
action is taken.
To specify a < duration, break down the Find pattern present for <
duration trigger function. (It actually uses occurrence counts and four
sequence levels.)
To specify an occurrence count for events
1. In the Trigger tab's Trigger Sequence area, if the occurs button is not
present, select the present for > button and choose occurs.
2. Enter an occurrence count value.
3. If the occurrence count is greater than 1, select whether the event should
occur consecutively or eventually.
The event must occur the specified number of times before the action
is taken.
To insert a store action (state mode)
You can insert store actions to override the default storage qualifier for
the samples that cause actions to occur, and you can insert store
actions to turn default storing on or off.
1. In the Trigger tab's Trigger Sequence area, select one of the action buttons
(for example, Trigger or Goto), choose Insert ACTION, choose Store, and
choose either Store sample, Don't store sample, Turn on default
storing, or Turn off default storing.
You can use store actions to set up sequence level storage qualification.
See Also “Storage Qualification” on page 201 in “Understanding Logic Analyzer
Triggering” on page 192
“To Specify Default Storing” on page 71
“To specify whether default storing is initially on or off” on page 72
To insert timer actions/events
Timers are like stopwatches. You can insert actions to start (from