How to turn off Assertions?

UVM
1

Hi,

I need to turnoff all the assertions from environment to all the below hierarchy agents and components. In my case, I have written like $assertoff(0,env.run_phase.assertion name) using this only that particular assertion will be turned off. But I need to turn off all the assertions from the environment class to all the below agents and components from the top module only. Is it possible to do like that? without giving entire path to turnoff all the assertions?

Thanks in advance.

2

In reply to A E Aravind:

You can simply use
$assertoff(0,env)
or $assertoff(0)
to swicth-off all assertions in your environment.

3

This is not working, I am getting an error.

import uvm_pkg::*;
`include "uvm_macros.svh"

 class tb_env extends uvm_component;
  `uvm_component_utils(tb_env)

  int exp_val = 0;
  int act_val = 0;

  function new(string name = "tb_env", uvm_component parent = null);
    super.new(name, parent);
  endfunction

  virtual task run_phase (uvm_phase phase);
    super.run_phase(phase);
    phase.raise_objection(this);
    #10;
    ASRT: assert ( exp_val == act_val) else
     `uvm_error(get_full_name(), "Error");
    
    ASRT1: assert ( exp_val == act_val) else
      `uvm_error(get_full_name(), "second assertion Error");
    
    #10;
    `uvm_info(get_full_name(), "Done Env", UVM_LOW);
    phase.drop_objection(this);
  endtask : run_phase
endclass

 

module tb_run;
  //tb_env env = new();
  
  initial
  begin
      tb_env env = new();

    //$assertoff(0,env.run_phase.ASRT);  
    //$assertoff(0,env.run_phase.ASRT1);
    
       //$assertoff(0);
       $assertoff(0,env);

     fork
       run_test();
       begin
         #5;
         env.exp_val = 1;
         $display("@%0t : exp_val - %0b, act_val - %0b", $time(), env.exp_val, env.act_val);
       end
     join
  end
endmodule

Error-[WRONGARGCNTRLTASK] Illegal argument of control task
testbench.sv, 43
“$assertoff(0, env);”
Argument of SVA control task should be module, hierarchical instance or
assertion

4

In reply to A E Aravind:

When removing run_test it works perfectly for me.
Note you do not have a testclass defined which couls be started using run_test.