In reply to chr_sue:
In reply to haithamx15:
It looks like you have a configuration in your environment and want to control your OCP agents. I think this is not a good ülace, because the environment has to be customized with respect to a certain test. For this reason you should move your configuration object up to the test.
All configuration data has to be defined in any place, but you can modify them depending on your actual configuration, i.e. number of masters, slaves etc. You can even randomize your configurations. Your configuration data can cover any aspects like ‘has_coverage’ or ‘is_active’, etc.
Seems reasonable, however those configurations concern the testbench itself, there are some parameters that are concerned with OCP protocol itself. for example addr_width. parameters that enable or disables some of the ocp features. Should those also be put in the configuration class? A better places for such parameters is a class isn’t it?