easy 10 pts Solved

Registered Change Detector

Flag combinationally, in the very same cycle, whenever the input differs from its last-registered value.

Verilog problems / Sequential Design

What you must build

Flag combinationally, in the very same cycle, whenever the input differs from its last-registered value.

Engineers use “Registered Change Detector” as a building block in sequential 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: Register the previous value on every clock edge (prev <= data), then compare it combinationally against the live input: assign changed = (data != prev). Because the comparison is combinational, changed reacts the instant data moves — even between clock edges — rather than waiting a cycle like a registered comparison would.

Port contract

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

NameDirWidthDescription
clkinput1Clock
rstinput1Sync active-high reset (prev=0)
datainput4Live input value
changedoutput11 whenever data differs from its last-registered value

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  clk,
  input  rst,
  input  [3:0] data,
  output changed
);

  // Your code here — register the previous data value, then compare combinationally against the live input.

endmodule

Why this shows up in interviews

Registered Change Detector sits under Sequential Design (sequential, edge-detect). Concept: Register the previous value on every clock edge ( prev <= data ), then compare it combinationally against the live input: assign changed = (data != prev) . Because the comparison is combinational, changed reacts the instant data moves — even between clock edges — rather than waiting a cycle like a registered comparison would.

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

  • D Flip-Flop with Asynchronous Reset — Standard D flip-flop with an active-low asynchronous reset. Reset clears q immediately, without waiting for a clock edge.
  • 4-Bit Shift Register (SIPO) — Serial-in, parallel-out shift register. Each clock, shift left and load sin into the LSB. Sync active-high reset clears q.
  • JK Flip-Flop — The flip-flop with no forbidden state: j=k=1 toggles instead of racing. Classic building block for counters.
  • 4-Bit Up/Down Counter — A synchronous counter that increments or decrements each clock edge depending on a direction input, with a synchronous reset.

FAQ

What does this problem require?

What does the Registered Change Detector problem ask for? Flag combinationally, in the very same cycle, whenever the input differs from its last-registered value. Implement it as Verilog module top_module with the listed ports.

Combinational or sequential?

Is Registered Change Detector combinational or sequential? Tags: sequential, edge-detect. 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 Registered Change Detector 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.