Logicore Ip Axi Master Lite v3.0: Product Guide For Vivado Design Suite
Logicore Ip Axi Master Lite v3.0: Product Guide For Vivado Design Suite
Logicore Ip Axi Master Lite v3.0: Product Guide For Vivado Design Suite
Chapter 1: Overview
Feature Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Unsupported Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Licensing and Ordering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Chapter 2: Product Specification
Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Performance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Resource Utilization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Port Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Chapter 3: Designing with the Core
General Design Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Clocking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Protocol Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Chapter 5: Constraining the Core
Chapter 6: Simulation
Chapter 7: Synthesis and Implementation
Chapter 8: Example Design
Chapter 9: Test Bench
Appendix A: Debugging
Finding Help on Xilinx.com . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Debug Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Interface Debug . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Appendix B: Additional Resources
Xilinx Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Notice of Disclaimer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Introduction LogiCORE IP Facts Table
Core Specifics
The AXI Master Lite is an AXI4-compatible Supported
Zynq®-7000, 7 Series, UltraScale™ Architecture
LogiCORE™ IP product. It provides an interface Device Family (1)
between a user-created IP core and an Supported User
AXI4-Lite
AXI4-Lite interface. The AXI4-Lite Master IP Interfaces
Support
Provided by Xilinx @ www.xilinx.com/support
Notes:
1. For a complete list of supported devices, see Vivado IP
catalog.
2. For the supported versions of the tools, see the Xilinx Design
Tools: Release Notes Guide.
Chapter 1
Overview
The LogiCORE™ IP AXI Master Lite core provides an interface between a user-created IP
core and an AXI4-Lite interface. The AXI4-Lite Master IP supports AXI4-Lite compatible bus
mastering operations, which are single 32-bit wide read or write data transfers.
Feature Summary
• AXI4-Lite Master interface
• Fixed 32-bit data width
• Supports single beat read and write data transfers of up to 4 bytes (32 bits)
Applications
The AXI Master Lite core provides a AXI4-Lite mastering capability that has the legacy IP
Interconnect (IPIC) User interface suitable for updating to AXI4 those legacy plbv46 designs
that used the plbv46_master_single module.
The backend IPIC interface connects directly to the legacy User IPIC interface of the
plbv46_master_single without modification. However, the plbv46 signal set has been
replaced with AXI4-Lite master signal set. To migrate from a plbv46_master_single core:
• HDL changes:
Unsupported Features
• Protection unit support is limited. AxPROT signals are ignored.
• Low-power interface is not implemented.
• AXI data bus and address bus widths are fixed to 32 bits.
• The AXI Lite Intellectual Property Interface (IPIF) does not do endian conversion. Both
AXI and IPIC are little endian.
Licensing and Ordering Information
This Xilinx LogiCORE IP module is provided at no additional cost with the Xilinx Vivado
Design Suite under the terms of the Xilinx End User License.
Information about this and other Xilinx LogiCORE IP modules is available at the Xilinx
Intellectual Property page. For information on pricing and availability of other Xilinx
LogiCORE IP modules and tools, contact your local Xilinx sales representative.
Product Specification
The LogiCORE™ IP AXI Master Lite core provides a quick way to implement a light-weight
mastering interface between user logic and an AXI4-Lite interface. Figure 2-1 is a block
diagram of the AXI Master Lite core. The port references and groupings are detailed in
Table 2-3. The design is natively 32 bits and supports read and write transfers of 1 to 4
bytes. Transfer request protocol between the AXI4 and the User Logic is provided by the
Read and Write Controller block.
X-Ref Target - Figure 2-1
$;,0DVWHU/LWH 8VHU,3
'HVLJQ
D[LBDFON ,3,&
D[LBDUHVHWQ
5G:U5HT 4XDOLILHUV
6WDWXV5HSO\
$;,/LWH0DVWHU5HDG$GGUHVV&KDQQHO
$;,%XV
$;,/LWH0DVWHU:ULWH5HVSRQVH&KDQQHO
;
Figure 2‐1: AXI Master Lite Block Diagram
Typical System Interconnect
A typical use case of the AXI Master Lite core is shown in Figure 2-2. The AXI Interconnect
Block allows the user IP core to access AXI4 slaves (AXI4 and AXI4-Lite) via the AXI4-Lite
interface.
$;,/LWH $;,/LWH
6ODYH
8VHU,3&RUH
$;,/LWH $;,/LWH
6ODYH
$;, 0DVWHU,3,&
$;,/LWH 0DVWHU
$;,00DS /LWH
,QWHUFRQQHFW
$;,/LWH
$;,/LWH 8VHU/RJLF
$;,/LWH
6ODYH
$;,/LWH $;,/LWH
6ODYH
;
Figure 2‐2: AXI Interconnect Block (AXI_Interconnect)
Standards
The AXI interfaces conform to the Advanced Microcontroller Bus Architecture (AMBA®) AXI
version 4 specification from Advanced RISC Machine (ARM®), including the AXI4-Lite
control register interface subset. See ARM AMBA AXI Protocol v2.0 [Ref 6].
Performance
This section provides performance information for the AXI Master Lite core.
Maximum Frequencies
Table 2-1 shows the targeted design clock frequencies of the AXI Master Lite core.
Table 2‐1: Targeted Frequencies
Family Fmax (Mhz)
Virtex-7 180
Kintex-7 150
Artix-7 120
Values for the Zynq® family of devices with a Kintex® or Artix® base are expected to be
similar. The maximum achievable clock frequency and resource utilization estimates may be
different from those shown due to tool options, FPGA speed and logic utilization, and other
factors.
Throughput
No information is currently provided for this core.
Power
No information is currently provided for this core.
Resource Utilization
Because the AXI4-Lite Master interface is used with other design modules in the devices,
the utilization and timing numbers reported in this section are estimates. Because the
AXI4-Lite Master interface is combined with other design elements, resource utilization and
timing may vary from the results reported here.
The resource utilization of this version of the AXI Master Lite core is shown here for example
configurations. The slave attachment was synthesized using Vivado® synthesis. The
resource utilization report was then used as the source data for the table.
Resource utilization numbers for the AXI Master Lite core are shown for the 7 series FPGA
families in Table 2-2. These values were generated using the Xilinx Vivado Suite. The Zynq
family of devices with a Kintex or Artix base are expected to have similar utilization results
for the same configurations. UltraScale architecture results are expected to be similar to 7
series device results.
Table 2‐2: FPGA Resource Estimates
Family C_M_AXI_DATA_WIDTH C_M_AXI_ADDR_WIDTH Slice Reg LUTs
Virtex-7 32 32 123 27
Kintex-7 32 32 123 27
Artix-7 32 32 123 27
Port Descriptions
This section provides port information for the AXI Master Lite core.
I/O Signals
The AXI Master Lite signals are described in Table 2-3.
Table 2‐3: AXI Master Lite I/O Signal Description
Signal Init
Signal Name Interface Type Status Description
System Signals
m_axi_lite_aclk Clock I AXI Master Lite synchronization clock.
AXI Master Lite Reset. When asserted low, the AXI
m_axi_lite_aresetn Reset I Master Lite core is put into hard reset. This signal
must be synchronous to m_axi_aclk.
Master Detected Error Discrete
Master Detected Error. Active high master detected
md_error Discrete Out O error output discrete. This bit is sticky when set and
is only cleared by a hardware reset.
AXI4‐Lite Master Read Address Channel
m_axi_lite_araddr AXI Master Lite Read Address Channel Address Bus.
(C_M_AXI_LITE_ADDR_ M_AXI_LITE O zeros
width-1: 0)
AXI Master Lite Read Address Channel Protection.
m_axi_lite_arprot(2:0) M_AXI_LITE O 000b This is always driven with a constant output of
000b.
AXI Master Lite Read Address Channel Read
Address Valid. Indicates if m_axi_lite_araddr is
m_axi_lite_arvalid M_AXI_LITE O 0 valid.
• 1 = Read Address is valid.
• 0 = Read Address is not valid.
Table 2‐3: AXI Master Lite I/O Signal Description (Cont’d)
Table 2‐3: AXI Master Lite I/O Signal Description (Cont’d)
Table 2‐3: AXI Master Lite I/O Signal Description (Cont’d)
Designing with the Core
This chapter includes guidelines and additional information to facilitate designing with the
core.
General Design Guidelines
The AXI Master Lite design parameters are described in Table 3-1.
Table 3‐1: AXI Master Lite Design Parameters
Allowable Default
Feature/Description Parameter Name VHDL Type
Values Values
AXI Master Lite AXI4‐Lite Parameters
Address width (in bits) of AXI4-Lite C_M_AXI_LITE_ADDR_WIDTH
Interface. This is currently fixed at 32 32 integer
32 bits.
Data width (in bits) of AXI4-Lite C_M_AXI_LITE_DATA_WIDTH
Interface. This is currently fixed at 32 32 integer
32 bits.
Table 3‐2: Parameter ‐ I/O Signal Dependencies
Table 3‐3: Parameter Descriptions
Allowed
Parameter Name Type Definition Description
Values
C_M_AXI_LITE_ Integer 32 (default) Address bus width Used to size the Read Address and Write
ADDR_WIDTH of attached AXI on Address Channels of the AXI Master Lite
the AXI AXI Master AXI4 Interface. The EDK tool suite
Lite interface assigns this parameter a fixed value of
32.
C_M_AXI_LITE_ Integer 32 (default) Read Data bus width Used to size the Read Data and Write
DATA_WIDTH of attached AXI4 on Data Channels of the AXI Master Lite
the AXI Master Lite interface. The EDK tool suite assigns this
interface parameter a fixed value of 32.
Clocking
The AXI Master Lite core uses a single clock for logic synchronization. This clock is input on
the m_axi_lite_aclk input port. All interfaces for the core are required to be
synchronized to this clock. The AXI Master Lite core has been simulation tested with an
m_axi_lite_aclk frequency range of 10 MHz to 200 MHz. Actual Fmax achieved in a
hardware implementation may vary.
Resets
An active low reset assertion on the AXI Master Lite m_axi_lite_aresetn input resets
the entire AXI Master Lite core. This is considered a hardware reset, and there are no
graceful completions of AXI4 transfers in progress. A hardware reset initializes all AXI
Master Lite internal logic to power-on conditions. It is required that the
m_axi_lite_aresetn input is synchronous to the m_axi_lite_aclk master clock
input and is asserted for the minimum number of clocks stated in Table 3-4. Table 3-4 also
indicates the stabilization time for AXI Master Lite outputs reacting to a reset condition.
Table 3‐4: Reset Assertion/Deassertion Stabilization Times
Description Value Applicable Signal
Minimum assertion time 8 clocks axi_resetn input
(m_axi_lite_aclk)
Reset assertion to output signals in reset state 3 clocks All output signals
(maximum) (m_axi_lite_aclk)
Reset deassertion to normal operation state 3 clocks All output signals
(maximum) (m_axi_lite_aclk)
Protocol Description
No information is currently provided for this core.
Transaction Timing Examples
This section shows timing relationships for AXI4-Lite and the IPIC interface signals during
read and write transfers. Only single data beat transfers of 1 to 4 bytes are supported by the
AXI Master Lite core.
Single Data Beat Read Operation
Two single beat read cycles are shown in Figure 3-1. The first cycle shows the AXI Slave
accepting the read address and qualifiers in one clock cycle and presenting the read data in
the next clock cycle. The second read transfer indicates a delayed address acceptance
sequence and a delayed read data valid by the AXI Slave device.
PBD[LBOLWHBDFON
PBD[LBOLWHBDUHVHWQ
PBD[LBOLWHBDUYDOLG
PBD[LBOLWHBDUUHDG\
PBD[LBOLWHBDUSURW>@
PBD[LBOLWHBUYDOLG
PBD[LBOLWHBUUHDG\
PBD[LBOLWHBUUHVS>@
PBD[LBOLWHBDZYDOLG
PBD[LBOLWHBDZUHDG\
PBD[LBOLWHBDZSURW>@
PBD[LBOLWHBZYDOLG
PBD[LBOLWHBZUHDG\
PBD[LBOLWHBZVWUE>@
PBD[LBOLWHBZGDWD>@
PBD[LBOLWHBEUHVS>@
PBD[LBOLWHBEUHDG\
PBD[LBOLWHBEYDOLG
,3%XVB0VW5GB5HT
,3%XVB0VW:UB5HT
,3%XVB0VWB%(
,3%XVB0VWB/RFN
,3%XVB0VWB5HVHW
%XV,3B0VWB&PG$FN
%XV,3B0VWB&PSOW
%XV,3B0VWB(UURU
%XV,3B0VWB5HDUELWUDWH
%XV,3B0VWB&PGB7LPHRXW
%XV,3B0VW5GBVUFBUG\BQ
,3%XVB0VW:UBG
%XV,3B0VW:UBGVWBUG\BQ
;
Figure 3‐1: Example Read Transfer Timing
Single Data Beat Write Operation
Two single beat write cycles are shown in Figure 3-2. The first cycle shows the AXI Slave
accepting the address and data in one clock cycle followed by a one clock later write
response. The second write transfer shows a delayed address acceptance, a delayed write
data acceptance, and a delayed write response by the AXI Slave device.
S
X-Ref Target - Figure 3-2
PBD[LBOLWHBDFON
PBD[LBOLWHBDUHVHWQ
PBD[LBOLWHBDUYDOLG
PBD[LBOLWHBDUUHDG\
PBD[LBOLWHBDUSURW>@
PBD[LBOLWHBUYDOLG
PBD[LBOLWHBUUHDG\
PBD[LBOLWHBUUHVS>@
PBD[LBOLWHBUGDWD>@
PBD[LBOLWHBDZYDOLG
PBD[LBOLWHBDZUHDG\
PBD[LBOLWHBDZSURW>@
PBD[LBOLWHBZYDOLG
PBD[LBOLWHBZUHDG\
PBD[LBOLWHBZVWUE>@ &
PBD[LBOLWHBEUHVS>@
PBD[LBOLWHBEUHDG\
PBD[LBOLWHBEYDOLG
,3%XVB0VW5GB5HT
,3%XVB0VW:UB5HT
,3%XVB0VWB$GGU
,3%XVB0VWB%( &
,3%XVB0VWB/RFN
,3%XVB0VWB5HVHW
%XV,3B0VWB&PG$FN
%XV,3B0VWB&PSOW
%XV,3B0VWB(UURU
%XV,3B0VWB5HDUELWUDWH
%XV,3B0VWB&PGB7LPHRXW
%XV,3B0VW5GBG>@
%XV,3B0VW5GBVUFBUG\BQ
%XV,3B0VW:UBGVWBUG\BQ
;
Figure 3‐2: Example Write Transfer Timing
Single Data Beat Read Operation with Error
Single data beat Read transfers with a Slave reported error is shown in Figure 3-3. A Slave
data channel response error is reported, and the Master’s md_error output is asserted and
held. The assertion of md_error is cleared by the input from the AXI4 interface. The
IP2Bus_Mst_Reset can also used to clear the md_error if desired.
S
X-Ref Target - Figure 3-3
PBD[LBOLWHBDFON
PBD[LBOLWHBDUHVHWQ
PGBHUURU
PBD[LBOLWHBDUYDOLG
PBD[LBOLWHBDUUHDG\
PBD[LBOLWHBDUSURW>@
PBD[LBOLWHBDUDGGU>@
PBD[LBOLWHBUYDOLG
PBD[LBOLWHBUUHDG\
PBD[LBOLWHBUUHVS>@
PBD[LBOLWHBUGDWD>@
PBD[LBOLWHBDZYDOLG
PBD[LBOLWHBDZUHDG\
PBD[LBOLWHBDZSURW>@
PBD[LBOLWHBDZDGGU>@
PBD[LBOLWHBZYDOLG
PBD[LBOLWHBZUHDG\
PBD[LBOLWHBZVWUE>@
PBD[LBOLWHBZGDWD>@
PBD[LBOLWHBEUHVS>@
PBD[LBOLWHBEUHDG\
PBD[LBOLWHBEYDOLG
,3%XVB0VW5GB5HT
,3%XVB0VW:UB5HT
,3%XVB0VWB$GGU
,3%XVB0VWB%(
,3%XVB0VWB/RFN
,3%XVB0VWB5HVHW
%XV,3B0VWB&PG$FN
%XV,3B0VWB&PSOW
%XV,3B0VWB(UURU
%XV,3B0VWB5HDUELWUDWH
%XV,3B0VWB&PGB7LPHRXW
%XV,3B0VW5GBG>@
%XV,3B0VW5GBVUFBUG\BQ
,3%XVB0VW:UBG
%XV,3B0VW:UBGVWBUG\BQ
;
Figure 3‐3: Example Read Transfer Timing with Error
Single Data Beat Write Operation with Error
Two single beat write cycles are shown in Figure 3-4. For both transfers, a Slave data error
is reported and the Master’s md_error output is asserted and held. The assertion of
md_error is cleared by the input from the AXI4-Lite interface. The IP2Bus_Mst_Reset
can also used to clear the md_error if desired.
X-Ref Target - Figure 3-4
PBD[LBOLWHBDFON
PBD[LBOLWHBDUHVHWQ
PGBHUURU
PBD[LBOLWHBDUYDOLG
PBD[LBOLWHBDUUHDG\
PBD[LBOLWHBDUSURW>@
PBD[LBOLWHBDUDGGU>@
PBD[LBOLWHBUYDOLG
PBD[LBOLWHBUUHDG\
PBD[LBOLWHBUUHVS>@
PBD[LBOLWHBUGDWD>@
PBD[LBOLWHBDZYDOLG
PBD[LBOLWHBDZUHDG\
PBD[LBOLWHBDZSURW>@
PBD[LBOLWHBDZDGGU>@
PBD[LBOLWHBZYDOLG
PBD[LBOLWHBZUHDG\
PBD[LBOLWHBZVWUE>@ &
PBD[LBOLWHBZGDWD>@
PBD[LBOLWHBEUHVS>@
PBD[LBOLWHBEUHDG\
PBD[LBOLWHBEYDOLG
,3%XVB0VW5GB5HT
,3%XVB0VW:UB5HT
,3%XVB0VWB$GGU
,3%XVB0VWB%( &
,3%XVB0VWB/RFN
,3%XVB0VWB5HVHW
%XV,3B0VWB&PG$FN
%XV,3B0VWB&PSOW
%XV,3B0VWB(UURU
%XV,3B0VWB5HDUELWUDWH
%XV,3B0VWB&PGB7LPHRXW
%XV,3B0VW5GBG>@
%XV,3B0VW5GBVUFBUG\BQ
,3%XVB0VW:UBG
%XV,3B0VW:UBGVWBUG\BQ
;
Figure 3‐4: Example Write Transfer Timing with Error
Customizing and Generating the Core
AXI Master Lite is a helper core, so no specific core graphical user interface is available. The
core needs to be instantiated in the user design and package through Vivado ® IP Packager.
The interface is available for the user design, which can optionally include parameters for
configuring the AXI Master Lite core.
Constraining the Core
No constraints are available for this core. When the AXI Master Lite core is instantiated in a
user design, the modified design can accommodate any user-provided constraints.
Simulation
For comprehensive information about Vivado® simulation components, as well as
information about using supported third-party tools, see the Vivado Design Suite User
Guide: Logic Simulation (UG900) [Ref 2].
Synthesis and Implementation
For details about synthesis and implementation, see “Synthesizing IP” and “Implementing
IP” in the Vivado Design Suite User Guide: Designing with IP (UG896) [Ref 5].
Example Design
No example design is provided with this core.
Test Bench
No test bench is provided with this core.
Debugging
This appendix includes details about resources available on the Xilinx Support website and
debugging tools.
Finding Help on Xilinx.com
To help in the design and debug process when using the AXI Master Lite core, the Xilinx
Support web page (www.xilinx.com/support) contains key resources such as product
documentation, release notes, answer records, information about known issues, and links
for opening a Technical Support WebCase.
Documentation
This product guide is the main document associated with the AXI Master Lite core. This
guide, along with documentation related to all products that aid in the design process, can
be found on the Xilinx Support web page (www.xilinx.com/support) or by using the Xilinx
Documentation Navigator.
Download the Xilinx Documentation Navigator from the Design Tools tab on the Downloads
page (www.xilinx.com/download). For more information about this tool and the features
available, open the online help after installation.
Solution Centers
See the Xilinx Solution Centers for support on devices, software tools, and intellectual
property at all stages of the design cycle. Topics include design assistance, advisories, and
troubleshooting tips.
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 also 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 messages
• Summary of the issue encountered
A filter search is available after results are returned to further target the results.
AR 55014
Contacting Technical Support
Xilinx provides technical support at www.xilinx.com/support for this LogiCORE™ IP product
when used as described in the product documentation. Xilinx cannot guarantee timing,
functionality, or support of product if implemented in devices that are not defined in the
documentation, if customized beyond that allowed in the product documentation, or if
changes are made to any section of the design labeled DO NOT MODIFY.
1. Navigate to www.xilinx.com/support.
2. Open a WebCase by selecting the WebCase link located under Support Quick Links.
Debug Tools
There are many tools available to address AXI Master Lite design issues. It is important to
know which tools are useful for debugging various situations.
Vivado Lab Tools
Vivado® inserts logic analyzer and virtual I/O cores directly into your design. Vivado Lab
Tools allows you to set trigger conditions to capture application and integrated block port
signals in hardware. Captured signals can then be analyzed. This feature represents the
functionality in the Vivado IDE that is used for logic debugging and validation of a design
running in Xilinx FPGA devices in hardware.
The Vivado logic analyzer is used to interact with the logic debug LogiCORE IP cores,
including:
Interface Debug
The AXI Master Lite core is a helper core and should be instantiated in another AXI master
core that is part of the system. The interface of the parent core should have additional
information about interface debug.
Note: The Master AXI interface address, data, and response channels should be monitored while
debugging the scenarios.
AXI4‐Lite Interfaces
Initiate a read transaction towards targeted slave registers. To check if the interface is
functional, monitor the m_axi_lite_arvalid, m_axi_lite_araddr[31:0], and
m_axi_lite_rready signals. The slave should respond with valid
m_axi_lite_arready, m_axi_lite_rvalid, m_axi_lite_rresp[1:0], and
m_axi_lite_rdata[31:0] signals. The assertion of these signals indicates that the read
transaction from the master is completed. If the interface is unresponsive, ensure that the
following conditions are met:
Additional Resources
Xilinx Resources
For support resources such as Answers, Documentation, Downloads, and Forums, see the
Xilinx Support website at:
www.xilinx.com/support.
www.xilinx.com/company/terms.htm.
References
These documents provide supplemental material useful with this product guide:
Revision History
The following table shows the revision history for this document.
Notice of Disclaimer
The information disclosed to you hereunder (the “Materials”) is provided solely for the selection and use of Xilinx products. To the
maximum extent permitted by applicable law: (1) Materials are made available “AS IS” and with all faults, Xilinx hereby DISCLAIMS
ALL WARRANTIES AND CONDITIONS, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING BUT NOT LIMITED TO WARRANTIES OF
MERCHANTABILITY, NON-INFRINGEMENT, OR FITNESS FOR ANY PARTICULAR PURPOSE; and (2) Xilinx shall not be liable (whether
in contract or tort, including negligence, or under any other theory of liability) for any loss or damage of any kind or nature related
to, arising under, or in connection with, the Materials (including your use of the Materials), including for any direct, indirect,
special, incidental, or consequential loss or damage (including loss of data, profits, goodwill, or any type of loss or damage
suffered as a result of any action brought by a third party) even if such damage or loss was reasonably foreseeable or Xilinx had
been advised of the possibility of the same. Xilinx assumes no obligation to correct any errors contained in the Materials or to
notify you of updates to the Materials or to product specifications. You may not reproduce, modify, distribute, or publicly display
the Materials without prior written consent. Certain products are subject to the terms and conditions of the Limited Warranties
which can be viewed at http://www.xilinx.com/warranty.htm; IP cores may be subject to warranty and support terms contained in
a license issued to you by Xilinx. Xilinx products are not designed or intended to be fail-safe or for use in any application requiring
fail-safe performance; you assume sole risk and liability for use of Xilinx products in Critical Applications: http://www.xilinx.com/
warranty.htm#critapps.
© Copyright 2013 Xilinx, Inc. Xilinx, the Xilinx logo, Artix, ISE, Kintex, Spartan, Virtex, Vivado, Zynq, and other designated brands
included herein are trademarks of Xilinx in the United States and other countries. All other trademarks are the property of their
respective owners.