I use the following command in the simulation file for stop the simulation:
+UVM_MAX_QUIT_COUNT
The issue is that the simulation stops when any error (uvm_error/uvm_fatal_ occur). Is there an option to manage the errors, so some errors will cause the simulation to stop and some no?
With UVM_MAX_QUIT_COUNT=1 you are advicing the simulator to stop after the first error. You see it works perfectly. If you want the simulator to tolerate some errors you have to set UVM_MAX_QUIT_COUNT to any value different from 1. In my projects I use a value between 10 and 30.
In reply to saritr:
With UVM_MAX_QUIT_COUNT=1 you are advicing the simulator to stop after the first error. You see it works perfectly. If you want the simulator to tolerate some errors you have to set UVM_MAX_QUIT_COUNT to any value different from 1. In my projects I use a value between 10 and 30.
How can I manage the simulator to tolerate some errors?
Youz have 2 options:
(1) from the CLI (command line interface) you can issue:
+UVM_MAX_QUIT_COUNT=10
(2) from your test you can call
set_report_max_quit_count(10).
In both cases the simulation will stop after 10 errors.
In reply to saritr:
If you want to change how a message behaves, you can either override the severity of a message (i.e. change from error to warning) or you can change the actions associated with a message (remove the UVM_COUNT action so it does not stop when reaching the max_quit_count).