Hardware interview practice
UVM callbacks
A callback object is constructed and added with uvm_callbacks#(driver_t, driver_cb)::add, but its method is never called. What is the most likely missing step?
Choose one
Answer choices
- A. The callback must extend uvm_driver and own a sequencer port
- B. Every callback automatically runs only in final_phase
- C. The driver class must explicitly invoke the registered callbacks at the desired hook, typically using the UVM callback iteration/invocation macros
- D. Callbacks work only when report verbosity is UVM_DEBUG