Integrated Logic Analyzer V6.1: Logicore Ip Product Guide
Integrated Logic Analyzer V6.1: Logicore Ip Product Guide
Analyzer v6.1
Chapter 1: Overview
Feature Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Licensing and Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Overview
Feature Summary
Signals in the FPGA design are connected to ILA core clock and probe inputs (Figure 1-1).
These signals, attached to the probe inputs, are sampled at design speeds and stored using
on-chip block RAM (BRAM). The core parameters specify the number of probes, trace
sample depth, and the width for each probe input. Communication with the ILA core is
conducted using an auto-instantiated debug core hub that connects to the JTAG interface
of the FPGA.
X-Ref Target - Figure 1
,/$&RUH
FON WULJBRXW
WULJBLQ WULJBLQBDFN
WULJBRXWBDFN 6ORWBB$;,
SUREH
SUREH
SUREH
;
After the design is loaded into the FPGA, use the Vivado ® logic analyzer software to set up
a trigger event for the ILA measurement. After the trigger occurs, the sample buffer is filled
and uploaded into the Vivado logic analyzer. You can view this data using the waveform
window.
Regular FPGA logic is used to implement the probe sample and trigger functionality.
On-chip block RAM memory stores the data until it is uploaded by the software. No user
input or output is required to trigger events, capture data, or to communicate with the ILA
core.
IMPORTANT: Note that the comparator is set at run time through the Vivado logic analyzer.
Applications
The ILA core is designed to be used in any application that requires verification or
debugging using the Vivado logic analyzer.
Information about this and other Xilinx LogiCORE IP modules is available at the Xilinx
Intellectual Property page. For information about pricing and availability of other Xilinx
LogiCORE IP modules and tools, contact your local Xilinx sales representative.
License Checkers
If the IP requires a license key, the key must be verified. The Vivado design tools have
several license checkpoints for gating licensed IP through the flow. If the license check
succeeds, the IP can continue generation. Otherwise, generation halts with error. License
checkpoints are enforced by the following tools:
• Vivado synthesis
• Vivado implementation
• Bitstream generation
IMPORTANT: IP license level is ignored at checkpoints. The test confirms a valid license exists. It does
not check IP license level.
Product Specification
Performance
The ILA core can be configured to Select 1,024 probes each of width ranging from 1 to
4,096. This probe ports should be connected to user design signals which needs to be
monitored in Vivado ® logic analyzer during the run time.
Resource Utilization
For full details about performance and resource utilization, visit the Performance and
Resource Utilization web page.
Port Descriptions
ILA Ports and Parameters
Table 2-1 and Table 2-2 provide the details about the ILA ports and parameters.
Notes:
1. The maximum number of compare value (match) units are limited to 1,024. For the basic trigger (C_ADV_TRIGGER = FALSE),
each probe has one compare value unit (as in the earlier version). But for the advance trigger option (C_ADV_TRIGGER =
TRUE), this means the individual probes can still have possible selection of number of compare values units from one to four.
But all of the compare value units cannot exceed more than 1,024. This also means if you need four compare units per probe
then you are allowed to use only 256 probes.
Clocking
The clk input port is the clock used by the ILA core to register the probe values. For best
results, it should be the same clock signal that is synchronous to the design logic that is
attached to the probe ports of the ILA core.
Resets
ILA can only be reset using the Vivado ® logic analyzer.
• Vivado Design Suite User Guide: Designing IP Subsystems using IP Integrator (UG994)
[Ref 3]
• Vivado Design Suite User Guide: Designing with IP (UG896) [Ref 2]
• Vivado Design Suite User Guide: Getting Started (UG910) [Ref 4]
If you are customizing and generating the core in the IP integrator, see the Vivado Design
Suite User Guide: Designing IP Subsystems using IP Integrator (UG994) [Ref 3] for detailed
information. IP integrator might auto-compute certain configuration values when
validating or generating the design. To check whether the values change, see the
description of the parameter in this chapter. To view the parameter value, run the
validate_bd_design command in the Tcl console.
You can customize the IP for use in your design by specifying values for the various
parameters associated with the IP core using the following steps:
For details, see the Vivado Design Suite User Guide: Designing with IP (UG896) [Ref 2] and
the Vivado Design Suite User Guide: Getting Started (UG910) [Ref 4].
Note: Figures in this chapter are illustrations of the Vivado Integrated Design Environment. This
layout might vary from the current version.
1. Open a project by selecting File then Open Project or create a new project by selecting
File then New Project in Vivado.
2. Open the IP catalog and navigate to any of the taxonomies.
3. Double-click ILA to bring up the core name Vivado IDE.
Figure 4-2 shows the General Options tab in the AXI setting that allows you to specify the
options.
X-Ref Target - Figure 4-2
• Component Name – Use this text field to provide a unique module name for the ILA
core.
• Monitor Type – This option specifies which type of interface ILA should be debugging.
Currently the values for this parameter are "native" and "AXI."
• C_NUM_MONITOR_SLOTS (Only available in AXI type) – This option allows you to
select the number of AXI interface slots that needs to be connected to the ILA. For
2014.1 to currently, only one slot is supported for the ILA.
• Number of Probes – Use this text field to select the number of probe ports on the ILA
core. The valid range used in the Vivado IDE is 1 to 64. If you need more than 64 probe
ports, you need to use the Tcl command flow to generate the ILA core.
• Sample Data Depth – Select the suitable sample depth from the drop-down menu.
° Trigger Out Port – Check to enable the optional trigger out port.
• Probe Port Panels – Width of each Probe Port can be configured in Probe Port Panels.
Each Probe Port Panel has up to seven ports.
Also, number of comparator per probe can be configured on this panel. This option
appears only when Advanced Trigger option is selected and the Same No. of
Comparator for all Probes is disabled on the first page of Vivado IDE.
• C_ENABLE_AXI_MON – Enables AXI monitor in the ILA IP core. This option allows you
to debug designs with AXI interface at interface level.
• C_SLOT_0_AXI_ARUSER_WIDTH – Default value is always 1 (Not shown in the AXI Read
Address Channel User Width of the Vivado IDE).
• C_SLOT_0_AXI_RUSER_WIDTH – Default value is always 1 (Not shown in the AXI Read
Channel User Width of the Vivado IDE).
• C_SLOT_0_AXI_AWUSER_WIDTH – Default value is always 1 (Not shown in the AXI
Write Address Channel User Width of the Vivado IDE).
Output Generation
For details, see the Vivado Design Suite User Guide: Designing with IP (UG896) [Ref 2].
Required Constraints
The ILA core includes an XDC file that contains appropriate false path constraints to prevent
the over-constraining of clock domain crossing synchronization paths. It is also expected
that the clock signal connected to the clk input port of the ILA core is properly constrained
in your design.
Clock Frequencies
This section is not applicable for this IP core.
Clock Management
This section is not applicable for this IP core.
Clock Placement
This section is not applicable for this IP core.
Banking
This section is not applicable for this IP core.
Transceiver Placement
This section is not applicable for this IP core.
Simulation
This core does not support simulation.
IMPORTANT: Synthesis with Synopsys Synplify is not supported for the core.
Example Design
This chapter contains information about the example design provided in the Vivado®
Design Suite.
<component name>_example/<component
name>_example.srcs/
This directory contains the source files needed to synthesize the ILA core whose name is
<component name>.
Implementation
To implement the example design, select Run Implementation in the Vivado Project
Manager window. For further details on setting up the implementation, see the Vivado
Design Suite User Guide: Implementation (UG904) [Ref 6].
Test Bench
There is no test bench for this IP core release.
Port Changes
• The maximum number of Probe ports is 1,024 and the maximum width of each Probe
port can be up to 4,096. However, the total number of bits (sum of all probe ports)
cannot exceed 65,536 bits.
• The port names are changed from uppercase to lowercase and you have to take care of
updating this in your design.
• There are other new parameters added to support the new features. For example,
° Storage Qualifier
° Advance Trigger
• The new features are default disable to have backward compatibility.
• To upgrade the IP to the latest version use the upgrade IP service in Vivado.
Functionality Changes
The ILA v5.1 core no longer has separate Data and Trigger ports. The Probe port is used for
both Data and Trigger.
IMPORTANT: The ILA v5.1 core is not compatible with the legacy ChipScope™ Pro Analyzer tool. The
ILA v5.1 core requires the Vivado logic analyzer feature for run time interaction.
Debugging
This appendix includes details about resources available on the Xilinx Support website and
debugging tools.
TIP: If the IP generation halts with an error, there might be a license issue. See License Checkers in
Chapter 1 for more details.
Documentation
This product guide is the main document associated with the ILA. This guide, along with
documentation related to all products that aid in the design process, can be found on the
Xilinx Support web page or by using the Xilinx Documentation Navigator.
Download the Xilinx Documentation Navigator from the Downloads page. For more
information about this tool and the features available, open the online help after
installation.
Answer Records
Answer Records include information about commonly encountered problems, helpful
information on how to resolve these problems, and any known issues with a Xilinx product.
Answer Records are created and maintained daily ensuring that users have access to the
most accurate information available.
Answer Records for this core can be located by using the Search Support box on the main
Xilinx support web page. To maximize your search results, use proper keywords such as:
• Product name
• Tool message(s)
• Summary of the issue encountered
A filter search is available after results are returned to further target the results.
AR: 54606
Technical Support
Xilinx provides technical support in the Xilinx Support web page for this LogiCORE™ IP
product when used as described in the product documentation. Xilinx cannot guarantee
timing, functionality, or support if you do any of the following:
• Implement the solution in devices that are not defined in the documentation.
• Customize the solution beyond that allowed in the product documentation.
• Change any section of the design labeled DO NOT MODIFY.
To contact Xilinx Technical Support, navigate to the Xilinx Support web page.
Debug Tools
There are many tools available to address ILA design issues. It is important to know which
tools are useful for debugging various situations.
The Vivado logic analyzer is used with the logic debug IP cores, including:
See the Vivado Design Suite User Guide: Programming and Debugging (UG908) [Ref 1].
For more information on the ability to interact with the ILA core using Tcl Console
commands, see Chapter 5 in the Vivado Design Suite User Guide: Programming and
Debugging (UG908) [Ref 1].
Hardware Debug
Hardware issues can range from link bring-up to problems seen after hours of testing. This
section provides debug steps for common issues. The Vivado debug feature is a valuable
resource to use in hardware debug. The signal names mentioned in the following individual
sections can be probed using the debug feature for debugging the specific issues.
General Checks
Ensure that all the timing constraints for the core were properly incorporated from the
example design and that all constraints were met during implementation. If using MMCMs
in the design, ensure that all MMCMs have obtained lock by monitoring the locked port.
Xilinx Resources
For support resources such as Answers, Documentation, Downloads, and Forums, see Xilinx
Support.
References
These documents provide supplemental material useful with this product guide:
Revision History
The following table shows the revision history for this document.