System information

ManualsBrandsAgilent Technologies ManualsComputer equipment16700 SERIES LOGIC ANALYSIS SYSTEM 16700

Post-Processing Tool Sets for the

Agilent Technologies 16700A

Series Logic Analysis Systems

Product Overview

Solutions for Digital

System Debug

Post-processing tools

provide rapid insight

into your toughest debug

problems

When you want to understand what

your target is doing and why, you

need to view acquisition results in a

format that quickly guides you to

problem identification.

The tool sets described in the

following pages are optional, post-

processing software packages for

the Agilent Technologies 16700A

Series logic analysis systems. Each

tool set provides digital design

engineers like you insight into your

specific application.

You have unique measurement and

analysis needs. Agilent Technolo-

gies’ combination of powerful trig-

gering and deep trace provides the

ability to precisely acquire large

quantities of data around a speci-

fied sequence of events.

Once the data is acquired, you can

rely on the analysis tools to rapidly

consolidate data into displays that

provide insight into your system’s

behavior.

Free Tool Set Evaluation

To see which tool sets best fit your

needs, Agilent Technologies offers a

free 21-day trial period that lets you

evaluate any tool set as your work

schedule permits. Once you receive

your tool, you obtain a password

that temporarily enables the tool.

(See page 35 for information on

evaluation and tool set pass-

words.)

Application Product Name Agilent Model Detailed

Number Information

Debug your real-time code at the source level Source Correlation B4620B Pgs 3-6

Correlate a logic analyzer trace with the high-level source code Tool Set

that produced it. Set up the logic analyzer trace by simply pointing

and clicking on a line of source code.

Debug your parallel data communications buses Data Communications B4640B Pgs 7-15

Display logic analyzer trace information at a protocol level. Tool Set

Powerful trigger macros allow triggering on standard or

custom protocol fields. Supports data buses up to 32 bits wide.

Customize your trace for greater insight Tool Development Kit B4605B Pgs 16-22

Create custom tools using the C programming language.

Custom tools can analyze captured data and present it

in a form that makes sense to you. Analysis systems do not require

the tool development kit to run generated tools.

Optimize your system’s performance System Performance B4600B Pgs 23-28

Profile your system’s performance to identify system Analysis Tool Set

bottlenecks and to identify areas needing optimization.

Solve your serial communication problems Serial Analysis B4601B Pgs 29-34

Convert serial bit streams to parallel format for easy viewing and Tool Set

analysis. Supports serial data with or without an external clock

reference and protocols that use bit stuffing to maintain clock

synchronization. Works at speeds up to 1 GHz.

Table 1. Applications for the Agilent Technologies Post-Processing Tool Sets.

Summary of content (36 pages)

