Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • Reading Path
  • CDC/RDC Glossary
  • CDC/RDC Metrics Reference
  • CDC/RDC Interview Prep
  • CDC/RDC Signoff Cheatsheet
  • Clock Domains and Failure Modes8
  • Metastability and Synchronizers16
    • MTBF & Synchronizer Math
    • Two-Flop Synchronizers in Practice
    • Multi-bit CDC Hazards
    • Synchronizer Selection Guide
      • Decision Matrix
      • Slow-to-Fast Crossings
      • Fast-to-Slow Crossings
      • Cost of Each Choice
  • CDC Protocols and Handshakes16
  • Reconvergence and Gray Coding16
  • Reset Domain Crossing16
  • Architecture and Design Rules16
  • CDC Signoff Methodology24
  • RDC Signoff16
  • Debug and Case Studies11
  • CDC and RDC Interview Prep30
  • Capstone: Sign Off a Multi-clock Peripheral4
Loading lesson

‹Synchronizer Selection Guide
  1. Topics
  2. CDC & RDC
  3. Metastability and Synchronizers
  4. Synchronizer Selection Guide
  5. Cost of Each Choice

Part 2 · Metastability and Synchronizers · All levels

Cost of Each Choice

Latency, throughput, area, and verification effort for each pattern, compared qualitatively.

Correctness picks the shortlist; cost picks the winner. The table compares the patterns on the four budgets every crossing spends: latency added, throughput allowed, silicon area, and the effort to verify it.

Pattern

Latency

Throughput

Area and verification

Two-flop synchroniser

2 to 3 destination cycles.

One level change per 2+ cycles.

Two flops; lightest review.

Three-flop synchroniser

One more cycle than two-flop.

Same as two-flop.

One more flop; same checks.

Toggle plus edge detect

2 to 3 slow cycles per event.

One event per latency window.

A toggle flop plus detector; spacing proof needed.

Handshake

A full round trip per word.

One word per round trip.

Control logic both sides; protocol assertions required.

Async FIFO

Pointer sync latency on flags.

Burst rate of the memory.

Memory plus pointers; depth, reset, and flag verification.

Load pulse with held data

Pulse sync latency per write.

Rare writes only.

Holding logic; hold-window argument per crossing.

Dual-clock RAM

Synchroniser latency on handover.

Memory bandwidth.

A macro plus ownership proof; heaviest review.

How to use the table

Match the data rate to the throughput column first: streams need FIFOs or RAM, occasional words fit handshakes, rare settings fit load pulses. Then check latency against the protocol budget, remembering each extra synchroniser stage adds a cycle in each direction of a handshake loop. Area decides last, because a cheap pattern with the wrong throughput is not a saving.

Verification effort deserves equal weight with silicon: a handshake without protocol assertions, a FIFO without a depth argument, or shared RAM without an ownership rule will each cost more in signoff debate than a slightly larger but self-evidently correct structure.

Tip

When two patterns both meet throughput, prefer the one whose safety argument fits in one sentence. Reviewers, and your future self, will thank you at waiver time.

Check yourself A handshake crosses a word that must sustain one transfer every four slow cycles, and the round trip is six cycles. What follows?

The handshake cannot meet the rate: one word per six cycles falls short of one per four. Move to an async FIFO, which pipelines words at memory bandwidth.

Check yourself Why does adding a third flop to a handshake synchroniser cost more latency than adding it to a level crossing?

In a handshake loop the extra cycle delays every transfer in both directions, compounding per word. On a plain level it is a one-time two-to-three-cycle delivery delay.

Related topics

  • Decision Matrix

  • Glossary

Previous

30 / 179

Next: CDC Protocols and Handshakes

Up next

Up nextCDC Protocols and Handshakes

Sign in to save progress

Practice this lessonReport an error

See also

  • Decision Matrix
  • Slow-to-Fast Crossings