In reply to chr_sue:
The last transaction is running for infinite time.
Output:
UVM_INFO dff_sequence.sv(40) @ 85: uvm_test_top.dff_env_h.dff_agent_h.dff_sqr_h@@dff_seq_h [DFF_GEN] ****The SEQUENCE at the iteration::[ 4 ] is****
UVM_INFO dff_sequence.sv(42) @ 85: uvm_test_top.dff_env_h.dff_agent_h.dff_sqr_h@@dff_seq_h [DFF_GEN] The Generator stimulus is: din=7
UVM_INFO dff_monitor.sv(53) @ 90: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=13::q=13::qbar=0
UVM_INFO dff_driver.sv(42) @ 95: uvm_test_top.dff_env_h.dff_agent_h.dff_drv_h [DFF_DRV] Triggered DUT and din=7::q=0
UVM_INFO dff_monitor.sv(53) @ 100: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=13::q=13::qbar=0
UVM_INFO dff_monitor.sv(53) @ 110: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=7::q=7::qbar=0
UVM_INFO dff_sequence.sv(40) @ 115: uvm_test_top.dff_env_h.dff_agent_h.dff_sqr_h@@dff_seq_h [DFF_GEN] ****The SEQUENCE at the iteration::[ 5 ] is****
UVM_INFO dff_sequence.sv(42) @ 115: uvm_test_top.dff_env_h.dff_agent_h.dff_sqr_h@@dff_seq_h [DFF_GEN] The Generator stimulus is: din=11
UVM_INFO dff_monitor.sv(53) @ 120: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=7::q=7::qbar=0
UVM_INFO dff_driver.sv(42) @ 125: uvm_test_top.dff_env_h.dff_agent_h.dff_drv_h [DFF_DRV] Triggered DUT and din=11::q=0
UVM_INFO dff_monitor.sv(53) @ 130: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=7::q=7::qbar=0
UVM_INFO dff_monitor.sv(53) @ 140: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=11::q=11::qbar=0
UVM_INFO dff_monitor.sv(53) @ 150: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=11::q=11::qbar=0
UVM_INFO dff_monitor.sv(53) @ 160: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=11::q=11::qbar=0
UVM_INFO dff_monitor.sv(53) @ 170: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=11::q=11::qbar=0
UVM_INFO dff_monitor.sv(53) @ 180: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=11::q=11::qbar=0
UVM_INFO dff_monitor.sv(53) @ 190: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=11::q=11::qbar=0
UVM_INFO dff_monitor.sv(53) @ 200: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=11::q=11::qbar=0
UVM_INFO dff_monitor.sv(53) @ 210: uvm_test_top.dff_env_h.dff_agent_h.dff_mon_h [D_FF_MON] The data sent to scoreboard::din=11::q=11::qbar=0
In each transaction monitor broadcasting two different values. Why is it happening? Problem with the monitor or scoreboard