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
181
Chapter 3: Reference
Error Messages
Resume in any action. You do not need to start the timer in the same
sequence level. The timer will still function if not started, but will not
change value.
Trigger function initialization failure
The "trigger function initialization failure" messages mean that you
tried to insert a trigger function which required a change to the trigger
function default state.
Possible Causes
• Tried to insert "Wait for arm in" trigger function
A "Wait for arm in" trigger level causes the logic analyzer to wait for a
signal from another module or Port In. These signals are passed through
the Intermodule Bus. To prevent the logic analyzer from hanging, it must
be added to the Group Run Arming Tree. To do this, open the Intermodule
window by selecting the Intermodule icon in the System window. In the
Intermodule window, select the analyzer icon and select any option except
for Independent.
• Tried to insert "Wait for other machine to trigger" function
A "Wait for the other machine to trigger" trigger level causes the logic
analyzer to wait for a signal from the other logic analyzer machine in the
module. If this machine is not on, the current logic analyzer will hang. To
turn the other machine on, select Pod Assignment under Format. Set the
type of the other machine to State or Timing.
•In Format, no labels have bits assigned to them.
When you insert a trigger function, the logic analyzer sets up a field for you
to enter values. The field length is based on the number of bits assigned to
the first active label, or the label you specify. If there are no bits assigned
to the label, the logic analyzer cannot complete the value field.
See Also Using the Intermodule Window (see the Agilent Technologies 16700A/B-
Series Logic Analysis System help volume)
“To assign probe channels to labels” on page 59