Work it through
An external master writes 0xA5
A write outside RAL changes the DUT. With no monitor-connected predictor, the model can still say 0x5A.
A stale mirror is a model synchronization failure, even if the DUT register is correct.
Your next page is on its way.
Chapter 3 · Checking & debug
Keep observation independent from prediction, choose the correct TLM path, and debug hangs, report severity, and register-model synchronization with evidence.

A worked mechanism
Use an ordinary 8-bit RW register with initial DUT and mirror value 0x00.
desired = 0x5A; mirror = 0x00
set() changes model intent without performing a bus transaction.
DUT receives WRITE 0x5A
update() can issue the needed frontdoor write; check its status.
mirror = 0x5A
The configured prediction path updates the mirror using the access policy and observed transaction.
Work it through
A write outside RAL changes the DUT. With no monitor-connected predictor, the model can still say 0x5A.
A stale mirror is a model synchronization failure, even if the DUT register is correct.
W1C, read-clear, and volatile fields require their own prediction policies; the simple RW example does not apply unchanged.
Inject a non-RAL access and verify prediction, then disable prediction in a negative test so the mismatch is observable.
Question directory
Open an authored answer here, then follow its diagram and implementation example in context.
Treat the monitor as the source of observed behavior, use analysis connections for fan-out, and keep prediction independent from the actual-data path.
The monitor publishes a fresh observed transaction. Coverage samples it, the predictor creates expected behavior, and the scoreboard compares expected with actual.
An analysis port broadcasts a transaction through a zero-time write() function to every connected subscriber. Put and get interfaces model directed transfer and may be blocking or nonblocking.
write() or modify the shared transaction. Clone it or use a uvm_tlm_analysis_fifo when deferred processing is required.seq_item_port and seq_item_export pull interface, not an ordinary uvm_tlm_put_port or uvm_tlm_get_port.| Interface | Communication | Typical use |
|---|---|---|
| analysis | Broadcast write(), no time | Monitor fan-out |
| put/get | Directed, blocking or nonblocking | Producer-consumer transport |
seq_item | Arbitrated request/completion | Sequencer-driver |
The sequence creates intent, the driver realizes it on pins, the DUT transforms it, and the monitor reconstructs a new observed transaction for the checking path.
Choose report severity by recoverability, debug hangs from phase control outward, and use RAL as a synchronized model rather than a magical mirror.
Register intent travels through the map and adapter to the DUT. Prediction keeps the model mirror aligned with observed bus activity.
UVM_ERROR reports a recoverable test failure and normally lets simulation continue. UVM_FATAL reports an unusable testbench state and normally exits immediately.
| Severity | Default intent | Example |
|---|---|---|
UVM_ERROR | Record failure and continue | Scoreboard mismatch |
UVM_FATAL | Report and exit | Required virtual interface missing |
Start with phase control, then trace the sequencer-driver contract, topology, blocked waits, and finally clock or reset progress.
+UVM_OBJECTION_TRACE and +UVM_PHASE_TRACE. Identify the active phase, the source of every remaining objection, and whether another phase domain is still running.start_item/finish_item against get_next_item/item_done, confirm the sequence started on the intended sequencer, and verify the port-export connection and parameter types.RAL gives tests a named model of registers, fields, maps, access policies, desired values, and mirrored values, independent of the bus used to reach the DUT.
uvm_status_e status;
uvm_reg_data_t value;
reg_model.control.write(status, 'h5A, .parent(this));
reg_model.status.read(status, value, .parent(this));
if (status != UVM_IS_OK)
`uvm_error("RAL", "register access failed")