How kowdoorshashank/uvm_learning works
Project Type and Purpose
• This project is a UVM-based SystemVerilog testbench for verifying an Up/Down counter (see Up_Down_Counter.sv and tb.sv).
• Its purpose is to apply stimulus via UVM sequences, drive the DUT, monitor responses, check assertions, and collect coverage.
File Structure
• Top-level DUT and testbench:
• Up_Down_Counter.sv – the design under test (DUT)
• tb.sv – top testbench module that instantiates DUT and UVM test
• UVM environment files:
• Counter_intf.sv – defines the SystemVerilog interface connecting testbench and DUT
• Counter_env.sv – top UVM environment container
• Counter_agent.sv – UVM agent (bundles driver, monitor, sequencer)
• Counter_driver.sv – drives DUT inputs based on sequence items
• Counter_monitor.sv – samples DUT outputs for checks and coverage
• Counter_sequencer.sv – arbitrates sequence item issuance
• Counter_sequence.sv – sequence of operations (transactions)
• Counter_sequence_item.sv – single transaction definition
• Test control:
• Counter_test.sv – UVM test class that configures environment and starts sequences
• Verification aid:
• Counter_Sequencer.sv appears to be a duplicate or variant naming of Counter_sequencer.sv
• Conter_Sequencer.sv – likely a typo’d copy; can be merged/removed
README for Additional Insights
• Asserts on up/down counter behavior are included (likely inside Up_Down_Counter.sv or in UVM scoreboard/assertion blocks).
Detail & Clarity
• Both transaction-level and pin-level flows.
• Notes on where assertions reside.