Part of Curriculum: CDC, RDC and Low-Power RTL (Module 8: Async-FIFO Empty Flag Synchronization)
View Full Roadmap →
Level 7 Hard 50 pts ✓ Solved

Async-FIFO Empty Flag Synchronizer

Sequential Design · sequential, cdc, protocol

Synchronize a Gray-coded write pointer into the read domain and compare it against the local read pointer to generate a reliable empty flag — the core of every async FIFO.

Write a synthesizable Verilog module named top_module matching the ports below exactly.
📐 Circuit Schematic Diagram
SRC REGDOMAIN ASYNC 1METASTABLESYNC 2RESOLVEDDOMAIN A (clk_src)DOMAIN B (clk_dst)wptr_gray_in[3:0]empty
⚡ Timing & Synthesizability Constraints

Timing Contract: Strict synchronous timing aligned to posedge clk or zero-delay combinational propagation.

RTL Constraints: Synthesizable Verilog-2001. No # delays in synthesizable RTL.

Concept: An async FIFO's write pointer lives in the write clock domain but the empty flag is needed in the read domain, so the pointer must cross safely — Gray coding ensures only one bit ever changes per increment, so even a partially-synchronized value during a transition is never wildly wrong. Double-flop the incoming Gray pointer (meta, then wptr_gray_sync), then compare it against the local read pointer: empty <= (wptr_gray_sync == rptr_gray). Comparing the raw unsynchronized pointer directly against the local one skips the synchronizer chain entirely, reintroducing metastability risk into the empty flag.
NameDirWidthDescription
clkinput1Read-domain clock
rstinput1Sync active-high reset (empty=1)
wptr_gray_ininput4Gray-coded write pointer from the write domain
rptr_grayinput4Local Gray-coded read pointer (already in this domain)
emptyoutput11 when the synchronized write pointer matches the read pointer
Expected Waveform (Golden Timing Contract)
Verilog-2001 / SV Saved
Font: |
// Click Run Tests (or press Ctrl+Enter) to compile your RTL and simulate against hidden testbenches.
Simulation Timing Diagram (VCD Waveform)
100%
No simulation waveform yet. Run tests to simulate and generate VCD traces.
No compilation run yet. Syntax warnings and elaboration messages will appear here.
No simulation output yet. Raw stdout from vvp will appear here.

RTL Problems / Level 7 · Sequential Design

What You Will Learn

By solving Async-FIFO Empty Flag Synchronizer, you will acquire core industry skills:

  • Synthesizable hardware modeling in standard Verilog-2001 / SystemVerilog.
  • Correct handling of interface port contracts, edge-triggered clocks, and active-low/high resets.
  • Simulation waveform interpretation and debugging using timing diagrams (VCD traces).
  • Architectural avoidance of timing violations, glitching hazards, and synthesis warnings.

Problem Statement & Requirements

Synchronize a Gray-coded write pointer into the read domain and compare it against the local read pointer to generate a reliable empty flag — the core of every async FIFO.

Hardware design teams at leading semiconductor firms evaluate these exact port contracts, race-condition assertions, and corner cases during technical design reviews and ASIC engineer interviews.

Concept: An async FIFO's write pointer lives in the write clock domain but the empty flag is needed in the read domain, so the pointer must cross safely — Gray coding ensures only one bit ever changes per increment, so even a partially-synchronized value during a transition is never wildly wrong. Double-flop the incoming Gray pointer (meta, then wptr_gray_sync), then compare it against the local read pointer: empty <= (wptr_gray_sync == rptr_gray). Comparing the raw unsynchronized pointer directly against the local one skips the synchronizer chain entirely, reintroducing metastability risk into the empty flag.

Port List & Interface Timing

The hidden testbench instantiates top_module. Module port names and bit-widths must match the interface contract exactly:

NameDirWidthDescription
clkinput1Read-domain clock
rstinput1Sync active-high reset (empty=1)
wptr_gray_ininput4Gray-coded write pointer from the write domain
rptr_grayinput4Local Gray-coded read pointer (already in this domain)
emptyoutput11 when the synchronized write pointer matches the read pointer

Timing Constraints & Synthesizable RTL Rules

⚡ Synthesizable Implementation Guidelines

Timing Contract: Strict synchronous timing aligned to posedge clk or zero-delay combinational propagation.

Synthesis Constraints: Synthesizable Verilog-2001. No # delays in synthesizable RTL.

Starter RTL Code

module top_module(
  input  clk,
  input  rst,
  input  [3:0] wptr_gray_in,
  input  [3:0] rptr_gray,
  output reg empty
);

  // Your code here — 2-flop sync wptr_gray_in, then empty = (synced value == rptr_gray).

endmodule
Advertisement

Related RTL Problems in Level 7

  • Async-Assert / Sync-Deassert Reset — Assert reset the instant it goes active, but only release it once it has been clean for 2 clock edges — the standard reset architecture for any real design.
  • 3-Flop CDC Synchronizer — A deeper 3-stage synchronizer for signals that need extra MTBF margin beyond the standard 2-flop chain.
  • Synchronized Rising-Edge Detector — Safely synchronize an asynchronous level signal, then produce a clean single-cycle pulse the moment it rises in the local clock domain.

Frequently Asked Questions

What does Async-FIFO Empty Flag Synchronizer require?

Synchronize a Gray-coded write pointer into the read domain and compare it against the local read pointer to generate a reliable empty flag — the core of every async FIFO. Implement it as Verilog module top_module matching the listed ports.

Is this design combinational or sequential?

Tags: sequential, cdc, protocol. If a clock signal is present in the port table, implement it as sequential logic; otherwise, use continuous assignments or combinational blocks.

How is my solution graded?

A hidden SystemVerilog testbench simulates your module in the cloud judge. You pass when all directed corner cases match the golden model and the VCD timing waveform matches the contract.

How does this challenge help with semiconductor interviews?

Technical interviewers at NVIDIA, Qualcomm, Apple, and Intel routinely ask candidates to code, debug, and explain the timing waveforms of Async-FIFO Empty Flag Synchronizer to assess real-world synthesizability and race-condition awareness.

Advertisement