How gokulbalagopal/verification-of-apb-protocol-using-uvm works
Project type and purpose
• This is a hardware-verification project using UVM (Universal Verification Methodology) to verify an APB (Advanced Peripheral Bus) protocol implementation.
• The README confirms a SystemVerilog/Verilog design, a UVM testbench, and use of QuestaSim for simulation and coverage.
File structure
• Top-level RTL/DUT files:
– bridge_apb.sv (bus-bridge logic)
– slave_apb.sv (APB slave model)
– timer.v (example peripheral)
– top_apb.sv (top-level APB system instantiation)
• UVM testbench components (all .sv):
– apb_agent.sv
– apb_driver.sv
– apb_monitor.sv
– apb_scoreboard.sv
– apb_seq_item.sv (transaction definition)
– apb_sequence.sv (sequence of transactions)
– apb_sequencer.sv
– apb_env.sv (aggregates agent + scoreboard)
– apb_testbench_top.sv (top of UVM testbench)
– apb_test.sv (defines specific test scenarios)
Extract insights from the README
• UVM components created: sequencer, driver, monitor, agent, environment, scoreboard, testbench.
• Coverage report generation implies a coverage collector component (could be part of the UVM environment).