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
179
Chapter 3: Reference
Error Messages
No more Pattern resources available for this
pod pair
This error occurs when you have used up all the pattern resources
available. Each pod pair has about 28 pattern resources. Some pattern
events use more than 1 resource.
Possible Solutions
• Keep labels within a pod pair
If a label (bus) spans pod pairs (for example, pods 2 and 3) then when you
use the label in a trigger sequence it will use up at least one pattern
resource on both pod pairs. If you hook up your probes in such a way that
the signals are on a single pod pair, you can free up a pattern resource on
the other pod pair.
• Move some labels to another pod pair
Each pod pair has its own set of pattern resources. Putting your two most-
used labels on different pod pairs can improve your resource usage.
You may find more information in the Branch expression is too
complex (see page 171) error message help for the 800 and 1250 Mb/s
modes.
No Trigger action found in the trace
specification
This warning occurs when the trigger sequence you specified does not
have at least one trigger and fill memory or trigger and goto action.
The analyzer will still acquire data, but you will need to manually stop
it. For example, when you use the Run until user stop function, to
avoid popping up the status window, set the popup level to errors only.