G5.9.1 Skew Helps, Skew Hurts

MediumImplementIcarus · browser samples / server checksReview the topic

Recompute setup and hold slack of one path as the capture clock arrives late or early, and as jitter shortens a cycle.

Hardware context: A low-power event counter whose enable was ANDed into its clock, and a clock tree with skew between two flops. Compute setup and hold slack with late and early capture clocks and with jitter.

A clock tree reaches two flip-flops at slightly different times. The timing team asks how much the difference may be in each direction, and how much the clock's jitter costs.

This is an Implement problem with no logic to write. Work out each answer by hand and write it into the answer module as a constant. The first three constants are worked examples and are already correct.

The check compares every constant with the right value and names the first one that is wrong.

Signals in the Timeline

SignalWidthRole
question8input of each check
Full specification
QuantityValue
Clock period800 ps
Clock-to-Q, latest / earliest100 / 70 ps
Setup / hold time50 / 40 ps
Logic propagation / contamination600 / 30 ps
CheckSlack
SetupT + skew − jitter − (t_pcq + t_pd + t_setup)
Hold(t_ccq + t_cd) − (t_hold + skew)
ConstantWhat to write
SETUP_NO_SKEWSetup slack with no skew and no jitter, in ps (800 - 750).
HOLD_NO_SKEWHold slack with no skew, in ps (100 - 40).
SETUP_LATE_40Setup slack when the capture clock arrives 40 ps late, in ps (800 + 40 - 750).
HOLD_LATE_40Hold slack when the capture clock arrives 40 ps late, in ps.
SETUP_EARLY_40Setup slack when the capture clock arrives 40 ps early, in ps.
HOLD_EARLY_40Hold slack when the capture clock arrives 40 ps early, in ps.
MAX_LATE_SKEWThe largest late skew of the capture clock that still meets hold, in ps.
SETUP_JITTER_30Setup slack with no skew and 30 ps of jitter, in ps.
MIN_PERIOD_JITTER_30The shortest clock period that meets setup with no skew and 30 ps of jitter, in ps.

Skew is the capture clock's arrival minus the launch clock's arrival: positive when the capture clock is late. Jitter is cycle-to-cycle jitter: the most one period can be shorter than T. It enters the setup check only. These are exercise numbers.

Examples

Example 1

Worked Example: Setup, No Skew
Input
setup slack with no skew and no jitter, in ps (800 - 750)
Output
setup_no_skew = 50

Arrival 100 + 600 = 700 ps; required 800 - 50 = 750 ps. Slack 50 ps. This constant is already filled in.

Example 2

Worked Example: Hold, No Skew
Input
hold slack with no skew, in ps (100 - 40)
Output
hold_no_skew = 60

Earliest change 70 + 30 = 100 ps after the edge; hold needs 40 ps. Slack 60 ps. This constant is already filled in.

Example 3

Worked Example: Setup, Late Capture Clock
Input
setup slack when the capture clock arrives 40 ps late, in ps (800 + 40 - 750)
Output
setup_late_40 = 90

The capture edge comes at 840 ps, so data may arrive until 790 ps. Slack 90 ps: the late clock helped. This constant is already filled in.

Constraints and Contract

  • Keep the module name answer and the names of the constants.
  • Slacks may be negative.

Hints

Hint 1

A late capture edge gives the data more time to arrive: setup gains the skew. The same late edge must also be held past: hold loses it.

Hint 2

An early capture clock is a negative skew: setup loses, hold gains.

Hint 3

Jitter can only hurt setup. Subtract it from setup slack, and add it to the period you need. Hold is checked at one edge, so it does not see it.

What the grader checks: The check reads nine constants and compares each with a value computed in JavaScript from the formulas in the brief. It cannot see how a value was found. The jitter model is the simple one stated in the brief.

9 checks on Icarus · browser samples / server checks. Run the examples first, then check the full regression. Full checks use the server judge. Downloads contain public samples only. A passing result establishes the tested cases, not a proof for all possible inputs.

See all 2 steps and the final capstone

Report a problem with this page

Your code SystemVerilogSaved locally
Ln 1, Col 1Tab indents · Ctrl/⌘ + Enter runs samples
Not run yet

Worked Example: Setup, No Skew

Input
setup slack with no skew and no jitter, in ps (800 - 750)
Expected output
setup_no_skew = 50

Arrival 100 + 600 = 700 ps; required 800 - 50 = 750 ps. Slack 50 ps. This constant is already filled in.

Run samples executes all 3 public checks. Check all tests runs 9 checks on the server.

Icarus · browser samples / server checks