easy 10 pts Solved

BCD Digit Adder

Add two BCD digits (0-9) plus a carry-in and produce a valid BCD digit result — binary addition alone isn't enough once the sum exceeds 9.

Verilog problems / Combinational Design

What you must build

Add two BCD digits (0-9) plus a carry-in and produce a valid BCD digit result — binary addition alone isn't enough once the sum exceeds 9.

Engineers use “BCD Digit Adder” 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: First add normally in binary: bin_sum = a + b + cin. If that exceeds 9, it's not a valid BCD digit — add 6 to skip over the 6 unused 4-bit codes (10-15) and land back on a valid digit with a decimal carry: cout = (bin_sum > 9); corrected = cout ? bin_sum+6 : bin_sum;.

Port contract

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

NameDirWidthDescription
ainput4BCD digit, 0-9
binput4BCD digit, 0-9
cininput1Carry in
sumoutput4Result BCD digit
coutoutput1Decimal carry out

How to approach this kata

This is a medium kata: you will need sequential logic or a small FSM. Decide what is registered versus combinational before you type. Reset polarity and clock edge must match the spec; the judge will fail you on the first mismatched cycle.

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] a,
  input  [3:0] b,
  input        cin,
  output [3:0] sum,
  output       cout
);

  // Your code here — binary add, then add 6 and set cout if the result exceeds 9.

endmodule

Why this shows up in interviews

BCD Digit Adder sits under Combinational Design (combinational, arithmetic). Concept: First add normally in binary: bin_sum = a + b + cin . If that exceeds 9, it's not a valid BCD digit — add 6 to skip over the 6 unused 4-bit codes (10-15) and land back on a valid digit with a decimal carry: cout = (bin_sum > 9); corrected = cout ? bin_sum+6 : bin_sum; .

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 Adder problem ask for? Add two BCD digits (0-9) plus a carry-in and produce a valid BCD digit result — binary addition alone isn't enough once the sum exceeds 9. Implement it as Verilog module top_module with the listed ports.

Combinational or sequential?

Is BCD Digit Adder 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 Adder 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.