aboutsummaryrefslogtreecommitdiffstats
path: root/fpga/usrp3/lib/axi/axi_lite_slave.v
diff options
context:
space:
mode:
authorBen Hilburn <ben.hilburn@ettus.com>2014-02-14 12:05:07 -0800
committerBen Hilburn <ben.hilburn@ettus.com>2014-02-14 12:05:07 -0800
commitff1546f8137f7f92bb250f685561b0c34cc0e053 (patch)
tree7fa6fd05c8828df256a1b20e2935bd3ba9899e2c /fpga/usrp3/lib/axi/axi_lite_slave.v
parent4f691d88123784c2b405816925f1a1aef69d18c1 (diff)
downloaduhd-ff1546f8137f7f92bb250f685561b0c34cc0e053.tar.gz
uhd-ff1546f8137f7f92bb250f685561b0c34cc0e053.tar.bz2
uhd-ff1546f8137f7f92bb250f685561b0c34cc0e053.zip
Pushing the bulk of UHD-3.7.0 code.
Diffstat (limited to 'fpga/usrp3/lib/axi/axi_lite_slave.v')
-rw-r--r--fpga/usrp3/lib/axi/axi_lite_slave.v42
1 files changed, 42 insertions, 0 deletions
diff --git a/fpga/usrp3/lib/axi/axi_lite_slave.v b/fpga/usrp3/lib/axi/axi_lite_slave.v
new file mode 100644
index 000000000..54cfa9c53
--- /dev/null
+++ b/fpga/usrp3/lib/axi/axi_lite_slave.v
@@ -0,0 +1,42 @@
+module axi_lite_slave
+ (
+ input aclk, // Global AXI clock
+ input aresetn, // Global AXI reset, active low.
+ //
+ // AXI Write address channel
+ //
+ input [31 : 0] m_axi_awaddr, // Write address. The write address gives the address of the first transfer in a write burst
+ input [2 : 0] m_axi_awprot, // Protection type. This signal indicates the privilege and security level of the transaction
+ input m_axi_awvalid, // Write address valid. This signal indicates that the channel is signaling valid write addr
+ output m_axi_awready, // Write address ready. This signal indicates that the slave is ready to accept an address
+ //
+ // AXI Write data channel.
+ //
+ input [31 : 0] m_axi_wdata, // Write data
+ input [3 : 0] m_axi_wstrb, // Write strobes. This signal indicates which byte lanes hold valid data.
+ input m_axi_wvalid, // Write valid. This signal indicates that valid write data and strobes are available.
+ output m_axi_wready, // Write ready. This signal indicates that the slave can accept the write data.
+ //
+ // AXI Write response channel signals
+ //
+ output [1 : 0] m_axi_bresp, // Write response. This signal indicates the status of the write transaction.
+ output m_axi_bvalid, // Write response valid. This signal indicates that the channel is signaling a valid response
+ input m_axi_bready, // Response ready. This signal indicates that the master can accept a write response
+ //
+ // AXI Read address channel
+ //
+ input [31 : 0] m_axi_araddr, // Read address. The read address gives the address of the first transfer in a read burst
+ input [2 : 0] m_axi_arprot, // Protection type. This signal indicates the privilege and security level of the transaction
+ input m_axi_arvalid, // Read address valid. This signal indicates that the channel is signaling valid read addr
+ output m_axi_arready, // Read address ready. This signal indicates that the slave is ready to accept an address
+ //
+ // AXI Read data channel
+ //
+ output [31 : 0] m_axi_rdata, // Read data.
+ output [1 : 0] m_axi_rresp, // Read response. This signal indicates the status of the read transfer
+ output m_axi_rvalid, // Read valid. This signal indicates that the channel is signaling the required read data.
+ input m_axi_rready, // Read ready. This signal indicates that the master can accept the read data and response
+ //
+ //
+ //
+ ) \ No newline at end of file