In reply to dave_59:
In reply to Fipser@VA:
That’s a different situation. If you have parameters you want to be used by both DUT and testbench, the common package is the way to go. The config_db is for per-test parameterization.
Thanks for the clarification. So in order to be able to access the package from both the driver side and for the DUT generics I will have to import it at driver level (the corresponding agent package) as well? Meaning I have to push the test_params_pkg compilation to the front of the compilation order.