Verilog problems / Combinational Design
What you must build
Grant exactly one of four requesters at a time, always favoring the highest-index request when several arrive together.
Engineers use “Fixed-Priority Arbiter” as a building block in combinational design. Interviewers ask for the same ports and the same corner cases this judge covers. Completing it in the browser is the same skill as writing synthesizable RTL at work, minus the EDA license.
req[3]), and only fall through to lower ones if it is idle. grant = req[3]?4'b1000:req[2]?4'b0100:req[1]?4'b0010:req[0]?4'b0001:4'b0000; guarantees only one grant bit is ever set, with bit 3 always winning ties.Port contract
The judge instantiates exactly these ports. Extra ports or a different module name fail to elaborate.
| Name | Dir | Width | Description |
|---|---|---|---|
| req | input | 4 | Request lines, one per requester |
| grant | output | 4 | One-hot grant, req[3] has highest priority |
How to approach this kata
This is an introductory kata. Prefer a clear continuous assignment or a small combinational always block. Name the module top_module and keep the port list identical to the table — the hidden testbench instantiates that name.
Hidden tests instantiate top_module, drive the ports, and compare every sample against a golden model. They do not grade coding style. They do grade X/Z, off-by-one counters, and ignoring enables. Sign in only when you want the run saved on the leaderboard — the specification below is public.
Starter shape
Copy this skeleton into the editor (or press Reset starter). Fill the body; do not rename the module.
module top_module( input [3:0] req, output [3:0] grant ); // Your code here — grant the highest-index active request; grant=0 if no requests. endmodule
Why this shows up in interviews
Fixed-Priority Arbiter sits under Combinational Design (combinational, encoder). Concept: A fixed-priority arbiter is a nested-priority mux: check the highest-priority request first ( req[3] ), and only fall through to lower ones if it is idle. grant = req[3]?4'b1000:req[2]?4'b0100:req[1]?4'b0010:req[0]?4'b0001:4'b0000; guarantees only one grant bit is ever set, with bit 3 always winning ties.
A passing solution is synthesizable intent: no delays in the DUT, no initial blocks inside top_module, and no reference to testbench tasks. Use blocking assignments only in combinational always blocks; use non-blocking for registers clocked by clk.
Related problems
- 2-to-1 Multiplexer — Select between two 1-bit inputs using sel. When sel=0 output a; when sel=1 output b.
- 1-Bit Full Adder — Compute sum and carry-out for a + b + cin.
- 4-to-1 Multiplexer — Select one of four 1-bit inputs using a 2-bit sel. sel=00→in0, 01→in1, 10→in2, 11→in3.
- 4-to-2 Priority Encoder — Output the index of the highest-priority (MSB-most) set bit in a 4-bit input, plus a valid flag when any bit is set.
FAQ
What does this problem require?
What does the Fixed-Priority Arbiter problem ask for? Grant exactly one of four requesters at a time, always favoring the highest-index request when several arrive together. Implement it as Verilog module top_module with the listed ports.
Combinational or sequential?
Is Fixed-Priority Arbiter combinational or sequential? Tags: combinational, encoder. Follow the clock/reset ports if they appear in the table; if there is no clock, use continuous assignment or combinational always @(*).
How does the auto-grader work?
How is Fixed-Priority Arbiter graded? A hidden SystemVerilog/Verilog testbench in the EcrioniX judge simulates your module in the browser. You pass when every directed vector matches, including the waveform contract shown on this page.