UVM Factory what is it ? and it helps ?

 How can we add new functionality to our testbench ?

  • A Key UVM guideline is to write our testbench once
    • Basic functionality description which has a good transcations
    • Extend the classes to add new functionality
    • Need to make sure it won't break the existing setup
  • UVM Factory
    • Creates objects in the UVM Testbench
    • Allows the new written tests to "override" the original defined object 
  • Factory overrides are Very Important
    • Factory overrides make it possible to write many complex scenarios to run on the same testbench
  • Each test can customize the testbench at run time for the speicific needs of that test.

Comments

Post a Comment

Popular posts from this blog

Agent definition using UVM

  Agent is defined to make sure all the active and passive component elements are bundled in one group. which means the components like sequencer,driver are part of active elements and monitor, scoreboard, functional coverage are part of passive elements. Need to Bundle them together in an agent defined using "uvm_agent" library e.g class  tx_agent extends  uvm_agent ;        `uvm_component_utils (tx_agent)      function new (string name = "tx_agent", uvm_component parent);            super.new (name, parent);    endfunction   //  define the handle for driver, monitor and sequencer          tx_driver          drv;          tx_monitor         mon;          tx_sequencer       sqr;  //  build driver, monitor and sequencer  using factory  definition         virtual function void  build_phase (uvm_phase phase);           drv  =  tx_driver :: type_id :: create ("drv", this);           sqr  =  tx_sequencer :: type_id :: create("sqr", this);           m
Read more

How to define Packages using UVM

When we need to group our VE (Verification Environment) files for easier compilation we need to package them as because Our  compile strategy is project specific Below example demonstrate how we can create our own package and place all the files package   tx_pkg;       import   uvm_pkg ::*;      `include "uvm_macros.svh"         `include  "tx_item.svh"        `include  "tx_sequence.svh"        `include  "tx_sequencer.svh"        `include  "tx_driver.svh"        `include  "tx_monitor.svh"        `include  "tx_agent.svh"        `include  "tx_env.svh"        `include  "tx_test.svh" endpackage : tx_pkg *** Here  uvm_pkg and uvm_macros.svh  are the predefined UVM Package and macro libraries  *** As our VE (Verification Environment) are built on these macros we need to import before  importing our own files.
Read more

How to Run the test using UVM

Once we have all the Verification Environment available we need to perform compile, optimize, debug and simulate the defined test to check for transcation on DUT. Below example illustrates how we can integrate our verification package with Testbench having DUT in picture. e.g  module top();  import  uvm_pkg ::*;  import tx_pkg ::*;  // create handle for Virtual interface  // instiate the DUT      initial begin  // configure Virtual interface using uvm_config_db with set() method          run_test();       end endmodule         \
Read more