Vivado使用系列:IP Integrator HDL

2023-10-31 18:30

本文主要是介绍Vivado使用系列:IP Integrator HDL,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

测试平台Vivado 2017.2

在Vivado的Block设计里,全IP化逐渐形成了一种新型的设计方案,受Vivado内的IP可配置的GUI界面影响,使用IP要比RTL代码更有良好的用户体验;然而,在Block设计里,并不是只有IP这一种可添加并可配置,RTL也可实现上述功能,只需要在Block内右键Add Module..,会弹出下面界面:

选择我之前写的模块add,点击ok,

这样就添加了一个add的RTL Module到Block Design内了。默认Vivado左边是输入端口,右边是输出端口。

上面是一个很简单的操作,接下来进入正题,讲解如何利用IP Integrator HDL语言使我们的RTL Module在Block内更像一个IP,IP Integrator HDL语言支持Verilog、VHDL,这里只用Verilog进行演示。

先看一下Xilinx提供的IP Integrator HDL的Language Templates:

分析一下结构,得出以下几点结论:

1.每个端口定义都是以(*起始,并以*)结束,并写在端口定义之前;

2.每个端口定义结构满足 X_INTERFACE_INFO = "{存在的接口类型} {接口的名字} 接口内的端口(必须与接口类型定义的端口一致)"

3.除了端口定义,还有Parameter定义,以X_INTERFACE_PARAMETER = "开始,内部采用键值对,即Param = value型结构;

下面是vivado内的原话:

//

// Verilog attributes are used to declare signal interfaces and set parameters on them.

// Due to the language, the attributes need to be placed before a port which is part of the interface.

// When adding one or more parameters for an interface, a single attribute with multiple

// key value pairs should be added to before of the ports that is mapped into the interface.

// Generally, the form of the attributes are:

// (* X_INTERFACE_INFO = "<interface vlnv> <interface_name> <logical_port_name>" *)

// (* X_INTERFACE_PARAMETER = "<parameter_name1> <parameter_value1>, <parameter_name2> <parameter_value2>" *)

// input <portname>;

接下来以一个AXI4_controller模块做例子演示一下。

首先按上述步骤添加一个AXI4_controller模块到Block内:

 

module axi4_controller_top #(parameter DATA_WIDTH = 'h100, parameter ADDR_WIDTH = 'h20, parameter LENGTH_WIDTH = 'h8,parameter ID_WIDTH = 'h2,parameter MASTER_ID = 'h1,parameter CLK_FREQ = 'hc8,parameter BASE_ADDR = 'h000000
)(
//
//Other Port
//input s_axil_aclk0,input s_axil_aresetn0,input [31:0] s_axil_awaddr0,input s_axil_awvalid0,output s_axil_awready0,input [31:0] s_axil_wdata0,input [3:0] s_axil_wstrb0,input s_axil_wvalid0,output s_axil_wready0,output [1:0] s_axil_bresp0,output s_axil_bvalid0,input s_axil_bready0,input [31:0] s_axil_araddr0,input s_axil_arvalid0,output s_axil_arready0,output [31:0] s_axil_rdata0,output [1:0] s_axil_rresp0,output s_axil_rvalid0,input s_axil_rready0,// AXI4_masteroutput m_axi_aclk0,output m_axi_aresetn0,output [AXI4_ID_WIDTH-1:0] m_axi_awid0,output [AXI4_ADDR_WIDTH-1:0] m_axi_awaddr0,output [AXI4_LENGTH_WIDTH-1:0] m_axi_awlen0,output [2:0] m_axi_awsize0,output [1:0] m_axi_awburst0,output [3:0] m_axi_awcache0,output [2:0] m_axi_awprot0,output m_axi_awvalid0,input m_axi_awready0,output [AXI4_DATA_WIDTH-1:0] m_axi_wdata0,output [AXI4_DATA_WIDTH/8-1:0] m_axi_wstrb0,output m_axi_wlast0,output m_axi_wvalid0,input m_axi_wready0,input [AXI4_ID_WIDTH-1:0] m_axi_bid0,input [1:0] m_axi_bresp0,input m_axi_bvalid0,output m_axi_bready0,output [AXI4_ID_WIDTH-1:0] m_axi_arid0,output [AXI4_ADDR_WIDTH-1:0] m_axi_araddr0,output [AXI4_LENGTH_WIDTH-1:0] m_axi_arlen0,output [2:0] m_axi_arsize0,output [1:0] m_axi_arburst0,output [3:0] m_axi_arcache0,output [2:0] m_axi_arprot0,output m_axi_arvalid0,input m_axi_arready0,input [AXI4_ID_WIDTH-1:0] m_axi_rid0,input [AXI4_DATA_WIDTH-1:0] m_axi_rdata0,input [1:0] m_axi_rresp0,input m_axi_rlast0,input m_axi_rvalid0,output m_axi_rready0
);endmodule

看到了Vivado有两条axi总线,一条Master一条Slave,我们现在要做的就是用IP Integretor HDL语言强制将两条AXI总线指定出来,并让它们以总线形式显示。

