UVM Environment (i)

1) How to avoid the emergence of absolute path: absolute path is generally used in the signal connection relationship, so you can use virtual interface, through the assignment of the handle to dynamically establish the connection relationship. So how does the top-level module

The interface handle is assigned to Driver/monitor, and through config_db, the path completion handle assignment must be explicitly indicated. And config_db is a parameterized

class, the parameter type is the type to transfer. Set and get are two static function. It is generally placed in the initial procedure block of test or other build_phase to complete the parameter configuration.

2) Objection mechanism: Raise_objection and drop_objection in pairs appear to control the running time of phase by triggering event events. (limit: Must be in the first statement that consumes simulation time

Prior to the raise).

3) Factory mechanism: Use the macro definition mechanism uvm_component_utils (), register the component in the UVM environment, so config_db can only find the path. When running Run_test (env), UVM starts

Starting with each phase from its own build_phase, it is common to introduce new () in the build_phase of Env to build each component. As opposed to component, the top of the UVM

Layer is uvm_test_top. Another type of macro definition is uvm_object_utils.

4) Phase mechanism: UVM in the phase are a function, but UVM to them have a special event contact, you can start directly through the Run_test (), and strictly in accordance with the specified order of execution to execute

UVM Environment (i)