Skip to question
asic.fyi
DesignVerificationSystemVerilogFirmwareArchitectureInterviews
asic.fyi/Interview questions/Sequencer locks and grabs

Hardware interview practice

Sequencer locks and grabs

MediumUVM ComponentsSystemVerilog

Sequence A locks a sequencer and then waits for an event that can be generated only after sequence B sends an item on that same sequencer. Why can the test deadlock?

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 →
Choose one

Answer choices

  1. A. A lock randomizes B with incompatible constraints
  2. B. A lock prevents B from receiving a grant, so A waits on progress that its own exclusivity blocks
  3. C. lock releases automatically after each item, so B sends too early
  4. D. Locks affect analysis ports, not sequencer arbitration
Continue practicing

Related questions

UVM ComponentsStart_item and finish_item→UVM ComponentsTiming between start_item and finish_item→
asic.fyi · Learn silicon end to end.info@asic.fyi