我添加好的axi_dma_controller的代码:

module axi4_controller_top #(parameter DATA_WIDTH = 'h100,parameter ADDR_WIDTH = 'h20,parameter LENGTH_WIDTH = 'h8,parameter ID_WIDTH = 'h2,parameter MASTER_ID = 'h1,parameter CLK_FREQ = 'hc8,parameter ADDR = 'h109000
)(//Other port// AXI4Lite_slave(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite AWADDR" *)input [31:0] s_axil_awaddr0, // Write address (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite AWVALID" *)input s_axil_awvalid0, // Write address valid (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite AWREADY" *)output s_axil_awready0, // Write address ready (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite WDATA" *)input [31:0] s_axil_wdata0, // Write data (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite WSTRB" *)input [3:0] s_axil_wstrb0, // Write strobes (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite WVALID" *)input s_axil_wvalid0, // Write valid (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite WREADY" *)output s_axil_wready0, // Write ready (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite BRESP" *)output [1:0] s_axil_bresp0, // Write response (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite BVALID" *)output s_axil_bvalid0, // Write response valid (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite BREADY" *)input s_axil_bready0, // Write response ready (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite ARADDR" *)input [31:0] s_axil_araddr0, // Read address (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite ARVALID" *)input s_axil_arvalid0, // Read address valid (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite ARREADY" *)output s_axil_arready0, // Read address ready (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite RDATA" *)output [31:0] s_axil_rdata0, // Read data (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite RRESP" *)output [1:0] s_axil_rresp0, // Read response (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite RVALID" *)output s_axil_rvalid0, // Read valid (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 S_AXI_Lite RREADY" *)input s_axil_rready0, // Read ready (optional)(* X_INTERFACE_PARAMETER = "ASSOCIATED_BUSIF S_AXI_Lite, ASSOCIATED_RESET s_axil_aresetn0, FREQ_HZ 100000000" *)(* X_INTERFACE_INFO = "xilinx.com:signal:clock:1.0 s_axil_aclk0 CLK" *)input s_axil_aclk0,(* X_INTERFACE_PARAMETER = "POLARITY ACTIVE_LOW" *)(* X_INTERFACE_INFO = "xilinx.com:signal:reset:1.0 s_axil_aresetn0 RST" *) output s_axi_aresetn0,// AXI4_masteroutput [AXI4_ID_WIDTH-1:0] m_axi_awid0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI AWADDR" *)output [AXI4_ADDR_WIDTH-1:0] m_axi_awaddr0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI AWLEN" *)output [AXI4_LENGTH_WIDTH-1:0] m_axi_awlen0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI AWSIZE" *)output [2:0] m_axi_awsize0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI AWBURST" *)output [1:0] m_axi_awburst0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI AWCACHE" *)output [3:0] m_axi_awcache0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI AWPROT" *)output [2:0] m_axi_awprot0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI AWVALID" *)input m_axil_awvalid0, // Write address valid (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI AWREADY" *)output m_axil_awready0, // Write address ready (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI WDATA" *)output [AXI4_DATA_WIDTH-1:0] m_axi_wdata0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI WSTRB" *)output [AXI4_DATA_WIDTH/8-1:0] m_axi_wstrb0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI WLAST" *)output m_axi_wlast0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI WVALID" *)input m_axil_wvalid0, // Write valid (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI WREADY" *)output m_axil_wready0, // Write ready (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI BID" *)input [AXI4_ID_WIDTH-1:0] m_axi_bid0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI BRESP" *)output [1:0] m_axil_bresp0, // Write response (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI BVALID" *)output m_axil_bvalid0, // Write response valid (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI BREADY" *)input m_axil_bready0, // Write response ready (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI ARID" *)output [AXI4_ID_WIDTH-1:0] m_axi_arid0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI ARADDR" *)output [AXI4_ADDR_WIDTH-1:0] m_axi_araddr0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI ARLEN" *)output [AXI4_LENGTH_WIDTH-1:0] m_axi_arlen0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI ARSIZE" *)output [2:0] m_axi_arsize0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI ARBURST" *)output [1:0] m_axi_arburst0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI ARCACHE" *)output [3:0] m_axi_arcache0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI ARPROT" *)output [2:0] m_axi_arprot0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI ARVALID" *)input m_axil_arvalid0, // Read address valid (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI ARREADY" *)output m_axil_arready0, // Read address ready (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI RID" *)input [AXI4_ID_WIDTH-1:0] m_axi_rid0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI RDATA" *)input [AXI4_DATA_WIDTH-1:0] m_axi_rdata0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI RRESP" *)output [1:0] m_axil_rresp0, // Read response (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI RLAST" *)input m_axi_rlast0,(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI RVALID" *)output m_axil_rvalid0, // Read valid (optional)(* X_INTERFACE_INFO = "xilinx.com:interface:aximm:1.0 M_AXI RREADY" *)input m_axil_rready0, // Read ready (optional)(* X_INTERFACE_PARAMETER = "ASSOCIATED_BUSIF M_AXI, ASSOCIATED_RESET m_axi_aresetn0, FREQ_HZ 100000000" *)(* X_INTERFACE_INFO = "xilinx.com:signal:clock:1.0 m_axil_aclk0 CLK" *)output m_axi_aclk0,(* X_INTERFACE_PARAMETER = "POLARITY ACTIVE_LOW" *)(* X_INTERFACE_INFO = "xilinx.com:signal:reset:1.0 m_axil_aresetn0 RST" *)output m_axi_aresetn0
);endmodule

 

