3.2.6 · D5CMOS Circuit Design

Question bank — Noise margins (NMH, NML)

2,161 words10 min readBack to topic

Symbol refresher — read this before the traps

Every trap below leans on the same nine symbols. If any of these feels fuzzy, the trap will beat you for the wrong reason. Here they are in plain words, all anchored to one picture.

The VTC (Voltage Transfer Characteristic) is just the graph of against for one inverter. Look at Figure 1: the S-shaped white curve is the VTC. The two points where its slope is exactly (the small amber marks) are, by definition, (left) and (right). Read the output off those points to get and .

Figure — Noise margins (NMH, NML)
Figure — Noise margins (NMH, NML)

True or false — justify

A wider noise margin always means a faster gate.
False. Margins measure static robustness (voltage cushion), not switching speed. A gate with a very sharp, high-gain VTC can have large margins yet be slow if it is heavily loaded — see Fan-out and Loading.
If a gate has V it can absorb exactly 0.9 V of noise on any input without ever failing.
False in spirit. is the worst-case HIGH-side cushion; it only guards a signal that is genuinely HIGH and being pulled down. It says nothing about a LOW signal, which is guarded by .
Making both transistors symmetric () maximises the sum .
False. Symmetry maximises the minimum of the two, not the sum. Skewing can raise one margin while lowering the other; the sum can stay similar, but the weakest link (the min) gets worse.
and depend only on the driver, while and depend only on the receiver.
True. Output levels are what the driving gate guarantees; input thresholds are what the next gate demands. Noise margin couples the two across the wire.
Lowering leaves the noise margins unchanged because everything scales together.
False. Absolute margins shrink roughly with (about each in ideal CMOS), while physical noise sources like coupling do not scale down as neatly — see Power Supply Scaling.
A gate with negative can still work as long as is large.
False. A negative margin means a valid driver LOW already overlaps the receiver's forbidden band, so a LOW can be misread as HIGH even with zero noise. Robustness , so it is broken.
and are chosen by the designer to give convenient margins.
False. They are defined by the (i.e. ) unity-gain points of the actual VTC — they fall out of transistor physics, not preference. See CMOS Inverter VTC.
The noise margins on a datasheet fully describe how much noise a fast gate tolerates at any frequency.
False. are static (DC) margins. At high speed, short spikes of capacitive coupling or kickback can be tolerated even if they briefly exceed the static margin, while sustained ringing can fail below it — dynamic behaviour is a separate story.

Spot the error

", because those are the two output extremes."
Wrong term. HIGH margin must cross the gate boundary to the receiver's input threshold: . Subtracting two outputs never involves the next gate at all.
", by analogy with the HIGH formula."
Sign error — this comes out negative. For a LOW, noise pushes the voltage up, so the receiver limit is the larger number: .
"We pick the slope points because that is where the gate has maximum gain."
Not maximum — maximum is at . The points are where equals exactly one, the break-even boundary between noise being attenuated () and amplified (), as Figure 1 shows.
"For a stored HIGH, noise is dangerous if it pushes the level upward toward ."
Backwards. Pushing a HIGH higher only makes it more clearly a 1. The threat is noise pulling it down toward ; that is what budgets for.
"CMOS has huge margins because its transistors have high gain, so can exceed ."
The output cannot exceed the rail. CMOS margins are large because the swing is rail-to-rail (, ) and the threshold sits near , not because of any over-rail output.
"If everywhere, the gate still restores logic levels, just slowly."
No restoration at all. Restoration needs a region where (so a marginal input is amplified back toward a rail); with everywhere the curve is too flat to push signals to the rails — see Static Gain and Regenerative Property. Margins would collapse.

Why questions

Why does the HIGH margin subtract and not ?
Because a HIGH signal is only ever tested against the receiver's HIGH-recognition floor, — the lowest voltage still read as 1. is the LOW side's business.
Why is overall robustness the minimum of the two margins rather than the average?
A chip fails at its weakest point. The average could look healthy while one side is near zero; the min exposes the real failure threshold — the smaller cushion is the one noise will breach first.
Why must both margins be strictly positive, not merely non-negative?
At exactly zero, the guaranteed output sits on the receiver's threshold with no cushion — any noise at all, or normal manufacturing spread, tips it into misreading.
Why does the SRAM butterfly curve reuse this same margin idea?
A bit-cell is two cross-coupled inverters; its stability is the largest square that fits between the mirrored VTCs, which is a static noise margin of the very same "how much noise before the state flips" flavour — see Static Noise Margin (SRAM butterfly curve).
Why does heavier fan-out erode the margins?
Extra load and leakage pull down and up (the swing degrades from the rails), which directly shrinks both and — see Fan-out and Loading.
Why can't we simply widen the forbidden band to get bigger margins for free?
The forbidden band lives between and (Figure 2), which are fixed by the VTC's slopes. Widening it means changing the transistor design, not relabelling — the physics sets those points.
Why does weakening the PMOS () move down?
The NMOS then wins the pull-down tug-of-war at a lower input voltage, so the output flips earlier and the whole switching point slides toward ground — see CMOS Inverter VTC.

Edge cases

What are the margins if the VTC is a perfectly vertical step at (infinite gain)?
Then and, with rail outputs, , . This is the idealised symmetric case giving each — the theoretical best.
What happens to the margins if the gate has gain everywhere (no crossings exist)?
and become ill-defined and the valid logic ranges collapse; effectively there is no reliable noise margin because the gate never restores levels.
A skewed inverter has pushed very close to ground. Which margin is at risk?
shrinks because its ceiling drops with , while grows — the LOW side becomes the weak link.
What is the noise margin of two gates whose equals the next gate's exactly?
. The system is on the knife-edge — logically it "works" with zero noise but any disturbance fails it, so it is treated as broken in practice.
If a driver's rises above the receiver's (e.g. severe loading), what does signal?
goes negative, meaning a driven LOW already exceeds the largest voltage read as 0 — the receiver may latch it as a 1 with no noise present at all.
Does a symmetric CMOS inverter guarantee equal margins across every input pattern in a real chip?
No — process variation, temperature, and unequal wire coupling make the effective and thresholds drift, so nominal symmetry only gives approximately balanced margins.
How can a fast switching aggressor wire hurt a victim even when its static noise margin is comfortable?
Capacitive coupling ("kickback") injects a brief spike whose height depends on the aggressor's edge rate, not its DC level; a fast edge can momentarily push the victim past or even though a slow signal at the same level would be safe — a dynamic, frequency-dependent margin.
Are static noise margins enough to guarantee a flip-flop never captures a wrong value?
No. Even with perfect voltage margins, a data change too close to the clock edge violates setup/hold timing and can drive the flop into metastability — a valid-voltage failure that noise margins do not cover; it is a timing margin, a separate axis of robustness.

Connections

  • CMOS Inverter VTC — the source of every voltage used here.
  • Static Gain and Regenerative Property — why is required for real margins.
  • Fan-out and Loading — how loading eats the margins.
  • Power Supply Scaling — why lower shrinks the cushions.
  • Static Noise Margin (SRAM butterfly curve) — the same principle for bit-cells.

#flashcards/hardware