easy 10 pts Solved

BCD Digit Validator

Flag whether a 4-bit nibble is a legal BCD digit (0-9) or one of the six unused patterns (10-15) — the guard every BCD datapath needs before trusting its input.

Verilog problems / Combinational Design

What you must build

Flag whether a 4-bit nibble is a legal BCD digit (0-9) or one of the six unused patterns (10-15) — the guard every BCD datapath needs before trusting its input.

Engineers use “BCD Digit Validator” 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.

Concept: A 4-bit nibble can represent 0-15, but BCD only uses 0-9 — the top six codes (1010-1111) are illegal. The check is a plain magnitude comparison, valid = (nibble <= 9). A tempting shortcut, valid = ~nibble[3] ("valid if the top bit is 0"), looks like it works for small numbers but wrongly rejects 8 and 9 (both have their MSB set) while wrongly accepting nothing above 7 — it's checking the wrong thing entirely.

Port contract

The judge instantiates exactly these ports. Extra ports or a different module name fail to elaborate.

NameDirWidthDescription
nibbleinput44-bit value to check
validoutput11 if nibble is 0-9 (a legal BCD digit), 0 otherwise

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] nibble,
  output valid
);

  // Your code here — valid = (nibble <= 9).

endmodule

Why this shows up in interviews

BCD Digit Validator sits under Combinational Design (combinational, arithmetic). Concept: A 4-bit nibble can represent 0-15, but BCD only uses 0-9 — the top six codes (1010-1111) are illegal. The check is a plain magnitude comparison, valid = (nibble <= 9) . A tempting shortcut, valid = ~nibble[3] ("valid if the top bit is 0"), looks like it works for small numbers but wrongly rejects 8 and 9 (both have their MSB set) while wrongly accepting nothing above 7 — it's checking the wrong thing entirely.

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 BCD Digit Validator problem ask for? Flag whether a 4-bit nibble is a legal BCD digit (0-9) or one of the six unused patterns (10-15) — the guard every BCD datapath needs before trusting its input. Implement it as Verilog module top_module with the listed ports.

Combinational or sequential?

Is BCD Digit Validator combinational or sequential? Tags: combinational, arithmetic. 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 BCD Digit Validator 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.

Write a module named top_module matching the ports below exactly.
Expected waveform
Your solution
Judge output
// Output appears after you run tests.