Advantages and problems of uvm:10.5.2 polymerization parameters

1. After using the aggregation parameters, you can place a pointer to this parameter class in virtual sequencer:

2. When sequence to dynamically change the validation platform for a variable, the following:

3. You can even put interface into aggregate parameters:

4. In this way, either driver or monitor, you can use cfg.vif directly, without having to use config_db to get interface:

1) because interface is hidden in CFG.

2) If the CFG is assigned to sequencer, then the 10.3.1 Sequencer does not have to use get to get the interface.

5.my_config is an object, not a component. When you use GET, the result of Get_full_name is an instantiated name. So base_test in the name of the CFG with TOP_TB Config_db::set has been. Such as:

Or

6. The most convenient is as follows:

7. The aggregation parameter greatly facilitates the verification of the platform construction. Assign this pointer to any component, which no longer needs to be config_db::get. When a component is going to add a parameter, as long as

1) Add this parameter to the aggregation class.

2) Assign a value directly to the test case.

3) and then use it directly in the verification platform.

8. Join does not use aggregation class, but config_db, set:

Driver

1) reduce set, error probability decreased.

2) Imperfect, member variables are visible to all components.

3) Reduce reusability.

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Advantages and problems of uvm:10.5.2 polymerization parameters