Download Public Interface

class bu_eth_mii extends bu_xactor {
...
protected task pre_frame_tx_t(...) {}
protected task post_frame_rx(...) {}
...
}
Note that the use of AOP callback extensions is restricted to
implementing testcases, not verification environments.
The AOP callback method shall be called before the
corresponding OOP callback method )
The OOP callbacks will be used to integrate the scoreboard and
sample functional coverage. These features are part of the
verification environment and thus must be implemented using the
OO programming model. The AOP callback, which may be used
to implement an error-injection testcase, may modify the content
of the transaction. Any such modification must be recorded in the
scoreboard and functional coverage model. Therefore, AOP
callback methods must be called before OOP callback methods.
For example:
task bu_eth_mii::main_t() {
...
while (1) {
...
this.pre_frame_tx_t(...);
rvm_OO_callback(bu_eth_mii_callbacks,
pre_frame_tx_t(...));
...
}
}
Transactors shall be configured using a randomizable
configuration object
The configuration of a transactor must be specified as an object.
All the properties in the configuration object must be randomized
to allow the generation of a random configuration – both to verify
Transactors: Transactor Models
6-10