A worked mechanism
A four-phase handshake must return to idle before reuse.
This is a non-pipelined, active-high request/acknowledge teaching protocol. Source data remains stable throughout the exchange.
Publish request
req=1 · ack=0
The source holds word 0xA5 and raises request.
Capture and acknowledge
req=1 · ack=1
After synchronized request and data settling, the destination captures once and raises acknowledgement.
Withdraw request
req=0 · ack=1
After acknowledgement crosses back, the source lowers request while retaining the word for this conservative contract.
Return to idle
req=0 · ack=0
After request withdrawal crosses, the destination lowers acknowledgement; its return permits the next transfer.
Work it through
An early second word
Replacing 0xA5 with 0x5A before the round trip completes can make ownership of the destination sample ambiguous.
Only a completed return-to-idle exchange makes this instance available again.
Watch for this
A two-phase toggle protocol has different state rules. Do not combine its reuse rule with this four-phase sequence.
Check your reasoning
Count one destination capture per accepted request and assert held data, synchronized controls, reset convergence, and no new request while busy.
Check your understanding
Questions to reason through.
Why does a two-flop synchronizer reduce risk instead of eliminate it?
The first destination flop can still enter metastability when an asynchronous transition violates its sampling aperture. The second stage gives that analog state additional resolution time, which improves MTBF exponentially, but the probability is never mathematically zero and depends on library parameters, placement, clock rate, data-toggle rate, and available resolution time.
Why is synchronizing every bit of a bus independently unsafe?
Each bit can resolve on a different destination edge, so the receiver may observe a word that never existed at the source. Preserve coherence with a bundled-data handshake, Gray-coded control state, source-synchronous transfer, or asynchronous FIFO selected for the payload and throughput contract.
Put it into practice
Explain the decision behind the design.
- Choose a CDC strategyMatch the transfer mechanism to payload semantics.→
- Model an asynchronous FIFOReason about Gray pointers, full/empty, and reset convergence.→
- Check clock gatingProve glitch-free enable capture and stopped-clock behavior.→
Continue the learning path

