We are having an ovm env where multiple high level sequencers connected to a single low level sequencer (ahb_rgm_mseqr).
e.g.
h1_reg_sequencer[0].req_port.connect(ahb_mseqr.reg_req_export);
ahb_rgm_mseqr.reg_rsp_port.connect(h1_reg_sequencer[0].rsp_export);
h2_reg_sequencer[0].req_port.connect(ahb_mseqr.reg_req_export);
ahb_rgm_mseqr.reg_rsp_port.connect(h2_reg_sequencer[0].rsp_export);
h3_reg_sequencer[0].req_port.connect(ahb_mseqr.reg_req_export);
ahb_rgm_mseqr.reg_rsp_port.connect(h3_reg_sequencer[0].rsp_export);
If only one high level sequencer is active e.g(h1_reg_sequencer[0]),the responses going to the other two were dropped and
giving OVM_INFO messages as
" ovm_test_top.ve.h2_reg_sequencer[0] [Sequencer] Dropping response for sequence 5, sequence not found. Probable cause: sequence exited or has been killed "
" ovm_test_top.ve.h3_reg_sequencer[0] [Sequencer] Dropping response for sequence 5, sequence not found. Probable cause: sequence exited or has been killed "
:
:
and so on.
Although the functionality works fine, the above messages were clobbering the log file and hence difficult to debug the log.
Can anyone know the solution to resolve the above case and hence stopping the messages getting clobbered the log file ?
Thanks,
Muthu