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
176
Chapter 3: Reference
Error Messages
combine 2 non-split labels that are ANDed together even though it fails to
compile a pattern on a single label that spans pods.
• Cannot specify more than 3 patterns or 1 range per pod.
Non-split patterns may use operations: =, !=, <, <=,>, >=, In range, Not
in range.
Split patterns may only use operations: =, !=.
Patterns on labels with re-ordered bits may only use operations: =, !=
(same as Timing and 200 and 400 Mb/s modes).
• Restrictions on the ways event resources can be used and combined vary
with the type of trigger function selected.
The "Find Pattern" and "Find 2 Patterns in Immediate Sequence"
trigger functions can use all of the available pattern events in any
sequence level. However, some combinations (ANDing and ORing) of
pattern events, while not exceeding the maximum number of pattern
resources, can use too many combiner resources. Any combination of 3
of the flag events and "Wait for arm in from IMB" event can also be
combined with the pattern events in each sequence level.
When using the "Find 2 Patterns in Eventual Sequence" trigger
function, only non-split labels may be used and only one pattern event
per sequence level may be used. The interface allows insertion of other
events in each sequence level to allow ANDing or ORing of the pattern
event with other event types (flags or arm in) or replacement of the
pattern event with another event type. However, if more than one
pattern event is specified the trigger compiler will be unable to compile
it.
• Pattern events used in the Default Storing Control count against the
number of available resources.
Cannot specify range on label with clock bits
that span pod pairs
A label that contains clock bits being used as data bits, can only be
included in a range term if the clock bits are confined to a single pod
pair.