3.2.7 · D3CMOS Circuit Design

Worked examples — Propagation delay and rise - fall times

2,958 words13 min readBack to topic

Before line one, three tiny reminders so no symbol is unearned:

Unit shorthand used everywhere: (femto), (pico), (micro), (kilo).


The scenario matrix

Every problem this topic can throw is one of these cells. The right column names the example that covers it.

# Case class What makes it tricky Covered by
A Plain RC delay (well-behaved) just plug in Ex 1
B Rise/fall vs delay (two conventions on one edge) 50% vs 10–90% mix-up Ex 2
C Constant-current model half-swing charge only Ex 3
D Asymmetric H→L vs L→H (both signs of the edge) Ex 4
E Sizing to match (solve for ) inverse: given target, find geometry Ex 5
F Degenerate: (weak / cut-off transistor) delay ; limiting behaviour Ex 6
G Degenerate: (unloaded gate) delay ; what actually limits it Ex 6
H Real-world word problem (max clock frequency) translate delay → MHz Ex 7
I Exam twist: model disagreement RC vs constant-I give different numbers — which and why Ex 8

Example 1 — Cell A: plain RC delay

Forecast: guess first — is bigger or smaller than ? (It must be smaller: we only wait until half-way, not one full time constant.)

  1. Compute . Why this step? is the single knob that sets the whole timescale; every delay is a pure number times .
  2. Multiply by . Why ? The output falls as ; setting gives , so .
Figure — Propagation delay and rise - fall times

How to read the figure: the cyan curve is the output voltage falling exponentially from the full rail (, the top) toward ground. The horizontal amber dashed line marks the level ; the amber dot is exactly where the curve crosses it. Drop straight down from that dot to the time axis and you read off — notice it lands before the tick, which is our whole forecast made visible. The two white dotted lines at and are there for the next example.

Verify: ✓ (matches the forecast — half-way happens before one full ). Units: ✓.


Example 2 — Cell B: rise/fall vs delay on the same edge

Forecast: which is longer, or ? The fall time watches a longer stretch of the curve (10% to 90%), so predict .

  1. Fall time uses , not . Why ? Going from down to : the time is .
  2. Take the ratio. Why does cancel? Both are the same exponential; the ratio depends only on the voltage levels, never on or . This is a universal fingerprint of RC discharge.

How to read the figure (reuse Fig 1): look again at the two white dotted lines at and . The fall time is the horizontal distance the cyan curve travels between those two lines — a much wider slice of time than the single amber crossing used in Ex 1. Seeing that the span is visibly wider than the span is why .

Verify: ✓ (tiny gap is rounding of and ). Forecast confirmed: .


Example 3 — Cell C: constant-current model

Forecast: the model says falls as a straight line (constant current ⇒ constant slope), not a curve. So we only need the charge to drop the half swing .

  1. Charge to remove for a half swing. Why half? Delay is measured to ; only that much charge must leave before the next gate flips.
  2. Time = charge / current. Why divide? with constant gives — the hose empties the bucket at a fixed rate.
Figure — Propagation delay and rise - fall times

How to read the figure: the amber straight line is the constant-current model — a fixed slope, because a fixed current removes charge at a fixed rate. The cyan dashed curve is the RC exponential for comparison; both are tuned to cross the white dotted line at the same instant (the white dot). The amber arrow highlights that only the upper half of the swing (down to ) counts toward — everything below the decision level is irrelevant to the delay number.

Verify: compact form ✓. Units: ✓.


Example 4 — Cell D: asymmetric H→L and L→H

Forecast: the PMOS is weaker (bigger ), so the rising edge () should be slower. The overall delay is an average, so it lands between the two.

  1. Falling edge (NMOS pulls down). Why ? Output going High→Low is the NMOS discharging .
  2. Rising edge (PMOS pulls up). Why ? Output going Low→High is the PMOS charging from the supply.
  3. Overall gate delay = average of the two edges. Why average? A real signal path sees both transitions in roughly equal proportion, so the representative delay is their mean.

Verify: ratio ✓ (delay tracks resistance exactly). Forecast confirmed: rising edge slower, sits between them.


Example 5 — Cell E: inverse problem, size to match

