Jump to content
Sign in to follow this  

Requirement of objections in UVM

Recommended Posts



I have a doubt about requirement of raise/drop_objection.


Why does a compiler need objections in run_phase?


Why can it not just wait for time given like 100ns as following example?



task run_phase(uvm_phase phase);







Share this post

Link to post
Share on other sites

Some components may have a run-time phase which operates in a "Run forever and wake up when there's something to do" mode, like this simplistic driver:

virtual task run_phase(uvm_phase phase);
   forever begin
endtask : run_phase

When there are no objections remaining, all of the tasks spawned by all of the component's run phases are killed. This is a feature, not a bug.


It just wouldn't do to kill this task's run phase while it was driving a request. And UVM cannot implicitly know how long that will take. Therefore, the objection software pattern is used for all run-time phases.

Share this post

Link to post
Share on other sites

Mainly the objections are used in testcases, which helps in simulation to end after your sequences or intented operations are performed.Hard coded delays are not good to use, because when you are doing Constaint Random testing we can't predict completion time.I think I answered your question

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this