Xilinx Training
After completing this module, you will be able to:
Explain what the AXI protocol is
Identify the advantages of the AXI protocol over a shared bus model
List the various AXI-based system architectural models
APB
AMBA
AHB AXI
Performance
Is an interface and protocol definition and is not a bus standard
– Preproduction in the EDK 12.3 release
– Currently, only targets the MicroBlaze soft processor core
• Only for Spartan-6 and Virtex-6 devices
• Most EDK peripherals will support AXI with the EDK 13.1 release
Who should migrate their design?
– Anyone that believes the features are beneficial (AXI advantages are coming up)
– Anyone building an embedded design that will target the next generation of product families (after Spartan-6 and Virtex-6)
ISE Design Suite 12.3 is a pre-production release for designs that use AXI IP
– The AXI IP peripherals in this release have not yet completed qualification for use in production designs
– Some wizard functionality in Xilinx Platform Studio does not yet fully support AXI-based designs
For ISE Design Suite 12.3, pre-production status applies only to designs making use of AXI IP peripherals
– If you design does not use these peripherals then your ok
Processor
PLB
Peripherals
PLB
PLB
PLB
PLB46
Arbiter
“Shared Access” Bus
Interconnect
Implementation is not described in the spec
Several companies build and sell “AXI interconnect IP”
Xilinx is building its own
AXI Masters
AXI
AXI
AXI AXI
AXI AXI
AXI
AXI Slaves
AXI
AXI
AXI
Arrows indicate master/slave relationship, not direction of dataflow
AXI is an interface specification, not a bus specification
Master Slave
Higher performance
– AXI allows systems to be optimized for highest Fmax, maximum throughput, lower latency or some combination of those attributes. This flexibility enables you to build the most optimized products for your markets
Easier to use
– By consolidating a broad array of interfaces into AXI, you only need to know one family of interfaces, regardless of whether they are embedded,
DSP or logic users. This makes it easier to integrate IP from different domains, as well as developing your own IP
Enable ecosystem
– Partners are embracing the move to AXI: an open, widely adopted interface standard. Many of them are already creating IP targeting AXI and other AMBA® interfaces. This gives you a greater catalog of IP, ultimately leading to faster time to market
AMBA Enhancements for FPGAs
APB
Same Spec
AHB
AXI-4
Memory Map
AXI
AXI-4
Stream
ATB
AMBA 3.0
(2003)
AXI-4
Lite
AMBA 4.0
(Just Announced)
Interface
Memory Map /
Full
Streaming
Features
Traditional Address/Data Burst
(single address, multiple data)
Data-Only, Burst
Lite Traditional Address/Data —No Burst
(single address, single data)
Similar to
PLBv46, PCI
Local Link / DSP Interfaces
/ FIFO / FSL
PLBv46-single
OPB
Re-building the Embedded System is usually best
– This is NOT difficult
• Adding processors, busses, and IP is literally “drag-and-drop”
• Custom IP…has some challenges
If the IP was built with the IP Wizard, the IP can be migrated using templates provided in the following solution record
– http://www.xilinx.com/support/answers/37425.htm
If the IP cannot be altered to AXI, just add the AXI-to-PLB bridge component
– This is described in the Xilinx AXI Reference Guide
If the IP was built from scratch, refer to the “Memory Mapped IP
Feature Adoption and Support,” in the Xilinx AXI Reference
Guide
Xilinx AXI Reference Guide, UG761
– AXI Usage in Xilinx FPGAs
• Introduce key concepts of the AXI protocol
• Explains what features of AXI Xilinx has adopted
– PLB-to-AXI Migration Guide
• Handbook for existing embedded customers
– How to create and import AXI IP
– How to debug and verify designs using ChipScope
– How to convert PLB-based IP to AXI
ARM specifications
– AMBA AXI Protocol Version 2.0
– AMBA 4 AXI4-Stream Protocol Version 1.0
– http://infocenter.arm.com/help/topic/com.arm.doc.set.amba
AXI is a signal interface protocol, not a shared bus standard
AXI offers higher performance, ease of use, and has the support of many partners
The AXI protocol has three different configurations
– Memory Map/Full for OPBv46 replacement
– Streaming for data streaming applications
– Lite for simpler systems
The Xilinx AXI Reference Guide, UG761 contains more details about the AXI protocol and explains how to migrate IP to AXI
www.xilinx.com/training
– Embedded Systems Development course
• EDK tool training
• How to build custom IP
• How to build your system software
– Advanced Features and Techniques of Embedded Systems Design course
• How to debug your software on your hardware system with ChipScope
• How to optimize the use of the available memory controllers
• How to design a Flash memory-based system and boot load from an off-chip memory
• How to add an interrupt controller into your hardware and software system
– Embedded Systems Software Development course
• Software development and debugging with SDK
• How to profile your software and develop custom device drivers
Xilinx is disclosing this Document and Intellectual Property
(hereinafter “the Design”) to you for use in the development of designs to operate on, or interface with Xilinx FPGAs. Except as stated herein, none of the Design may be copied, reproduced, distributed, republished, downloaded, displayed, posted, or transmitted in any form or by any means including, but not limited to, electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of Xilinx. Any unauthorized use of the Design may violate copyright laws, trademark laws, the laws of privacy and publicity, and communications regulations and statutes.
Xilinx does not assume any liability arising out of the application or use of the Design; nor does Xilinx convey any license under its patents, copyrights, or any rights of others. You are responsible for obtaining any rights you may require for your use or implementation of the Design.
Xilinx reserves the right to make changes, at any time, to the Design as deemed desirable in the sole discretion of Xilinx. Xilinx assumes no obligation to correct any errors contained herein or to advise you of any correction if such be made. Xilinx will not assume any liability for the accuracy or correctness of any engineering or technical support or assistance provided to you in connection with the Design.
THE DESIGN IS PROVIDED “AS IS" WITH ALL FAULTS, AND THE ENTIRE RISK AS TO ITS FUNCTION AND IMPLEMENTATION IS WITH
YOU. YOU ACKNOWLEDGE AND AGREE THAT YOU HAVE NOT RELIED ON ANY ORAL OR WRITTEN INFORMATION OR ADVICE,
WHETHER GIVEN BY XILINX, OR ITS AGENTS OR EMPLOYEES. XILINX MAKES NO OTHER WARRANTIES, WHETHER EXPRESS,
IMPLIED, OR STATUTORY, REGARDING THE DESIGN, INCLUDING ANY WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, TITLE, AND NONINFRINGEMENT OF THIRD-PARTY RIGHTS.
IN NO EVENT WILL XILINX BE LIABLE FOR ANY CONSEQUENTIAL, INDIRECT, EXEMPLARY, SPECIAL, OR INCIDENTAL DAMAGES,
INCLUDING ANY LOST DATA AND LOST PROFITS, ARISING FROM OR RELATING TO YOUR USE OF THE DESIGN, EVEN IF YOU HAVE
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE TOTAL CUMULATIVE LIABILITY OF XILINX IN CONNECTION WITH
YOUR USE OF THE DESIGN, WHETHER IN CONTRACT OR TORT OR OTHERWISE, WILL IN NO EVENT EXCEED THE AMOUNT OF
FEES PAID BY YOU TO XILINX HEREUNDER FOR USE OF THE DESIGN. YOU ACKNOWLEDGE THAT THE FEES, IF ANY, REFLECT
THE ALLOCATION OF RISK SET FORTH IN THIS AGREEMENT AND THAT XILINX WOULD NOT MAKE AVAILABLE THE DESIGN TO YOU
WITHOUT THESE LIMITATIONS OF LIABILITY.
The Design is not designed or intended for use in the development of on-line control equipment in hazardous environments requiring fail-safe controls, such as in the operation of nuclear facilities, aircraft navigation or communications systems, air traffic control, life support, or weapons systems (“High-Risk Applications”). Xilinx specifically disclaims any express or implied warranties of fitness for such High-Risk Applications. You represent that use of the Design in such High-Risk Applications is fully at your risk.
© 2012 Xilinx, Inc. All rights reserved. XILINX, the Xilinx logo, and other designated brands included herein are trademarks of Xilinx, Inc. All other trademarks are the property of their respective owners.