Encountered the following error message today, while using the pre-defined UVM sequence uvm_reg_hw_reset_seq : UVM_ERROR @ 84050000:[uvm_test_top.m_env.m_core_agent.m_core_sequencer.reg_hw_reset_seq] Response queue overflow, response was dropped This occurred because the driver was sending a sequence response to the sequencer via the seq_item_port. The default size of the response queue between the sequence and driver is 8. When the …
Continue reading “reg_hw_reset_seq] Response queue overflow”
[START_SEQ] and [STARTING_SEQ] from the transcript got me intrigued: Why UVM’s verbose spits them out? [START_SEQ] is due to a sequence start on the sequencer, while [STARTING_SEQ]s are due to start of predefined UVM_REG sequences.
Because object “seq” was not created prior to starting the #UVM sequencer, questasim crashed horribly with # UVM_INFO @ 0: # uvm_test_top.m_env.m_core_agent Run phase # ** Fatal: (SIGSEGV) Bad handle or reference. # Time: 0 ps Iteration: 50 Process: # /uvm_pkg::uvm_task_phase::execute/#FORK#144(#ublk#43#144)_b6318a1 # Fatal error in Task uvm_pkg/uvm_sequence_base::start # at uvm-1.2/src/seq/uvm_sequence_base.svh line 258 Quick Solution: seq …
Continue reading “(UVM) : fatal error before starting the sequencer”
