In reply to cgales:
In reply to Fipser@VA:
Your agent (and driver) should have a configuration object that contains all the parameters regarding the functionality of the agent. You should create this configuration at the test level, set the parameters as required, store it in the config_db(), and retrieve it in the agent during the build() phase.
Thanks for your reply. Yes, I have the configuration objects set up as described in the cookbook, and they also get created at the test level (in the test base class xxx_test_base.svh) and retrieved in the agent's build phase (as you described).
The thing is that these constants/parameters I need to access in the driver are mainly used as DUT generics. So the test_params_pkg is imported into the top lvl testbench module, and that's it. But from a hierarchical point of view, of course I do not have access to these constants/parameters as components/classes are included bottoms up (and the driver being at the lowest level).
Do I still have to pass these constants/parameters via the configuration object now? I'm not sure at the moment how to achieve this.