The UVM “Transaction Recording Database” classes are an abstract representation of the backend tool which is recording information for the user. Usually this tool would be dumping information such that it can be viewed with the waves of the DUT.
| Transaction Recording Databases | |
| The UVM “Transaction Recording Database” classes are an abstract representation of the backend tool which is recording information for the user. |
The uvm_tr_database class is intended to hide the underlying database implementation from the end user, as these details are often vendor or tool-specific.
The uvm_tr_database class is pure virtual, and must be extended with an implementation. A default text-based implementation is provided via the uvm_text_tr_database class.
| uvm_tr_database | ||||
| The uvm_tr_database class is intended to hide the underlying database implementation from the end user, as these details are often vendor or tool-specific. | ||||
| Class Hierarchy | ||||
| ||||
| Class Declaration | ||||
| ||||
| Database API | ||||
| Stream API | ||||
| Link API | ||||
| Implementation Agnostic API | ||||
The uvm_void class is the base class for all UVM classes.
virtual class uvm_void
The uvm_object class is the base class for all UVM data and hierarchical classes.
virtual class uvm_object extends uvm_void
The uvm_tr_database class is intended to hide the underlying database implementation from the end user, as these details are often vendor or tool-specific.
virtual class uvm_tr_database extends uvm_object
The uvm_text_tr_database is the default implementation for the uvm_tr_database.
class uvm_text_tr_database extends uvm_tr_database