PAGE 1
Post-Processing Tool Sets for the Agilent Technologies 16700A Series Logic Analysis Systems Product Overview Solutions for Digital System Debug Post-processing tools provide rapid insight into your toughest debug problems Series logic analysis systems. Each tool set provides digital design engineers like you insight into your specific application.
PAGE 2
Seamless Integration with Your Development Environment Remotely access any tool set from a PC or workstation through your web browser or X-window emulation software. You can also use an SVGA monitor to locally control and view measurements at your lab bench. Access source files or other development environment applications (compiler, debugger) from your 16700A Series system via Telnet, NFS or mapped file systems, and X-Windows client/server protocols.
PAGE 3
The Source Correlation Tool Set Debug Your Source Code 3 Obtain Answers to the Following Questions: Software-Hardware Integration • What is the root cause of a system As an engineer, you are responsifailure—hardware or software? ble for the flawless execution of Software Code Execution • Are timing anomalies found by the your software in its real-time • What happened just before the hardware engineer the cause of environment.
PAGE 4
The Source Correlation Tool Set (continued) When You Want to Trace . . . ...on a variable to see what caused data corruption. ...on a function to determine where it is being called from in order to understand the context of a system error. ...on a line number to determine if a specific code segment is ever executed. Simply Click . . . ... to trace about a variable, function, or line number. ... to halt processor execution with an integrated emulation module when the trace event occurs. ...
PAGE 5
The Source Correlation Tool Set (continued) 5 Once You Acquire the Trace . . . ...“step” through the trace at the sourcecode level or the assembly level. Locate the cause of a problem by “stepping backward” from the point where you see a problem to its root cause. ...quickly locate a specific function, variable, or text string. The system maintains a history of previous text searches for quick recall. ...click the source line which you want to trace about on your next acquisition. ...
PAGE 6
The Source Correlation Tool Set (continued) Product Characteristics Data Sources All state and timing measurement modules supported by the 16700A Series logic analysis systems (except the 16517A/518A) serve as data sources for the source correlation tool set.
PAGE 7
Data Communications Tool Set 7 Monitor Packet Information on Parallel Data Buses The powerful protocol trigger macro allows easy trigger setup by eliminating the need to manually configure the trigger sequencer for complex measurements. All custom-defined protocol fields or layers are supported in the trigger macro.
PAGE 8
Data Communications Tool Set (continued) 8 Theory of Operation UTOPIA Level 2 Custom / UTOPIA CPU PHY PHY ATM Layer ATM Layer PHY PHY Switch Fabric PHY ATM Layer ATM Layer PHY PHY UTOPIA Level 1 Figure 3: Typical ATM Switch Design. The logic analyzer probes the parallel data buses in the system, such as the UTOPIA shown above. The logic analyzer needs access to data signals, qualifying signals, start of cell or packet bit, and the synchronous clock for the bus.
PAGE 9
Data Communications Tool Set (continued) Edit or create a protocol using the logic analyzer user interface. Select a known protocol and add proprietary fields. Insert custom wrapper or field here. Insert name, number of bits and format for trigger and display. Define any symbols for both trigger and display of packets. Edit or create a protocol using a text file. Start with standard protocol definition and add custom fields with text file. Insert protocol layer name.
PAGE 10
Data Communications Tool Set (continued) 10 Trigger Interface New packet trigger macros. Specify protocol layer to trigger on. Trigger on simple IP address instead of setting up trigger sequencer. Specify what action to perform once a packet is found. Specify protocol layer to trigger on. Use any defined protocol fields as a trigger, such as source address, destination address, etc. Physical representation of bit fields to be triggered on. This window is automatically updated when fields are edited.
PAGE 11
Data Communications Tool Set (continued) 11 View the actual trigger sequencer setup. Up to 16 trigger sequences are available for a measurement.
PAGE 12
Data Communications Tool Set (continued) 12 Display of custom protocol levels. Protocol view of data acquired in logic analyzer. Time tags for system level correlation of other data buses, memory interfaces, microprocessors, etc.
PAGE 13
Data Communications Tool Set (continued) 13 Protocol Filters and Viewing Preferences Filter captured data to only view key data for measurement. Choose to view payload data with header information. Select which protocol layers and fields to view in trace.
PAGE 14
Data Communications Tool Set (continued) 14 Global markers measure time intervals between packets on separate parallel interfaces or timing between the data path and a microprocessor. Collapsed view of protocol information using preferences. Raw packet header information. Raw payload information.
PAGE 15
Data Communications Tool Set (continued) Product Characteristics Requires a 16700/702A Series logic analysis system with operating system version A.01.50.00 or later. Logic Analysis Modules Supported: Agilent Technologies 16715A, 16716A, 16717A, 16718A, and 16719A Protocols Supported: Ethernet and ATM* * These are example files shipped with the product. These standard files can be edited to include any custom protocol layers or fields.
PAGE 16
The Tool Development Kit 16 Customize Your Measurements Product Description A logic analysis system is used to obtain critical information about your system. At times the information you need can be buried in the raw data of your measurement.
PAGE 17
The Tool Development Kit (continued) With Custom Tools You Can: Enhance How Data is Displayed • Color-code specific states of your trace. • Display some of your trace data in engineering units. • Convert the raw trace of a proprietary bus to a transaction-level trace of that bus. Manipulate Data • Unravel interleaved data into two or more columns of data. • Combine the traces of two different analyzers into one trace, with each column being combined or separately displayed as prescribed by you.
PAGE 18
The Tool Development Kit (continued) 18 Custom Tool Examples, Microprocessor Code Reconstruction The code was reconstructed by using the branch trace messages and information in the SRecord file created when the code was compiled. The tool took the address of the appropriate states in the trace data and found the corresponding code (data) in the SRecord file. This created a trace that the MPC 555 inverse assembler could operate on properly.
PAGE 19
The Tool Development Kit (continued) 19 Custom Tool Examples, Multiplex Data Custom tools can combine several lines of data acquired sequentially under one label into one line of data. However the data to be combined does not have to come from the same label, it can come from different labels. The labels can even come from different analyzers. Output of Custom Tool Original Trace At left are the parameter window and message display created by the custom tool in this example.
PAGE 20
The Tool Development Kit (continued) Custom Tool Examples, FFT Algorithm In this example the output of a scope module is modified by a custom tool using a FFT algorithm. The tool’s output is then displayed 20 using the chart display. This is an example of how custom tools can be used with something other than state traces. While the chart does not have label vs label, you can get an idea of the characteristics of the signal acquired by the scope.
PAGE 21
The Tool Development Kit (continued) 21 Custom Tool Development Environment This is the main window for developing code with the tool development kit. Select this button to cause the compiled code to operate on the acquired data. Select this button to compile the code displayed in the “Source Code” tab. Load a file created on another system or create your code here using the “Source Code” editor. Errors generated during a compile are displayed in the “Buildtime” tab.
PAGE 22
The Tool Development Kit (continued) 22 Custom Tool Development Environment (continued) This window provides the information and icon necessary to create an installable tool. Once your code has been created and is working properly, you can create an installable tool for use on other 16700A Series analysis systems. Name the tool and manage versions of it here. Select the icon for the tool here. New icons can be created and added to the toolbar if you like. Add your tool descriptions here.
PAGE 23
The System Performance Analysis Tool Set 23 Optimize System Performance Product Description Software Execution Coverage • Do my test suites provide thorough coverage of my application? Getting your target system up and • Is this function or variable accessed by the application? running is clearly the first priority for successful product developDebug and System ment. But a working system isn’t Parameter Analysis enough.
PAGE 24
The System Performance Analysis Tool Set (continued) Identify which Events Occur Most Frequently State Overview Tool Use this tool as the first step of the analysis or optimization process to identify which events occur most frequently during a measurement. The tool interprets the captured data and displays the number of hits for each possible bus state. Narrow in on an area of interest using built-in qualification and zoom functions.
PAGE 25
The System Performance Analysis Tool Set (continued) Determine which Functions Use the Most CPU Cycles State Interval Tool Help prioritize functions that are candidates for duration measurements using the time interval tool. The histogram display shows the percentage of time the system is spending in each procedure, function, or event (states). Events are defined as patterns or ranges associated with any set of data (labels, symbols). 25 Use this tool to show which functions are using the most CPU cycles.
PAGE 26
The System Performance Analysis Tool Set (continued) Determine a Specific Routine’s Execution Times Time Interval Tool Examine execution times and verify signal timing specifications using the time interval tool. Results from the tool help you determine the best and worst 26 execution scenarios so you can decide if optimization is needed. The time interval tool uses a histogram to display a distribution of the execution time of a specific function or of the time between two user-defined events.
PAGE 27
The System Performance Analysis Tool Set (continued) View the Frequency of Events Over Time the occurrence rate of any event, including interrupts, over time. Time Overview Tool Use the time overview tool to show the variation in the frequency of events as you vary test conditions. The tool measures Define the event and time period in which events are counted. Also define the width of the time buckets and number of time buckets based on the frequency of events you expect.
PAGE 28
The System Performance Analysis Tool Set (continued) 28 Product Characteristics Off-Line Analysis and Post-Processing All measurements can be saved using the file out tool. Data can be recalled at any time for later analysis using any SPA or other tool. Performance measurements can be exported to your host computer as histograms or as tabularformatted text files.
PAGE 29
The Serial Analysis Tool Set Solve Serial Communication Problems Your system uses serial buses to communicate between ICs and to transfer data to and from peripheral devices. Sifting through thousands of serial bits by looking at long vertical columns of captured 1’s and 0’s can be very tedious, time-consuming, and error-prone.
PAGE 30
The Serial Analysis Tool Set (continued) 30 When You Want to Analyze Serial Bit Streams . . . ...specify which signal you want to convert to parallel format by selecting a specific bit of any available label. ...accept the default output label“Parallel” or modify the label name for easy recognition. ...set the output parallel word width (up to 32 bits). ...select the specific state in the trace where conversion begins. ...
PAGE 31
The Serial Analysis Tool Set (continued) 31 To Separate Frame Information from the Data Block . . . ...accept the default start of frame label “Start” or modify the label to a name of your choosing. ...specify the pattern that designates the start of a frame. ...get immediate feedback as you configure the tool set for your data. This diagram changes as you make your framing and data block selections. ...remove stuffed 0s or 0/1s from the trace before other serial analysis functions are performed.
PAGE 32
The Serial Analysis Tool Set (continued) 32 To Acquire a Serial Bit Stream without an External Clock Reference . . . ...set the sample period of your timing analyzer to take four or more samples for each serial bit. ...accept the “Samples” default label or enter a new label name. ...specify the embedded bit time of the serial bit stream. ...specify the incoming signal’s data encoding method, normal or NRZI. Clock Recovery Algorithm 1.
PAGE 33
The Serial Analysis Tool Set (continued) 33 Once the Serial Bit Stream is Acquired . . . This example shows the conversion of an RS232 serial bit stream. The data sent to the printer includes the column header ”MACHINE”. ...configure the serial tool once for your specific bus, then save the configuration for future uses. ...view the serial-to-parallel conversion in the format that is easiest for you — waveform or listing. ...
PAGE 34
The Serial Analysis Tool Set (continued) Product Characteristics Data Sources All state and timing measurement modules supported by the 16700A Series logic analysis systems serve without modification as data sources for the B4601B serial analysis tool set. The particular measurement module used determines time resolution and accuracy.
PAGE 35
Tool Set Licensing Information License Policy The 16700A Series logic analysis systems’ tool set software is licensed for single-unit use only. Licenses are valid for the life of the tool set. Software updates do not affect the license. Nodelock Mode Tool set licenses are shipped or first installed as nodelocked applications. Nodelocked means that use of the tool set license is only allowed on the single node (16700A Series analyzer) on which it is installed.
PAGE 36
Ordering Information www.agilent.com Agilent Model Number and Description For more information about Agilent Technologies test and measurement products, applications, services, and for a current sales office listing, visit our web site: http://www.agilent.