precedence of set_config/config_db in build phase

[manjubshetty]

Hey,

In our environment, we overwrite few variables using set_config/config_db in test file. these variable also have a default value set in base test class.

Following pseudo code shows the guts of it.

class test extends test_base

...

virtual function build()

...

this.set_config_int("*", "timer", 300);

...

endfunction

endclass

class test_base extends uvm_test

...

virtual function build()

...

this.set_config_int("*", "timer", 100);

...

endfunction

endclass

In OVM this was working fine and "timer" used to get the value "300". Now we have the environment migrated to UVM and this is not working anymore.

By adding a print statement in both build(), I see the following behavior:

for OVM:

OVM_INFO @ 0.000 ns: ovm_test_top [ovm_test_top] timer = 100

OVM_INFO @ 0.000 ns: ovm_test_top [ovm_test_top] test: timer = 300

for UVM:

UVM_INFO @ 0.000 ns: uvm_test_top [uvm_test_top] test: timer = 300

UVM_INFO @ 0.000 ns: uvm_test_top [uvm_test_top] timer = 100

Am I missing any thing obvious here, during OVM to UVM migration?

Regards,

Manju Shetty

[manjubshetty]

FYI.

Issue was using build() instead of build_phase() in my test file. With the change precedence is as expected in UVM too.

Regards,

Manju Shetty