Forecast: because , to lower the PMOS resistance to match, we must widen it. Predict .

  1. Baseline PMOS resistance at . At equal width, . Why 2×? Half the mobility ⇒ half the current at the same ⇒ double the resistance.
  2. Scale width to hit . Since , we need such that , giving Why this scaling? Doubling width doubles the current-carrying channel, halving resistance — exactly the factor 2 we need to cancel the mobility handicap.
  3. Matched delay per edge. Now , so and . Why the factor here? and are edge times, and (as derived in Ex 2) that span of a pure exponential is — the same logic, now applied to the matched resistance. The line uses because those are delays.

Verify: with , edges are equal ⇒ ✓, forecast ✓. See Logical Effort and Fan-out-of-4 for why this "matched" inverter is the reference for effort calculations.


Example 6 — Cells F & G: the two degenerate limits

Forecast: a dying hose can never empty the bucket (delay blows up); an empty bucket needs no emptying (delay vanishes). Predict and respectively.

  1. Cell F — (transistor cut off / very weak). Why? Zero drive current means no charge ever leaves ; the output never reaches , so the delay is unbounded. Equivalently in the RC view and . A gate whose input never turns it on has no defined delay — it simply does not switch.
  2. Cell G — (unloaded output). Why? No bucket to empty ⇒ nothing to wait for. But physically it is never exactly zero: there is always the transistor's own drain/junction capacitance (its "self-load"). So the true floor is , the intrinsic delay.

Verify (Cell F — carried through with numbers): to show the limit diverges, freeze the numerator by setting (whatever units), so , and shrink by factors of ten:

Each tenfold drop in current multiplies the delay by exactly ten — the sequence grows without bound, so as ✓. Verify (Cell G): ✓. Together these two cells bracket every real answer strictly between and .


Example 7 — Cell H: real-world max-frequency word problem

Forecast: more stages = more total delay = lower max frequency. Five stages of 30 ps is 150 ps total, and frequency is one-over-time, so expect a few gigahertz.

  1. Total path delay = sum of stage delays. Why sum? Signals traverse stages one after another; the lags add linearly along the path.
  2. Max frequency = 1 / (path delay). Why the reciprocal? One clock period must be at least as long as the slowest path so the signal settles before it is sampled; the fastest allowed period is exactly , and .

Verify: ✓ (period times frequency = 1). Sanity: matches the forecast of "a few GHz." (Real chips add setup/hold margins and wire delay, lowering further — see Elmore Delay for distributed-wire timing.)


Example 8 — Cell I: exam twist, the two models disagree

Forecast: the RC model (small-, resistive) and the constant-current model (large-, saturated) describe different phases of the same switch, so their numbers need not match; expect them to be in the same ballpark but not identical.

  1. RC model.
  2. Constant-current model.
  3. Reconcile — which to trust, and why. Why the gap? At the start of the fall the output is near , so is large and the transistor sits in saturation — a nearly constant current — which is exactly the constant-current model's home turf. As the output approaches ground, shrinks and the transistor slides into the resistive (triode) region, which is the RC model's home turf. The takeaway: neither number is "the right answer" — each is exact only in its own regime, and the true delay is a blend. Because is measured only down to (still fairly high ), the transition spends most of the measured interval in saturation, so the constant-current estimate (100 ps) is usually the more trustworthy of the two, and a full SPICE simulation lands between and ps. Rule of thumb for exams: when both are offered and no regime is specified, quote the constant-current value for the delay-to-50% and note the RC value as the fast-limit.

Verify: both share the proportionality : double and both double. Ratio — a fixed factor set only by whether was pinned to the end-of-transition current or the saturation current (CMOS Inverter DC Transfer Characteristic shows where each regime lives on the curve). ✓ Forecast confirmed: same ballpark, not identical.


Recall Self-test across the whole matrix

Which cell needs not ? ::: Cell B — rise/fall time (10–90%); delay (50%) uses . As , what is ? ::: — a non-switching gate has no finite delay (Cell F). Two models give 69 ps and 100 ps — which to trust and why? ::: The constant-current 100 ps, because the transition to 50% stays mostly in saturation; SPICE lands between (Cell I). Path of 5 stages at 30 ps → max clock? ::: (Cell H). To match with , set ::: , halving to equal (Cell E).


Connections