A worked mechanism
A faster clock does not repair an early transition.
Use one hypothetical same-clock path with zero skew: earliest data arrival 0.06 ns and hold requirement 0.08 ns.
Original clock
Hold slack −0.02 ns
A 1.00 ns period leaves the same-edge hold inequality unchanged.
Slower clock
Hold slack −0.02 ns
A 2.00 ns period moves the next setup edge, not the current hold edge.
Add minimum delay
Hold slack +0.01 ns
An illustrative 0.03 ns delay raises earliest arrival to 0.09 ns.
Recheck maximum delay
No free timing fix
The inserted structure also affects setup and physical constraints.
Work it through
Two boundaries, two remedies
Hold slack = 0.06 − 0.08 = −0.02 ns. Changing period does not enter that expression. Adding 0.03 ns changes it to 0.09 − 0.08.
The repair is provisional until all setup and hold views pass.
Watch for this
A fixed illustrative delay is not a characterized delay across PVT; use the actual cell and route arcs for signoff.
Check your reasoning
Inspect min-delay arrival, same-edge requirement, max-delay regression, slew, capacitance, and both clock paths.
Check your understanding
Questions to reason through.
What is the practical difference between setup and hold?
Setup is a maximum-delay check: old-cycle data must reach the capture register before its active edge. Hold is a minimum-delay check: new-cycle data must not reach that register too soon after the edge. Setup is helped by a longer period or faster data path; hold usually needs added data delay or improved skew.
Put it into practice
Explain the decision behind the design.
Practice Digital Design in the question bankContinue the learning path