可以看到Slave AXI和Master AXI已经以总线图标显示,并能以总线接口进行连线,这是System Verilog才具有的功能,但是Vivado通过Block将其应用在Verilog和VHDL上了。

有的时候Vivado可以根据RTL Module自动推断出模块内的接口,这时候可以不用,但是自动推断的接口,经常会有莫名其妙的问题。如果系统内没有满足自己需要的接口,可以自定义接口,同样可以被IP Integrator HDL使用。

 

这篇关于Vivado使用系列:IP Integrator HDL的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/317267

相关文章

Java使用Javassist动态生成HelloWorld类

《Java使用Javassist动态生成HelloWorld类》Javassist是一个非常强大的字节码操作和定义库,它允许开发者在运行时创建新的类或者修改现有的类,本文将简单介绍如何使用Javass... 目录1. Javassist简介2. 环境准备3. 动态生成HelloWorld类3.1 创建CtC

使用Python批量将.ncm格式的音频文件转换为.mp3格式的实战详解

《使用Python批量将.ncm格式的音频文件转换为.mp3格式的实战详解》本文详细介绍了如何使用Python通过ncmdump工具批量将.ncm音频转换为.mp3的步骤,包括安装、配置ffmpeg环... 目录1. 前言2. 安装 ncmdump3. 实现 .ncm 转 .mp34. 执行过程5. 执行结

Java使用jar命令配置服务器端口的完整指南

《Java使用jar命令配置服务器端口的完整指南》本文将详细介绍如何使用java-jar命令启动应用,并重点讲解如何配置服务器端口,同时提供一个实用的Web工具来简化这一过程,希望对大家有所帮助... 目录1. Java Jar文件简介1.1 什么是Jar文件1.2 创建可执行Jar文件2. 使用java

C#使用Spire.Doc for .NET实现HTML转Word的高效方案

《C#使用Spire.Docfor.NET实现HTML转Word的高效方案》在Web开发中,HTML内容的生成与处理是高频需求,然而,当用户需要将HTML页面或动态生成的HTML字符串转换为Wor... 目录引言一、html转Word的典型场景与挑战二、用 Spire.Doc 实现 HTML 转 Word1

Java中的抽象类与abstract 关键字使用详解

《Java中的抽象类与abstract关键字使用详解》:本文主要介绍Java中的抽象类与abstract关键字使用详解,本文通过实例代码给大家介绍的非常详细,感兴趣的朋友跟随小编一起看看吧... 目录一、抽象类的概念二、使用 abstract2.1 修饰类 => 抽象类2.2 修饰方法 => 抽象方法,没有

MyBatis ParameterHandler的具体使用

《MyBatisParameterHandler的具体使用》本文主要介绍了MyBatisParameterHandler的具体使用,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参... 目录一、概述二、源码1 关键属性2.setParameters3.TypeHandler1.TypeHa

Spring 中的切面与事务结合使用完整示例

《Spring中的切面与事务结合使用完整示例》本文给大家介绍Spring中的切面与事务结合使用完整示例,本文通过实例代码给大家介绍的非常详细,对大家的学习或工作具有一定的参考借鉴价值,需要的朋友参考... 目录 一、前置知识:Spring AOP 与 事务的关系 事务本质上就是一个“切面”二、核心组件三、完

使用docker搭建嵌入式Linux开发环境

《使用docker搭建嵌入式Linux开发环境》本文主要介绍了使用docker搭建嵌入式Linux开发环境,文中通过示例代码介绍的非常详细,对大家的学习或者工作具有一定的参考学习价值,需要的朋友们下面... 目录1、前言2、安装docker3、编写容器管理脚本4、创建容器1、前言在日常开发全志、rk等不同

使用Python实现Word文档的自动化对比方案

《使用Python实现Word文档的自动化对比方案》我们经常需要比较两个Word文档的版本差异,无论是合同修订、论文修改还是代码文档更新,人工比对不仅效率低下,还容易遗漏关键改动,下面通过一个实际案例... 目录引言一、使用python-docx库解析文档结构二、使用difflib进行差异比对三、高级对比方

sky-take-out项目中Redis的使用示例详解

《sky-take-out项目中Redis的使用示例详解》SpringCache是Spring的缓存抽象层,通过注解简化缓存管理,支持Redis等提供者,适用于方法结果缓存、更新和删除操作,但无法实现... 目录Spring Cache主要特性核心注解1.@Cacheable2.@CachePut3.@Ca