Verilog problems / Sequential Design
What you must build
A deeper 3-stage synchronizer for signals that need extra MTBF margin beyond the standard 2-flop chain.
Engineers use “3-Flop CDC Synchronizer” 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.
meta1<=async_in; meta2<=meta1; sync_out<=meta2; gives 3 cycles of latency instead of 2. Stopping one stage short (using meta1 directly as the output) saves a cycle of latency but gives up the extra metastability margin — a real tradeoff, not just a bug.Port contract
The judge instantiates exactly these ports. Extra ports or a different module name fail to elaborate.
| Name | Dir | Width | Description |
|---|---|---|---|
| clk | input | 1 | Destination clock |
| rst | input | 1 | Sync active-high reset |
| async_in | input | 1 | Signal from another clock domain |
| sync_out | output | 1 | async_in, synchronized (3 cycles of latency) |
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 async_in, output reg sync_out ); // Your code here — 3 cascaded flops: meta1 <- async_in, meta2 <- meta1, sync_out <- meta2. endmodule
Why this shows up in interviews
3-Flop CDC Synchronizer sits under Sequential Design (sequential, cdc). Concept: More synchronizer stages exponentially improve mean-time-between-failures at the cost of extra latency: meta1<=async_in; meta2<=meta1; sync_out<=meta2; gives 3 cycles of latency instead of 2. Stopping one stage short (using meta1 directly as the output) saves a cycle of latency but gives up the extra metastability margin — a real tradeoff, not just a bug.
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 3-Flop CDC Synchronizer problem ask for? A deeper 3-stage synchronizer for signals that need extra MTBF margin beyond the standard 2-flop chain. Implement it as Verilog module top_module with the listed ports.
Combinational or sequential?
Is 3-Flop CDC Synchronizer combinational or sequential? Tags: sequential, cdc. 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 3-Flop CDC Synchronizer 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.