UVMLint - why not to "re-declare" is_active inside agent?

 Building on PySlint, UVMLint is adding rules for UVM based testbenches. A recent user reported the following violation:


That's just a short reporting, with detailed message to follow (users can add more information at their end with PySlint API soon). Let's understand why this is considered a bad practice in UVM. 

To speed things up (and to add spice to it), we used Google Bard on "what is is_active in UVM agent" and below is a response: 

The is_active variable in a UVM agent is an enum type of uvm_active_passive_enum. It specifies whether the agent is active or passive. An active agent has a driver and sequencer, while a passive agent only has a monitor.

The is_active variable is a useful tool for controlling the behavior of UVM agents. By setting the is_active variable, you can control whether an agent has a driver and sequencer, or whether it only has a monitor.

Not bad for a GenerativeAI conversation, isn't? As a quick recap, UVM agent is a specialized component and its UVM looks as follows:


UVM Base Class that defines uvm_agent is shown below:
A derived agent (such as hbus_agent) inherits this field is_active and hence no need to re-declare. Say a sample user code looks as follows:



UVMLint would flag that line-20 and report it as poor code. Why? Well, below are some rationales:

  • The value of is_active as declared above would be set to be UVM_PASSIVE - this is against the UVM standard implementation that makes it UVM_ACTIVE as the default.
  • Protected would prevent an env class unable to access this field - a common code style other UVCs (that do not override base class's is_active unlike above).
  • What's the point of using uvm_agent here as base class and not uvm_component? - make no mistake; we are not suggesting you do that, rather questioning why the re-declaration in user agent code.
So if you want to check for such issues in your UVM testbenches, start innovating on top of open-source PySlint https://github.com/AsFigo/pyslint








Comments

Post a Comment

Popular posts from this blog

Don't go "wild" with Associative arrays in SystemVerilog - PySlint it!

Image
 Hash tables, modeled via Associative arrays is a powerful data structure in SystemVerilog. Python calls it as "dictionary". One of the "wild" features of SystemVerilog is that it allows associative arrays to be declared with arbitrary key type. An example:           class wild_c;             string wild_hash_table [*];           endclass : wild_c While the above is a legal SystemVerilog code, may even be seen as "easier" to write, it is bad from a reuse perspective. Some of the side effects (mostly bad) are: Unclear data structure to begin with - for writer and then the reader/maintainer of the code.  As the key can be anything, SV does not allow wildcard indexed associative array to be iterated via foreach loop. It cannot be passed as function parameter. Many find*  methods do not work on wild-card indexed associative arrays. For instance, find_first would need to return a queue of the keys, and when used on wild-card indexed array, it would be a queue o
Read more

Porting a complete UVC to Verilator + UVM - an anecdote!

Image
 So, here we are on Day-1 of UVM + Verilator becoming available to the public, start of democratizing chip design verification. In case you just woke-up/started on this topic, read the release of UVM + Verilator with some intricate details on the challenge on the way by Antmicro via:  https://antmicro.com/blog/2023/10/running-simple-uvm-testbenches-in-verilator/  Awesome work by the folks at Antmicro and fantastic support by the ecosystem specifically Western Digital, kudos!  At AsFigo , we are committed to fueling open-source driven chip design and verification. So we took this opportunity to port a commercial-grade UVC (Universal Verification Component or a Verification IP) and ported it to compile and run on Verilator. Below are our reflections from this experiment. Get in touch with us to discuss how AsFigo can help your VIPs and testbenches to be ported to opensource EDA.  Case study: VLBus - a simple peripheral bus intended for write/read to configuration registers (like the pop
Read more

Opensource testbench generator for VHDL designs, OSVVM included!

Image
VHDL holds a prominent position in the world of FPGA design, particularly within the military, aerospace, and defense sectors. It serves both as a Register Transfer Level (RTL) design language and as a tool for creating testbenches. The availability of open-source simulators, such as GHDL and NVC, alongside numerous free FPGA simulators and synthesis tools, has provided FPGA designers with a significant advantage over their SystemVerilog counterparts. While the Universal Verification Methodology (UVM) is widely adopted among SystemVerilog users, VHDL practitioners have traditionally relied on various homegrown methodologies and frameworks. Recently, however, off-the-shelf methodologies and frameworks such as OSVVM, UVVM, and VUnit have become available to VHDL users. Each of these options presents different levels of complexity, allowing users to choose the one that best meets their needs. Despite these advancements, the development of open-source utility tools supporting the latest me
Read more