Verilog problems / Sequential Design
What you must build
Detect the two conditions that frame every I2C transaction: SDA falling while SCL is high (START) and SDA rising while SCL is high (STOP) — the one rule that makes I2C's bus protocol work at all.
Engineers use “I2C Start/Stop Condition 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.
start <= scl && scl_prev && sda_prev && !sda. Swapping which edge means start and which means stop is a genuinely easy mix-up (both rules look almost identical at a glance) — and it inverts the meaning of every transaction boundary in the bus trace.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 | Sampling clock (oversamples the bus) |
| rst | input | 1 | Sync active-high reset |
| sda | input | 1 | I2C data line |
| scl | input | 1 | I2C clock line |
| start_detected | output | 1 | Pulses for 1 cycle on a START condition |
| stop_detected | output | 1 | Pulses for 1 cycle on a STOP condition |
How to approach this kata
This is a hard kata. Sketch the state bits and the illegal overlaps (full/empty, wrap, simultaneous enable) on paper first. A design that “usually works” in your head will fail a directed corner in the hidden tests.
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 sda, input scl, output reg start_detected, output reg stop_detected ); // Your code here — register sda/scl; start=SDA falls while SCL held high; stop=SDA rises while SCL held high. endmodule
Why this shows up in interviews
I2C Start/Stop Condition Detector sits under Sequential Design (sequential, protocol, i2c). Concept: I2C is unique among serial buses: data (SDA) is only allowed to change while the clock (SCL) is low — every SDA transition while SCL is high is a special framing signal, not a data bit. Falling SDA while SCL stays high marks START; rising SDA while SCL stays high marks STOP. Detecting this needs registered previous samples of both signals: start <= scl && scl_prev && sda_prev && !sda . Swapping which edge means start and which means stop is a genuinely easy mix-up (both rules look almost identical at a glance) — and it inverts the meaning of every transaction boundary in the bus trace.
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 I2C Start/Stop Condition Detector problem ask for? Detect the two conditions that frame every I2C transaction: SDA falling while SCL is high (START) and SDA rising while SCL is high (STOP) — the one rule that makes I2C's bus protocol work at all. Implement it as Verilog module top_module with the listed ports.
Combinational or sequential?
Is I2C Start/Stop Condition Detector combinational or sequential? Tags: sequential, protocol, i2c. 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 I2C Start/Stop Condition 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.