STA Mastery · All levels

ECO Physical vs Logical: Design Space

Design Space for ECO Physical vs Logical.

Design space exploration

For ECO Physical vs Logical, closure options trade margin, schedule, and regression risk.

Option A — conservative

  • Conservative margin: helps safe signoff

  • Risk: over-pessimism, area/power

  • Validate with: first silicon

Option B — balanced

  • Balanced derate: helps reasonable margin

  • Risk: needs approval

  • Validate with: mature node

Option C — aggressive ECO

  • Aggressive ECO: helps fast WNS gain

  • Risk: hold/SI regressions

  • Validate with: late schedule

Option D — RTL restructure

  • RTL restructure: helps structural fix

  • Risk: schedule hit

  • Validate with: chronic paths

diagram
DESIGN SPACE — ECO Physical vs Logical
margin <-> performance <-> schedule
pick based on ECO turnaround time, leakage delta, area delta, timing recovery on product scenarios

Design pitfalls

  • ECO without regression matrix

  • Constraint change without audit

Tradeoff curve

diagram
BEFORE / AFTER ECO — ECO Physical vs Logical

WNS (ps)
  0 |                    --- target
-50 |    ● regressed
-80 |         ● before ECO
-20 |              ● after ECO
    +-------------------------------> ECO iteration
Prove setup AND hold moved safely.

STA deep dive

ECO without regression is a coin flip.

Concept diagram

diagram
ECO LOOP

failing path -> fix -> setup check -> hold check -> SI -> MMMC matrix

Metric graph

diagram
ECO PROGRESS

WNS
 0 |              o target
-50|        o
-100|   o baseline
    +-----------------> ECO #

Reports and artifacts

  • pre/post WNS

  • hold delta

  • leakage delta

  • ECO ticket log

Mini case study

48-hour tapeout crunch: VT swap fixed setup; hold fixed with route on short path — order mattered.

Debug branches

  • Never ship setup-only proof

  • Logical ECO needs equivalence

Senior review question

Ask: what corner/mode/view proves this topic is closed or failing?

Key takeaways

  • State corner, mode, view, and database tag with every slack claim.

  • Run setup and hold plus MMMC regression after every ECO.

Common pitfalls

  • Comparing STA runs with different SPEF or SDC tags.

  • Broad false_path to green-wash violations.

  • Setup-only ECO without hold check.

Principal STA review addendum

Logical ECO changes netlist; physical ECO changes placement/routing; each has different cost, risk, and regression surface.

Metric: ECO turnaround time, leakage delta, area delta, timing recovery