Verilog problems / Sequential Design
What you must build
Trigger a reset when the supply voltage dips too low — and use two different thresholds for asserting vs. releasing it, so noise near the edge can't chatter the reset line.
Engineers use “Brown-Out Reset 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.
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 | Clock |
| rst_ext | input | 1 | External force-reset input |
| vsense | input | 8 | Sensed supply voltage (arbitrary units) |
| reset_out | output | 1 | 1 while held in brown-out reset |
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_ext, input [7:0] vsense, output reg reset_out ); // Your code here — LOW=100, HIGH=110. Assert reset when vsense<LOW; release only when vsense>=HIGH. endmodule
Why this shows up in interviews
Brown-Out Reset Detector sits under Sequential Design (sequential, power, reset). Concept: A real brown-out detector uses hysteresis: reset asserts when voltage drops below a LOW threshold, but only releases once voltage climbs back above a separate, higher HIGH threshold — the gap between the two thresholds is a noise margin. Using the same threshold for both directions collapses that margin to zero: the moment voltage ticks back above the single threshold, reset releases immediately, even if it's still sitting in what should be the unsafe hysteresis band — exactly the chattering behavior hysteresis exists to prevent.
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 Brown-Out Reset Detector problem ask for? Trigger a reset when the supply voltage dips too low — and use two different thresholds for asserting vs. releasing it, so noise near the edge can't chatter the reset line. Implement it as Verilog module top_module with the listed ports.
Combinational or sequential?
Is Brown-Out Reset Detector combinational or sequential? Tags: sequential, power, reset. 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 Brown-Out Reset 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.