Class uvm_reg_item
Name |
Type |
Description |
---|---|---|
element_kind |
Kind of element being accessed REG, MEM, or FIELD. See uvm_elem_kind_e. |
|
element |
A handle to the RegModel model element associated with this transaction. Use element_kind to determine the type to cast to: uvm_reg, uvm_mem, or uvm_reg_field. |
|
kind |
Kind of access READ or WRITE. |
|
value |
The value to write to, or after completion, the value read from the DUT. Burst operations use the values property. |
|
offset |
For memory accesses, the offset address. For bursts, the starting offset address. |
|
status |
||
local_map |
The local map used to obtain addresses. Users may customize address-translation using this map. Access to the sequencer and bus adapter can be obtained by getting this map's root map, then calling uvm_reg_map::get_sequencer and uvm_reg_map::get_adapter. |
|
map |
The original map specified for the operation. The actual map used may differ when a test or sequence written at the block level is reused at the system level. |
|
path |
The path being used <UVM_FRONTDOOR> or <UVM_BACKDOOR>. |
|
parent |
The sequence from which the operation originated. |
|
prior |
int |
The priority requested of this transfer, as defined by uvm_sequence_base::start_item. |
extension |
Handle to optional user data, as conveyed in the call to write(), read(), mirror(), or update() used to trigger the operation. |
|
bd_kind |
string |
If path is UVM_BACKDOOR, this member specifies the abstraction kind for the backdoor access, e.g. "RTL" or "GATES". |
fname |
string |
The file name from where this transaction originated, if provided at the call site. |
lineno |
int |
The file name from where this transaction originated, if provided at the call site. |
Name |
Description |
---|---|
max_values |
TODO parameterize |
Constructors
Functions
- virtual function void do_copy ( uvm_object rhs ) [source]
Copy the rhs object into this object. The rhs object must derive from uvm_reg_item.
Defines an abstract register transaction item. No bus-specific information is present, although a handle to a uvm_reg_map is provided in case a user wishes to implement a custom address translation algorithm.