Presentation is loading. Please wait.

Presentation is loading. Please wait.

How to Convert a PLB-based Embedded System to an AXI-based System

Similar presentations

Presentation on theme: "How to Convert a PLB-based Embedded System to an AXI-based System"— Presentation transcript:

1 How to Convert a PLB-based Embedded System to an AXI-based System
Xilinx Training

2 Objectives 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

Advanced Microcontroller Bus Architecture AMBA APB AHB AXI AXI is a product of ARM, a company that designs and markets processor and peripheral IP to silicon vendors. Over the years, ARM has introduced various releases of its AMBA protocol interface to describe interconnect between the processor core and peripherals. For the most part, this protocol has been abstracted away from the user, as it has been buried in the single chip micro silicon that designers did not have, or need, access to. Now, the FPGA enables peripheral designers to build with this interface standard. Performance

4 The ARM AXI 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) Most embedded interconnect protocols define the implementation of the interconnect between the processor sub-system components. In AXI, only the signal names and operational protocol is defined. How the interconnect works is defined and optimized by the EDK software. This saves users from having to understand the details of the protocol.

5 Pre-Production AXI 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

6 AXI is an Interface Specification
PLB46 “Shared Access” Bus Processor Interconnect PLB AXI Slaves AXI Masters AXI AXI AXI AXI Peripherals AXI Interconnect IP Implementation is not described in the spec Several companies build and sell “AXI interconnect IP” Xilinx is building its own PLB Because AXI does not define the interconnect, it is possible that the interconnect could be specified as a shared bus. In such a case, AXI and PLBv46 implementations would share some common operational properties. AXI AXI AXI AXI PLB AXI AXI PLB Arrows indicate master/slave relationship, not direction of dataflow Master Slave AXI is an interface specification, not a bus specification Arbiter

7 Why use AXI? Higher performance Easier to use Enable ecosystem
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 One of the goals of the Xilinx implementation of AXI is a unified interface protocol of Xilinx components. There will be a migration towards AXI in all facets of Xilinx technology and components. This will allow you the flexibility to rapidly define and interconnect standard and custom components, thus reducing the learning curve to use various technologies.

8 Enhancements for FPGAs
AXI is Part of AMBA AMBA APB AHB AXI AXI-4 Memory Map Stream Lite ATB AMBA 3.0 (2003) AMBA 4.0 (Just Announced) Same Spec Enhancements for FPGAs AMBA = Advanced Microcontroller Bus Architecture Recently ARM announced the AXI4 spec. It is similar to AXI with three sub-interfaces to better target system specifications for performance and fabric usage. Memory Map: The traditional AXI3 address/data/control line interface with improvements such as larger data burst length phase. Stream: Targeting streaming applications to the same address. The transaction address phase has been removed. The focus is on high-performance data streaming. Lite: A simple interface, reducing fabric requirements, targeting peripherals in address space that only require a single data phase. Interface Features Similar to Memory Map / Full Traditional Address/Data Burst (single address, multiple data) PLBv46, PCI Streaming Data-Only, Burst Local Link / DSP Interfaces / FIFO / FSL Lite Traditional Address/Data—No Burst (single address, single data) PLBv46-single OPB

9 Design Conversion 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 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 New IP should be built to the AXI protocol.

10 Documentation Xilinx AXI Reference Guide, UG761 ARM specifications
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

11 Summary 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

12 Where Can I Learn More? Xilinx Education Services courses 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

13 Trademark Information
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.

Download ppt "How to Convert a PLB-based Embedded System to an AXI-based System"

Similar presentations

Ads by Google