Skip to question
asic.fyi
DesignVerificationSystemVerilogFirmwareArchitectureInterviews
asic.fyi/Interview questions/Nonblocking sequencer polling

Hardware interview practice

Nonblocking sequencer polling

EasyVerification UtilitiesSystemVerilog

What bug can occur in this driver when no sequence item is available?

Try it in the question bankReason first. Then compare.

Keep this exact question selected while you check your answer and review the full solution.

Practice this question →
Starting point

Question code

forever begin
  seq_item_port.try_next_item(req);
  if (req != null) begin
    drive(req);
    seq_item_port.item_done();
  end
end
Choose one

Answer choices

  1. A. The null path contains no blocking operation, creating a zero-time busy loop that can starve time advancement
  2. B. try_next_item raises a permanent objection when it returns null
  3. C. item_done must be called even when req is null
  4. D. A forever loop is illegal in run_phase
Continue practicing

Related questions

Verification UtilitiesBackground objections and blocking gets→Verification UtilitiesReset race in a forked driver→
asic.fyi · Learn silicon end to end.info@asic.fyi