I want to create a clock in my top level testbench whose period can be controlled from the test. What I did was set the period into the uvm_config_db and get it back in the testbench. I had to put in a #1 to make sure that the build phase was finished, otherwise the get returned the wrong value:
module testbench_top;
int clk_period;
bit clk = 0;
initial begin
#1;
void'(uvm_config_db #(int) ::get(null, "uvm_test_top.env", "clk_period", clk_period));
// Create clk
forever begin
#(clk_period/2) clk = !clk;
end
end
I am annoyed by the #1. Is there a better way to check that the config has been set? Can I somehow block until start_of_simulation_phase?
I found it buried in the class reference: You can access the global singleton versions of each phase with
<phase name>_ph
. Then I can use thewait_for_state
function to block until the start of the start of simulation phase. Simulated and it seems to work:Another alternative that can help is wait_modified function of uvm_config_db... Here is the excerpt from uvm reference manual
wait_modified:
Wait for a configuration setting to be set for field_namein cntxtand inst_name. The task blocks until a new configuration setting is applied that effects the specified field.