Verifying a simple ram module using AXI Master/Slave UVM method.
Our project aims to test a ram module using UVM method. Ram module is used to perform simple write/read opeartion on a particular address. Here, our ram module acts like a slave dut & we run it by using AXI Master. We generate our inputs from a sequencer. Then we drive our ram module via driver module. Monitor block reads the information of each transactions from the interface and sends them to Scoreboard module. Scoreboard module compares the result and shows us the final result if a successful operation was performed or not.
Our folder structure is given below,
├── top
│ ├── axi_test.sv
│ └── axi_top.sv
│ └── tb_top.sv
├── rtl
│ └── axi_slave_dut.sv
├── interface
| └── my_interface.sv
├── env
| ├── axi_env.sv
│ └── axi_sb.sv
│ └── axi_subscriber.sv
├── agent
| ├── axi_m_agent.sv
│ └── axi_m_drv.sv
│ └── axi_m_mon.sv
│ └── axi_m_seq.sv
│ └── my_seq_item.sv
│ └── my_sqncr.sv
│ └── axi_s_agent.sv
│ └── axi_s_mon.sv
└── README.mdIn this section we have provided details information of our modules.
-
axi_test: axi_test is the top level UVM component in the UVM testbench. This level instantiates the top level environment, configures the environment and applies stimulus by invoking UVM Sequences through the environment to the DUT.
-
axi_top: In axi_top we defined the clock, reset signals & their timeperiods. We also made connection with the DUT in this level. "axi_test" is initiated thorugh this module.
-
tb_top: In this module we have defined our modules access paths. One might need to change this if they want to run it in their machine.
-
my_interface: Interface module defines all the AXI protocol signals and their data types & sizes.
-
axi_env: axi_env module encapsulates the scoreboard & the agent modules. Environment module maintains the connections between various ports.
-
axi_sb: axi_sb module is like a checker board. This module checks the data & compares them. Scoreboard recieves data from the sequence item & the monitor.
-
my_seq_item: my_seq_item module initializes the input signals to drive the DUT.
-
axi_m_seq: axi_m_seq module generates various input sequences like write_sequence, read_sequence for the DUT using my_seq_item module
-
my_sqncr: This module is like a gateaway between driver module & sequence item.
-
axi_m_drv: This module drives the DUT through the interface. They receive the datas from the "my_sqncr" module.
-
axi_mon: This module just monitors all the datas from the interface. Then, it lists down all the informations & sends them to the scorboard.
-
axi_m_agent: Agent module encapsulates three modules (sequencer, driver & monitor)
Below, we have shown our UVM architecture.
To simulate this project we need Xilinx Vivado as our EDA tool. We used the student version 2020.2
Below we have shown how one can install Xilinx Vivado Webpack.
- First one must go to this site at https://www.xilinx.com/support/download.html
- Now you can download any version (preferably the latest one) according to their own operating system.
- One must create an account before downloading the EDA.
- Then by following on screen instructions one can easily install the tool on their machine.
- For first time run, one need to install gcc,gnn compilers.
Before executing the program one must configure the settings of vivado.
- We have to type "-L uvm" in the marked area.
- Just like the first one, we have to type "-L uvm" in the marked area.
- For the last modification we have to type "-testplusarg UVM_TESTNAME=axi_Test -testplusarg UVM_VERBOSITY=UVM_LOW" in the marked area.
- Nahid Rahman
- Md. Shamiul Alam Hriday
- 0.1
- Initial Release: This project only can simulate single fixed-burst operation mode. Currently we are working to simulate multiple incremental & wrapping burst mode. Will update them as soon as they are functional.
For our ram DUT we used, https://github.com/alexforencich/verilog-axi/blob/master/rtl/axi_ram.v