HP 16717A 333 MHz State/2
GHz Timing Zoom Logic
Analyzer
HP 16717A 333 MHz State/2 GHz Timing Zoom Logic
Analyzer
The HP 16717A 333 MHz State/2 GHz Timing Zoom logic analyzer
offers deep memory and very fast sample rates - up to 2 GHz for areas
around the trigger - with up to 340 channels. This logic analyzer also
marks the debut of VisiTrigger, HP’s new patented logic analyzer
triggering system.
Getting Started
•“Analyzer Probing Overview” on page 99
•“Setting Up a Measurement” on page 10
•“When Something Goes Wrong” on page 33
•“Error Messages” on page 33
Measurement Examples
•“Making a Basic Timing Measurement” on page 22
•“Making a Basic State Measurement” on page 18
•Advanced Measurement Examples (see the Measurement Examples help
volume)
•“Interpreting the Data” on page 26
More Features
“Arming Control - Multiple Instruments and Analyzers” on page 30
Using Inverse Assembly (see the Listing Display Tool help volume)
Using Symbols (see page 102)
Working with Markers (see the Markers help volume)
“Loading and Saving Logic Analyzer Configurations” on page 32
2
“Testing the Logic Analyzer Hardware” on page 42
“Specifications and Characteristics” on page 94
Interface Reference
“The Sampling Tab” on page 43
“The Format Tab” on page 52
“The Trigger Tab” on page 63
“The Symbols Tab” on page 102
Main System Help (see the HP 16600A/16700A Logic Analysis System
help volume)
Glossary of Terms (see page 129)
3
4
Contents
HP 16717A 333 MHz State/2 GHz Timing Zoom Logic Analyzer
Connect the Analyzer to the Target System10
Define the Type of Measurement11
Set Up the Bus Labels13
Define Trigger Conditions14
Run the Measurement15
Examine the Data 16
Making a Basic State Measurement18
Making a Basic Timing Measurement22
Interpreting the Data26
Analysis Using Waveform 26
Analysis Using Listing 28
Arming Control - Multiple Instruments and Analyzers 30
Loading and Saving Logic Analyzer Configurations32
Acquisition Depth43
2 GHz Timing Zoom44
Setting the Acquisition Mode44
Performing Clock Setup (State only)45
Naming the Analyzer48
Turning the Analyzer Off 48
Sample Period (Timing Only)49
Trigger Position Control 50
The Format Tab52
Activity Indicators52
Assigning Pods to the Analyzers53
Data On Clocks Display54
Labels: Mapping Analyzer Channels to Your Target58
Setting Up the Pod Clock58
Pod Selection59
Setting the Pod Threshold60
State Clock Setup/Hold (State only)60
The Trigger Tab63
6
Contents
E-mail Notify on Trigger65
What is SMTP66
Understanding Logic Analyzer Triggering 66
Setting Up a Trigger69
Inserting and Deleting Sequence Steps70
Editing Sequence Levels72
Setting Up Loops and Jumps in the Trigger Sequence72
Saving and Recalling Trigger Sequences 73
Clearing Part or All of the Trigger 74
Overview of the Trigger Sequence 75
Trigger Functions76
Trigger Function Libraries 77
Working with Advanced Functions86
Defining Events89
Tagging Data with Time or State Tags (State Only)93
Specifications and Characteristics94
What is a Specification94
What is a Characteristic94
What is a Calibration Procedure95
What is a Function Test95
HP 16717A Logic Analyzer Specifications95
HP 16717A Logic Analyzer Characteristics96
Analyzer Probing Overview99
The Symbols Tab102
Displaying Data in Symbolic Form103
7
Contents
Setting Up Object File Symbols104
To Load Object File Symbols 104
Relocating Sections of Code 106
To Delete Object File Symbol Files 107
Symbol File Formats107
Creating ASCII Symbol Files108
Creating a readers.ini File 113
User-Defined Symbols115
To Create User-Defined Symbols 115
To Replace User-Defined Symbols115
To Delete User-Defined Symbols 116
To Load User-Defined Symbols116
Using Symbols In The Logic Analyzer117
Using Symbols As Trigger Terms117
Using Symbols as Search Patterns in Listing Displays118
Using Symbols as Trigger Terms in the Source Viewer 118
Using Symbols as Pattern Filter Terms 119
Using Symbols as Ranges in the Software Performance Analyzer119
Help - How to Navigate Quickly122
Help - System Overview123
Run/Group Run Function124
Setting a tool for independent or Group Run125
Setting Single or Repetitive Run126
Checking Run Status 126
Demand Driven Data 127
Glossary
Index
8
1
HP 16717A 333 MHz State/2 GHz
Timing Zoom Logic Analyzer
After you have connected the logic analyzer probes to your target
system, (see page 10) there are five basic steps for any measurement.
1. “Define the Type of Measurement” on page 11
2. “Set Up the Bus Labels” on page 13
3. “Define Trigger Conditions” on page 14
4. “Run the Measurement” on page 15
5. “Examine the Data” on page 16
Refine measurement by repeating steps 3 - 5.
If you load a configuration file, it will set up the logic analyzer and
trigger. For your particular measurement, you may need to change
some settings.
See Also “Making a Basic Timing Measurement” on page 22
“Making a Basic State Measurement” on page 18
Measurement Examples (see the Measurement Examples help volume)
Making Basic Measurements for a self-paced tutorial
Connect the Analyzer to the Target System
Before you begin setting up a measurement, you need to physically
connect the logic analyzer to your target system. Attach the pods in a
way that keeps logically related channels together and be sure to
ground each pod. Analysis probes, available for most common
microprocessors, can simplify the connection process.
The logic analyzer pods carry the signals to the logic analyzer from
your target system. Connect the pods either directly to the target
system or to an analysis probe. You can attach the pods either directly
to a 40-pin header, to a 20-pin header with an adapter, or use the
General Purpose Probes to attach to individual channels.
If you are using an analysis probe, Setup Assistant will guide you
through the process based on your logic analyzer and the analysis
probe.
Step 1: Describe the Measurement (see page 11)
See Also“Analyzer Probing Overview” on page 99 for more detail on types of probes
Setup Assistant (see the Setup Assistant help volume)
Logic Analysis System and Measurement Modules Installation Guide
for probe pinout and circuit diagrams.
Define the Type of Measurement
There are two types of measurements: state measurements and
timing measurements. Use the Sampling tab to select either type
and to specify the details particular to that type.
In a state measurement, the analyzer uses an external clock to
determine when to sample. Each time the analyzer receives a state
clock pulse, it samples and stores the logic state of the target system.
In a timing measurement, the analyzer is analogous to an oscilloscope.
It samples at regular time intervals and displays the information in a
waveform similar to the oscilloscope.
Set Measurement Mode
Each measurement type has different measurement modes. In general,
there is a trade-off between number of signals and speed.
Because the measurement type and mode affect clocking and trigger
options, you must set the measurement type first.
Set up State Clock
For state measurements, you must specify a clock to match the
clocking arrangement used by your target system. It can be as simple
as a single rising edge, or a complex arrangement of up to four signals.
If the clock is incorrect, the trace data may indicate a problem where
there isn’t one. Specify the state clock in Clock Setup.
The equivalent in timing mode of the state clock is the Sample Period.
The Sample Period sets the time between logic analyzer samples. For
reliable data, the sample period should be no more than half of your
clock period. Many engineers prefer setting it to one-fourth of the clock
period.
Set up the Trace
The remaining controls finish your description of how you want to
capture data. The trigger position determines where the events you
specify in the trigger sequence will be relative to the majority of the
data the logic analyzer captures.
Memory depth is affected by the measurement mode. Some logic
analyzers also let you limit how big the acquisition will be with an
Acquisiton Depth control.
See Also“The Sampling Tab” on page 43 for information on setting type and
assigning pods
“Setting the Acquisition Mode” on page 44 for links to this analyzer's
modes
“Performing Clock Setup (State only)” on page 45
Set Up the Bus Labels
The next step is to finish defining the physical connection between the
target system and the analzyer. Use the Format tab to tell the analyzer
what you want to measure on the target system. If you load a
configuration file, this step is taken care of for you.
Group and Label Signals
Because the logic analyzer can capture dozens or even hundreds of
signals, you need to organize the signals by grouping and labeling
channels. Labels are used to group these channels into logical signals;
for example, "addr bus". These groupings are then used in the trigger
tab and the data displays. A label can have up to 32 channels. Each
measurement can define 126 labels. Active channels are indicated like
so .
Set Threshold Level
The logic analyzer needs to know what threshold level the target
system is using. You can set the analyzer to use TTL or ECL logic levels,
or set a different threshold voltage. The logic analyzer requires a
minimum voltage swing of 500 mV at the probe tip to recognize
changes in logic levels.
Step 3: Define Trigger Conditions (see page 14)
See Also“Assigning Bits to a Label” on page 54
“The Format Tab” on page 52
Define Trigger Conditions
The third step is to define the trigger. The trigger settings tell the
analyzer when you want to capture data. Controls for this are located
under the Tri g g e r tab. Configuration files saved from previous
measurements automatically define trigger settings.
Set Up a Trigger Sequence
The trigger sequence is like a small program that controls when the
logic analyzer stores data. There are trigger functions for the common
tasks, or you can set up your own. The logic analyzer starts at the first
trigger level, and stays there until the defined event occurs. When that
happens, it goes to the next level and follows the instructions there.
Define Events
Trigger events can be used like variables in the trigger sequence. Some
trigger functions only let you insert events that pertain to the
description of the function. The advanced functions let you insert any
type of event.
Step 4: Run the Measurement (see page 15)
See Also“Defining Events” on page 89
“Understanding Logic Analyzer Triggering” on page 66
“Setting Up a Trigger” on page 69
“The Trigger Tab” on page 63
Measurement Examples (see the Measurement Examples help volume)
Setting Up a Measurement
Run the Measurement
You run the measurement by selecting the Run button. The Run button
is labeled either Run, Group Run, or Run All. The difference between
the three types is that Run starts only the instrument you are using,
Group Run starts all instruments attached to group run in the
Intermodule window, and Run All starts all instruments currently
placed in the workspace.
Runs can be single or repetitive. Single runs gather data until the logic
analyzer memory is full, and then stop. Repetitive runs keep repeating
the same measurement and are useful for gathering statistics. To stop a
run, click Stop.
NOTE:Repetitive runs on a logic analyzer don’t do equivalent time sampling like
oscilloscopes do.
If Nothing Happens...
Analyzers with deep memory take a noticeable amount of time to
complete a run. Because data is not displayed until acquisition
completes, it may look like nothing is happening. Check the Run Status
window to see if the logic analyzer is still running. Messages such as
"Waiting in level 1" may indicate you need to refine your trigger. If the
status shows as "Stopped", the analyzer either finished the acquisition,
or was unable to run. The cause of the problem is listed in the bottom
half of the Run Status window, and the messages are explained in more
detail in “Error Messages” on page 33.
Step 5: Examine the Data (see page 16)
See Also“When Something Goes Wrong” on page 33
Examine the Data
Data from your measurement can be viewed in various display windows
or offline. Some of the things you can do in the display windows are
•Use markers to make measurements and gather statistics
Search for Patterns
You can search displays for certain values, and place markers on them.
There are two global markers which keep their place across all
measurement views, even across instruments.
Display Correlated Data
There are several tools for correlation. The Intermodule window allows
you to specify complex triggering configurations using several
instruments. It is also useful for starting acquisitions at the same time.
Global markers mark the same events in different displays, so you can
switch views without having to reorient yourself. The Compare tool lets
you compare two different acquisitions to look for changes.
Use Markers to Make Measurements
The markers can be positioned relative to the beginning, end, trigger,
or another marker, as well as set to a specific pattern, state, or time.
The Markers tab in the Display windows shows the time or state value
as you move the markers or take new acquisitions.
See AlsoWorking with Markers (see the Markers help volume)
Using the Chart Display Tool (see the Chart Display Tool help volume)
Using the Distribution Display Tool (see the Distribution Display Tool
help volume)
Using the Listing Display Tool (see the Listing Display Tool help volume)
Using the Digital Waveform Display Tool (see the Waveform Display Tool
help volume)
Using the Compare Analysis Tool (see the Compare Tool help volume)
The bit assignment field is the field to the right of a label name, and
under a pod column.
e. Select ........******** from the menu.
If none of the choices match your own system, select Individual...
and click on the individual bits to assign them (*) or ignore them (.).
5. Define trigger events for patterns on buses.
a. Click the Trigger tab.
b. Optional - Rename Pattern1.
1. Double-click in the Pattern1 field.
2. Enter a new name.
c. Select the appropriate label.
1. Click the field to the far-right of the label name.
2. To define the event as a combination of labels, click Insert... To use
a different label to define the event, click Replace...
3. In the dialog box, click the label name you want to use and then
click OK.
d. Click in the field with XX and enter the value you want to trigger on.
e. Optional - Repeat steps a - d for Pattern2.
6. Optional - Add additional trigger events to the trigger specification.
The logic analyzer automatically triggers on Pattern1, the first trigger
event. You can set up more complex triggers by editing the sequence levels
b. In the dialog box, click the Pattern1 button just after Trigger on and
select Combo...
c. In the Combination box, click Off next to Pattern2 and select On.
d. To change the trigger to Pattern1 and Pattern2, click the Or box to
the right of the events and select And.
e. Click on OK.
f. Click on Close.
The analyzer is now set to trigger when it detects both the pattern
defined by Pattern1 and the pattern defined by Pattern2 on the target
system’s buses. The trigger sequence windows shows
Trigger on "(Pattern1.Pattern2)" 1 time
See Also“The Tri gger Tab” on page 63
1. Click Run.
2. Examine the data.
a. Click the Navigate button.
b. Point to Analyzer<A> in the menu and select Listing<1>.
Depending on what other instruments are active, there may be more
than one Analyzer<A>. Choose the one that refers to your analyzer.
c. To have the listing display appear automatically when you run the logic
analyzer, select Options -> Popup on Run -> On in the menu bar of the
listing display.
d. To insert additional labels, right-click the label name.
See AlsoFor Connection Information
Logic Analysis System and Measurement Modules Installation Guide
For Details on the Training Board or More Tutorials
1. Click the label field immediately to the right of the label name.
2. To define the event as a combination of labels, click Insert... To use
a different label to define the event, click Replace... Edges within
an event are always OR’d together, which means only one of the
edges on one of the labels needs to occur for the edge event to
become true.
3. In the dialog box, click the label name you want to use and then
click OK.
d. Click the edge assignment field (........) and enter the edge or
edges you want to trigger on. Remember, if more than one edge is
specified, then when the logic analyzer detects any of the edges the
event becomes true.
6. Add the edge event to the trigger specification.
a. Right-click the 1 box and select Edit...
b. In the dialog box, click the Pattern1 button and select Combo...
c. In the Combination box, click Off next to Edge1 and select On.
d. Click the Or box where the path from Pattern1 and the path from
Edge1 come together, and select And.
e. Click on OK.
The analyzer is now set to trigger when it detects Edge1 and Pattern1
on the bus. The trigger sequence window shows
Trigger on Pattern1.Edge1 occurs 1 times
.
The logic analyzer automatically triggers on the first trigger event. You can
set up more complex triggers by editing the sequence levels and defining
additional trigger events.
See Also“The Tri gger Tab” on page 63
1. Click Run.
2. Examine the data.
a. Click the Navigate button.
b. Point to Analyzer<A> in the menu and select Waveform<1>.
After you’ve acquired a trace with the logic analyzer, you can analyze it
in the display tools. The logic analysis system also provides filtering
and compare tools for more complex analysis.
The logic analyzer is automatically connected to the Waveform and
Listing displays when you set up a measurement. To move to that
display,
1. Right-click the blue Navigate button.
2. Move the cursor over the name of the analyzer whose data you want to
view.
3. Click on Waveform or Listing.
Source Viewer brings up a Listing display but requires an inverse
assembler and an ADDR label.
•“Analysis Using Waveform” on page 26
•“Analysis Using Listing” on page 28
Analysis Using Waveform
Waveform is most useful for timing data. If you look at state data that
uses store qualification, you won’t be able to easily see where samples
were not stored. Timing data, however, is periodic and stores all
samples and so works well with Waveform.
Example: Looking for a Missing Pattern
You can easily use the waveform tool to make timing measurements.
For example, if you were triggering when a pattern doesn’t follow an
edge within a certain time (see the Measurement Examples help
volume), you would probably want to look at your data set to see if the
pattern ever did occur. This might be the case when you verifying that
the system is responding to an interrupt.
After triggering on an instance where the response did not appear
quickly enough, you might take these steps in the Waveform display:
1. Find the edge.
a. Click Search.
b. Click the down arrow after the Label field, and select the label
containing the edge.
c. Click the Value field and type 1.
d. Click Next to locate the edge transition.
2. Place a marker on the edge.
Click Set G1. This sets global marker G1 at the location of the edge you
just found.
3. Search for the pattern. Searches start at your current location. Since you
just set the global marker G1, it indicates where the search starts from.
a. Click the down arrow after the Label field, and select the label
containing the pattern.
b. Click the Value field and type the pattern you are searching for.
c. Click the down arrow after the When field and select Entering.
d. Click Next to find the next occurrence of that pattern after G1.
If the logic analysis system cannot find the pattern, a "Value not found"
message pops up.
4. Place a marker on the pattern.
Click Set G2. This will set global marker G2 at the location of the pattern.
5. Find the time between the edge and the pattern.
a. Click Markers.
b. In the G2 row, click the down arrow after from, and select G1.
The value after the from field changes to the time between G1 and G2. You
can toggle between time and samples by clicking the arrow after the Time
or Samples field.
See AlsoUsing the Digital Waveform Display Tool (see the Waveform Display Tool
Using the Listing Display Tool (see the Listing Display Tool help volume)
Using the Chart Display Tool (see the Chart Display Tool help volume)
Using the Distribution Display Tool (see the Distribution Display Tool
help volume)
Using the Compare Analysis Tool (see the Compare Tool help volume)
Using the Pattern Filter Analysis Tool (see the Pattern Filter Tool help
volume)
Analysis Using Listing
Listing is more useful than Waveform when your target system is
running code because it shows the labels as states rather than
transitions. Listing is especially useful when you have defined
meaningful symbol names for your states. If you have an inverse
assembler, you might prefer Source Viewer which functions like
Listing.
Example: Examining a Subroutine
Listing is the preferred display tool for state measurements. for
example, if you were trying to see if a subroutine were exiting
abnormally, you might want to measure the number of states between
entering and exiting the subroutine. After acquiring data with the logic
analyzer, you could examine the data set in the Listing display like this:
1. Find the start of the subroutine.
Assume the subroutine starts at the address 0x58FC.
a. Click Search.
b. Click the down arrow after the Label field, and select ADDR.
c. Click the Value field, and type in the starting address, 0x58FC.
d. Click the down arrow after the When field and select Present.
e. Click Next or Prev to move the display to the address.
Click Set G1. This sets global marker G1 at the address you just found.
3. Find the end of the subroutine.
Assume the end of the subroutine is at address 0x58FF. Searches always
start at the current location. Since you just set the global marker G1, it
indicates where the search starts from.
a. Click the Value field, and enter 58FF.
b. Click Next to find the next occurrence of 0x58FF after the starting
address.
4. Place a marker on the end of the subroutine.
Click Set G2 to set global marker G2 at this position. This lets you refer to
G2 when you want to know where the subroutine ends.
5. Find the number of states between the start and end of the subroutine.
Since you’ve placed markers at the start and end of the subroutine, all you
have to do is find the number of states between those markers.
a. Click Markers.
b. In the G2 row, click the second down arrow and select Sample.
c. Click the down arrow after from, and select G1.
The value after the from field changes to the number of states between G1
and G2. You can toggle between time and states by clicking the arrow after
the Time or Samples field.
Now you know how long the execution stayed in the subroutine, and
can also examine the data set between G1 and G2 to look for unusual
data.
See AlsoUsing the Digital Waveform Display Tool (see the Waveform Display Tool
help volume)
Using the Listing Display Tool (see the Listing Display Tool help volume)
Using the Chart Display Tool (see the Chart Display Tool help volume)
Using the Distribution Display Tool (see the Distribution Display Tool
help volume)
Using the Compare Analysis Tool (see the Compare Tool help volume)
Using the Pattern Filter Analysis Tool (see the Pattern Filter Tool help
volume)
Arming Control - Multiple Instruments and
Analyzers
An instrument must be armed before it can look for its trigger. If you
have not specified any arming actions, by default the instrument is set
to be armed immediately when you Run the measurement.
You can configure an analyzer instrument to be armed by either
another instrument (different slot or frame), or, by the second analyzer
within the same instrument if that second analyzer is turned on.
To configure an analyzer instrument to arm other instruments, it must
first be included in the Group Run Arming Tree (see the HP 16600A/16700A Logic Analysis System help volume). Next, in the analyzer
instrument Setup window, go to Settings under Trigge r, and specify
the analyzer which will drive the Arm Out signal. The specified
analyzer’s Trigger and fill memory action becomes Trigger, arm out, and fill memory.
To change the source of Arm In or the destination of Arm Out, use the
Intermodule Window (see the HP 16600A/16700A Logic Analysis System help volume).
Setting One Analyzer to Arm the Other
1. Activate the second analyzer.
a. In Format, click Pod Assignment...
b. In the Pod Assignment dialog, change the analyzer type from Off.
The system pauses while setting up the second analyzer. When it is
done, a setup window for the second analyzer appears.
2. In Trigger, click the Trigger Functions tab.
3. Select Wait for second analyzer to trigger from the function list.
30
Loading...
+ 116 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.