Part of Curriculum: CDC, RDC and Low-Power RTL (Module 1: Sequential Design)
View Full Roadmap →
Level 7 Hard 50 pts ✓ Solved

Toggle-Based Pulse Synchronizer

Sequential Design · sequential, cdc

Cross a single-cycle pulse safely between clock domains by toggle-encoding it — a plain 2-flop level synchronizer would simply miss it if the destination clock is slower.

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)tog_inpulse_out
⚡ 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: A pulse from another domain can't be trusted to survive a plain level synchronizer, since a fast pulse can come and go between destination clock edges. Toggle-encoding fixes this: the source flips a toggle bit for every pulse instead of pulsing directly (that flip happens upstream and is assumed already done here — tog_in is the toggled signal). The destination double-flops that toggle, then XORs two consecutive synchronized samples: pulse_out <= sync1 ^ sync2. Because a toggle only ever changes state (never returns to a matching value on its own), this reconstructs exactly one clean pulse per source event, no matter how the clocks relate. Using AND instead of XOR misses every toggle-back-to-0 transition.
NameDirWidthDescription
clkinput1Destination clock
rstinput1Sync active-high reset
tog_ininput1Toggle-encoded pulse signal from another domain
pulse_outoutput1Pulses for 1 cycle on every toggle transition
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 Toggle-Based Pulse 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

Cross a single-cycle pulse safely between clock domains by toggle-encoding it — a plain 2-flop level synchronizer would simply miss it if the destination clock is slower.

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: A pulse from another domain can't be trusted to survive a plain level synchronizer, since a fast pulse can come and go between destination clock edges. Toggle-encoding fixes this: the source flips a toggle bit for every pulse instead of pulsing directly (that flip happens upstream and is assumed already done here — tog_in is the toggled signal). The destination double-flops that toggle, then XORs two consecutive synchronized samples: pulse_out <= sync1 ^ sync2. Because a toggle only ever changes state (never returns to a matching value on its own), this reconstructs exactly one clean pulse per source event, no matter how the clocks relate. Using AND instead of XOR misses every toggle-back-to-0 transition.

Port List & Interface Timing

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

NameDirWidthDescription
clkinput1Destination clock
rstinput1Sync active-high reset
tog_ininput1Toggle-encoded pulse signal from another domain
pulse_outoutput1Pulses for 1 cycle on every toggle transition

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  tog_in,
  output reg pulse_out
);

  // Your code here — 2-flop synchronize tog_in, then XOR consecutive synced samples to regenerate a pulse.

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 Toggle-Based Pulse Synchronizer require?

Cross a single-cycle pulse safely between clock domains by toggle-encoding it — a plain 2-flop level synchronizer would simply miss it if the destination clock is slower. Implement it as Verilog module top_module matching the listed ports.

Is this design combinational or sequential?

Tags: sequential, cdc. 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 Toggle-Based Pulse Synchronizer to assess real-world synthesizability and race-condition awareness.

Advertisement