A worked mechanism
The constraint must follow the destination enable.
For this same-clock two-cycle example, data launches at C0 and the architectural enable prohibits capture at C1.
C0 · launch
Launch boundary
The source launches one value that must survive until its permitted capture.
C1 · disabled
capture_en = 0
The destination enable is false. This missing capture must be guaranteed by function.
C2 · enabled
capture_en = 1
The destination may capture the result after two periods.
Audit both checks
setup 2 · hold 1
The setup exception moves capture to C2; the paired hold correction preserves the intended C0 minimum-delay check.
Work it through
Break the enabling assumption
If a legal mode enables capture at C1, the two-cycle path is not justified for that mode even if STA reports positive slack at C2.
Prove the disabled C1 capture before accepting the exception.
Watch for this
The N/N−1 command pair shown is for identical-clock edge conventions; different clock ratios may need -start or -end.
Check your reasoning
Link an enable property or formal reachability result to the exact constrained endpoints, modes, and reported launch/capture edges.
Check your understanding
Questions to reason through.
How is a false path different from a multicycle path?
A false path cannot be sensitized in the defined operating modes and is excluded from timing. A multicycle path is real and must work, but the design deliberately allows more than one clock cycle. Calling a slow real path false hides a functional timing failure.
Put it into practice
Explain the decision behind the design.
Practice Digital Design in the question bankContinue the learning path

