Sometimes you will need to delay execution of a phase in your verification environment. A basic example is that in your test you might drive the sequences and then drop objection in the test to exit the test. In scoreboards or any monitors, if the transactions are still in line waiting for any responses or other stuff, you will have to delay the phase execution to flush all transactions. <\/p>\n\n\n\n
One of the way is to set the “set_drain_time<\/strong>” to specific phase that you need.<\/p>\n\n\n\n Another way is to use the “phase_ready_to_end<\/strong>” function of uvm component to induce delay.<\/p>\n\n\n\n Well “phase_ready_to_end” is a function, but how can i call it to insert delay. You need to raise objection create a fork join_none block and then you have to drop objection once your processing is complete. An example can be found below<\/p>\n\n\n\n Some caveats:<\/p>\n\n\n\n Sometimes you will need to delay execution of a phase in your verification environment. A…<\/p>\n... inside the component you want to set the drain time ... \ntask main_phase(uvm_phase phase);\n phase.set_drain_time(this, 500); \/\/this will set 500 timeunits of delay once all objections are dropped.\n \/\/You can also pass timeunits to the time like 500ns.. \nendtask<\/code><\/pre>\n\n\n\nfunction void phase_ready_to_end(uvm_phase phase);\n if(phase.get_name == \"main\" && (should_i_wait_or_not)) begin \/\/Use your own phase name which you want to stall, should_i_wait_or_not is a variable or function that you should see when do you want to delay the phase or not.\n phase.raise_objection(this);\n fork\n begin\n your_task_to_execute();\n end\n join_none\n end\n endfunction<\/code><\/pre>\n\n\n\n