|
所在平台: Udemy |
课程主页: https://www.udemy.com/course/axi4-implementations-in-fpga-designs/
课程评论：没有评论
**课程名称：FPGA设计中的AXI4实现** **课程概述：** 本课程提供了AXI4总线协议全方位的指导，涵盖AXI4 Stream、AXI4-Lite和AXI4。每种AXI4协议都有详细介绍其总线流程、握手和信号要求。课程包含AXI4各子集主端和从端的示例实现，并通过edaplayground和Vivado中的示例测试平台进行仿真演示。同时，利用Vivado块设计和AXI4协议检查工具进行验证。 **学习要点：** * **AXI4协议家族的差异：** 深入理解AXI4 Stream、AXI4-Lite和AXI4之间的区别。 * **AXI4 Stream：** 学习AXI4 Stream协议，该协议用于主机到从机之间无地址信息的单向批量数据传输，是三种协议中最易于实现且最常用的。 * **AXI4-Lite：** 学习AXI4-Lite协议的实现，了解AXI4-Lite主机与从机之间同时带有地址和数据的握手过程，支持单字读写，并包含从机对有效或错误事务的响应。 * **AXI4（全功能）：** 掌握AXI4协议的实现，该协议提供最高的**数据带宽**，支持高达256个128字节大小的突发模式。理解其包含独立的地址写总线、数据写总线、地址读总线、读总线和写响应总线，每条总线都有单独的握手机制，成功实现RTL组件需要全面的理解。 **目标学员：** 本课程适合需要深入了解和实践AXI4总线协议的FPGA设计工程师。
A full instructional series for all aspect of the AXI4 Bus protocol, including AXI4 Stream, AXI4-Lite, and AXI4. Each flavor of AXI4 has a bus flow, handshake, and signal requirements described in detail. An example implementation for a Master and Slave in each of the subsets of AXI4 are included, with simulation demonstrations using example testbenches in edaplayground, and vivado, included using the vivado block diagram with AXI4 Protocol checking.We learn the differences between each of the AXI4 flavors, where the AXI4 Stream protocol is used for uni-directional bulk data transfers from a master to a slave without addressing information. The AXI4 Stream protocol is the easiest to implement and the most common. The AXI4-Lite protocol is the other common interface that we learn how to implement. We get a full understanding of how the AXI4-Lite Master handshakes with the AXI4-Lite Slave with both address and data, and allows single word writes and reads, with slave responses on valid or error transactions. The full AXI4 protocol provides the highest data bandwith with burst modes up to 256 words of size 128 bytes. With 5 separate busses, including an Address Write Bus, a Data Write bus, an Address Read Bus, a Read Bus, and a Write Reponse bus, each with separate handshaking, there is an extensive understanding required to implement the RTL components successfully.
