A worked mechanism
Normalize the clock origin before comparing timing reports.
Reconcile the existing signoff fixture in absolute time and in launch-clock-relative time. Both must give the same slack.
Absolute arrival
1.06 ns
Launch latency 0.10 + tCQ 0.09 + data 0.87.
Absolute requirement
0.88 ns
Period 0.85 + capture latency 0.14 − setup 0.06 − uncertainty 0.05.
Relative pair
Same reference shift
Subtract launch latency 0.10 from both terms: arrival 0.96, requirement 0.78.
Invariant result
Slack −0.18 ns
0.88 − 1.06 = 0.78 − 0.96.
Work it through
A report mismatch that is only a ruler mismatch
Comparing absolute arrival 1.06 ns against relative requirement 0.78 ns invents another 0.10 ns of failure.
Subtract a reference from both sides or from neither side.
Watch for this
Clock uncertainty, CPPR, and edge pairing must still match; a common-origin subtraction cannot reconcile different analysis views.
Check your reasoning
Annotate each report’s time origin, launch/capture latencies, clock edge, setup arc, uncertainty, and data increments.
Check your understanding
Questions to reason through.
Why can positive capture skew help setup but hurt hold?
A later capture clock gives the maximum-delay path more time before the next capture edge, increasing setup margin. The same later edge makes it easier for the earliest new data to reach the destination too soon relative to that capture event, reducing hold margin. Useful skew is therefore a coupled optimization, not free setup slack.
Why is a clean pre-route timing report not final evidence?
Before placement and routing, net delays, congestion, coupling, and clock-tree latency are estimated. Signoff uses extracted interconnect, propagated clocks, variation and uncertainty models, and the required mode/corner combinations. Early timing is valuable for direction, but only the implemented timing model represents the final physical path.
Put it into practice
Explain the decision behind the design.
- Calculate maximum frequencyUse a setup path with skew and uncertainty correctly.→
- Reason about capture skewTrack opposite effects on setup and hold.→
Continue the learning path

