Every synchroniser argument rests on two facts: a flop sampling a changing input can hover before resolving, and the chance it is still unresolved falls exponentially with the settling time it is given. This topic builds that argument from the mechanism to the stage-count decision.
Lesson | After it you can... |
|---|---|
Explain the setup/hold window and why resolution is probabilistic. | |
State the MTBF model and the role of each term. | |
Work the arithmetic on illustrative parameters and show what a third stage buys. | |
Choose a stage count and say what extra stages do not fix. |
Read them in order: mechanism first, then the model, then the numbers, then the decision.
Because the chance the flop is still unresolved falls exponentially with settling time, so one idle period buys an enormous reliability margin.