BeginnerQuestion 77 of 95Source: Synopsys PrimeTime User Guide: Operating Conditions

What is a timing corner, and how is it different from a timing mode?

From PDVerse STA Mentor Guide · pdVerse Mentor Guide

By Tabish Iqbal · 9+ Years VLSI Physical Design Experience

Short Answer

A timing corner describes a set of physical operating conditions the silicon might actually see, such as process variation, supply voltage, and temperature, often shortened to PVT. A timing mode, by contrast, describes a functional operating state the design's logic is in, such as scan test or a low-power state, and is about which paths and constraints are active rather than how fast the silicon physically runs. A full signoff scenario needs both: which mode the logic is in, and which corner's physical conditions apply for that check.

A 2x2 grid of PVT corner combinations (slow/fast process x low/high voltage-temperature) with setup-worst and hold-worst corners labeled at opposite corners — Technical Reference DiagramWhat is a timing corner, and how is it different from a timing mode?

Technical Explanation

A corner is a property of the silicon; a mode is a property of what the logic is doing.

Process variation describes whether a manufactured chip came out faster or slower than target, labeled with letters like SS (slow-slow) or FF (fast-fast) for NMOS/PMOS speed.
Voltage and temperature are added to process to form a full PVT corner: slow process, low voltage, high temperature gives the slowest, most setup-critical timing; fast process, high voltage, low temperature gives the fastest, most hold-critical timing.
set_operating_conditions (PT) selects which PVT library data the tool uses, since vendors characterize cells at multiple PVT points and ship separate Liberty data for each.
A full signoff matrix multiplies modes by corners, so 3 modes and 4 corners need at least 12 combined scenarios, unless some combinations are known to be irrelevant.
Because a corner and a mode describe different things, the same corner combines with every mode, and the same mode gets checked across every corner.

Common Mistake

The Trap: treating "worst corner" as one fixed answer for every check, instead of recognizing setup and hold are usually stressed by opposite ends of the PVT range.

The slow-process, low-voltage, high-temperature corner stresses setup hardest; the fast-process, high-voltage, low-temperature corner stresses hold hardest.
Checking only one "worst-case" corner leaves the other check type unverified, even though it looks thorough.

Follow-up Question & Model Response

Given that more corners means more signoff runtime, how do teams keep the total scenario count manageable?

Candidate Model Response: Teams start from the corners their library vendor documents as intended signoff corners, then add any their own operating spec requires, such as a wide temperature range for an automotive part. Some also run a broader corner sweep once, early in the design, to confirm the smaller regular set actually captures the true worst case for setup, hold, and DRC, trusting it only after that check passes. This turns an assumption into a validated one.

Practical Example

A design specifies 0.81V to 0.99V and -40C to 125C across SS and FF process corners. Checking only the nominal 0.9V, 25C corner reports zero setup violations, but the SS corner at 0.81V/125C reveals 40 real setup violations, and the FF corner at 0.99V/-40C reveals 15 real hold violations.

Complete STA Handbook