TO Be coming

Nov 17, 2026

Functional Safety - automotive Safety Integrity Level

Automotive Functional Safety (FuSa): UPF, RTL, Synthesis & Physical Design Deep Dive

Automotive Functional Safety (FuSa): The Complete Deep Dive

From ISO 26262 to UPF, RTL, Synthesis, Timing, and Physical Design — with the exact constraints you need to give.

ISO 26262 ASIL UPF FFI / DFA Power-Aware Physical Design SDC Synthesis

1. What is Functional Safety?

Functional Safety (FuSa) is the discipline of ensuring that when an electrical/electronic (E/E) system fails, it fails safely — not unpredictably.

In automotive, the governing standard is ISO 26262 (and its semiconductor-specific Part 11). FuSa is not about making a car work perfectly; it is about guaranteeing that a failure — a bit flip, a power glitch, a software hang — cannot cause unreasonable harm.

Key idea: FuSa is a chain of custody. Requirements flow from the safety concept → into UPF → into RTL → into synthesis → into SDC → into physical design → and finally into the safety case that auditors read. Break one link and the whole ASIL claim collapses.

2. ASIL & Decomposition

ASIL (Automotive Safety Integrity Level) ranks risk from A (lowest) to D (highest). It is derived via HARA from three variables:

VariableMeaningExample (Braking)
Severity (S)How bad is the injury?S3 — fatal
Exposure (E)How often is the hazard situation possible?E4 — high probability
Controllability (C)Can the driver avoid harm?C3 — difficult

ASIL Decomposition lets you split a high-ASIL goal into independent lower-ASIL channels — but only if they are truly independent. That independence is a physical property, not a logical one.

  ┌─────────────────────┐
  │   ASIL D GOAL       │
  │   (e.g., Steering)  │
  └──────────┬──────────┘
             │ decompose
      ┌──────┴──────┐
      ▼             ▼
  ┌────────┐    ┌────────┐
  │ASIL B  │    │ASIL B  │   ← two independent channels
  │Channel │    │Channel │
  │   A    │    │   B    │
  └────┬───┘    └───┬────┘
       │            │
       └─────┬──────┘
             ▼
  ┌─────────────────────┐
  │ IF physically       │
  │ independent  →  D   │
  │ credit preserved    │
  │                     │
  │ IF NOT independent  │
  │ → reverts to ASIL D │
  │ for the whole chip  │
  └─────────────────────┘
Diagram 1 — ASIL decomposition collapses if physical independence is not proven.

3. The FuSa Chain of Custody

Every stage must produce evidence that separation and independence are real. This is the spine of the whole article.

  ┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐   ┌──────────┐
  │  SAFETY  │   │   UPF    │   │   RTL    │   │ SYNTHESIS│   │    PD    │
  │ CONCEPT  │──▶│ (intent) │──▶│ (verify) │──▶│ (insert) │──▶│(enforce) │
  └──────────┘   └──────────┘   └──────────┘   └──────────┘   └────┬─────┘
       ▲                                                             │
       │                                                             ▼
  ┌────┴──────────────────────────────────────────────────────┐
  │   DFA AUDIT  —  "Can a fault in A affect B?"              │
  │   Evidence: UPF + netlist + simulation + layout + SDC     │
  └───────────────────────────────────────────────────────────┘
Diagram 2 — FuSa is a chain of custody; every link is audited by the DFA.

4. UPF Section — Power Intent as Safety Evidence UPF

UPF (Unified Power Format, IEEE 1801) declares power domains, isolation, level shifting, retention, and power switches. In a FuSa design, it becomes a traceable safety document.

4.1 What Must Be Explicit (Not Defaulted)

UPF ConstructFuSa RequirementWhy
set_isolation Explicit clamp polarity per signal Wrong clamp on active-low reset can hold a safety block in reset forever — a systematic fault.
set_level_shifter Explicit location & rule; high-to-low shifters preferred Prevents overstress of thin-oxide devices — a latent fault mechanism flagged by DFA.
set_retention Selective element list + documented justification Retain only state needed to reach a safe state.
create_supply_set Separate supply set for safety island No shared always-on rail unless DFA explicitly allows.
create_power_domain One domain per independent channel / lake Physical separation root.

4.2 Example UPF Snippet (Safety Island)

# ---- Safety island: independent supply set ----
create_power_domain PD_SAFETY -elements {u_safety_island}
create_power_domain PD_QM     -elements {u_qm_domain}

create_supply_port VDD_SAFETY
create_supply_port VDD_QM
create_supply_net  VDD_SAFETY
create_supply_net  VDD_QM
connect_supply_net VDD_SAFETY -ports {VDD_SAFETY}
connect_supply_net VDD_QM     -ports {VDD_QM}

# Bind separate supply sets (NO shared always-on)
set_domain_supply_net PD_SAFETY -primary_power_net VDD_SAFETY \
                                 -primary_ground_net VSS
set_domain_supply_net PD_QM     -primary_power_net VDD_QM \
                                 -primary_ground_net VSS

# ---- Isolation on QM -> SAFETY crossings ----
set_isolation ISO_QM2SAFE -domain PD_QM -isolation_power_net VDD_SAFETY \
    -isolation_ground_net VSS -clamp_value 0 \
    -applies_to outputs -isolation_signal iso_en_qm

# ---- Level shifters (explicit location) ----
set_level_shifter LS_QM2SAFE -domain PD_QM -applies_to outputs \
    -location self -rule both

# ---- Retention: only safety-critical state ----
set_retention RET_SAFETY -domain PD_SAFETY \
    -retention_power_net VDD_SAFETY -retention_ground_net VSS \
    -elements {u_safety_island.u_core.safe_state_reg*}

4.3 What the User Must Do (UPF Checklist)

  • ✅ Declare separate supply sets for each independent safety channel.
  • ✅ Specify explicit clamp values on every isolation strategy — never rely on defaults.
  • ✅ Set level-shifter location (-location) and rule for every voltage crossing.
  • ✅ Define retention element lists and document the justification in the safety case.
  • ✅ Run static UPF structural checks before synthesis (missing isolation = DFA fail).
  • ✅ Hand the same golden UPF to simulation, synthesis, and PD — no local edits.
  ┌──────────────────────────────────────────────────────────┐
  │                    SoC  DIE                              │
  │                                                          │
  │   ┌──────────────────┐        ┌──────────────────┐       │
  │   │  PD_SAFETY       │        │  PD_QM           │       │
  │   │  (ASIL channel)  │        │  (non-safety)    │       │
  │   │  VDD_SAFETY      │        │  VDD_QM          │       │
  │   │  clk_root_S      │        │  clk_root_QM     │       │
  │   └────────┬─────────┘        └────────┬─────────┘       │
  │            │  ISO_QM2SAFE              │                 │
  │            │  (clamp = 0)               │                 │
  │            ▼                            ▼                 │
  │      ┌───────────┐              ┌───────────┐            │
  │      │ LEVEL     │              │ LEVEL     │            │
  │      │ SHIFTER   │              │ SHIFTER   │            │
  │      └─────┬─────┘              └─────┬─────┘            │
  │            └──────────┬───────────────┘                  │
  │                       ▼                                  │
  │              ┌─────────────────┐                         │
  │              │  FFI FIREWALL   │                         │
  │              │  (NoC / glue)   │                         │
  │              └─────────────────┘                         │
  └──────────────────────────────────────────────────────────┘
Diagram 3 — UPF-declared domains, isolation and level shifting at every boundary.

5. RTL Section RTL

RTL must be power-aware and UPF-compliant. The bugs that hurt in silicon are the ones that appear during power transitions.

5.1 RTL Rules

  • Do not hand-instantiate isolation cells. Let the tool insert them from UPF. Hand-coded cells can be optimized away or miss the UPF contract.
  • Use retention flops where set_retention demands them; verify save/restore sequencing.
  • No logic that assumes a domain is always ON unless UPF declares it always-on and DFA approves.
  • Reset and clock crossings must be synchronized and physically separated for the safety island.

5.2 Power-Aware Simulation (Mandatory)

Run RTL with the golden UPF and verify:

  • Isolation clamps correctly when source powers down.
  • Retention saves and restores the right state.
  • No X-propagation from OFF domains into ON safety logic.
  • Power transitions during interrupts and resets (the classic corner case).
  Power-aware coverage must cross power states with system events:

       Power State
       ▲
   ON  │  ┌────┐
       │  │████│  ← transition during
   OFF │──┘    └────  an interrupt: BUG ZONE
       └──────────────────▶ time
                ▲
           interrupt arrives here

  Coverage bins:
    cp_system_reset_power_mode      (reset × power state)
    cr_intr_during_power_transition (interrupt × power transition)
    cr_lpi_handshake_power_state    (LPI × power state)
Diagram 4 — The dangerous corner: a power transition during an interrupt or reset.

5.3 What the User Must Do (RTL Checklist)

  • ✅ Run static low-power checks at RTL before synthesis.
  • ✅ Run power-aware simulation with UPF; catch X-propagation.
  • ✅ Add assertions: isolation enabled before power-off, retention save before off / restore after on.
  • ✅ Cover interrupt × power-transition cross coverage.
  • ✅ Verify LPI handshaking completes before domain power-down.

6. Synthesis Section SYNTH

Synthesis is where UPF intent becomes real cells. If it drops an isolation buffer for timing, FuSa separation is broken.

6.1 Inputs to Synthesis

InputPurpose
RTL + golden UPFPower intent
SDC with power-mode awarenessTiming in every valid power state
Liberty with power attributesis_isolation_cell, is_level_shifter, always_on
UPF-aware synthesis toolInserts isolation/shifter/retention

6.2 What Synthesis Must Produce

  • Isolation cells on every OFF→ON crossing.
  • Level shifters on every voltage crossing, placed per UPF.
  • Retention flops in the specified domain.
  • No optimization across domain boundaries that violates FFI.

6.3 Post-Synthesis Checks

  ┌───────────────┐
  │ RTL + UPF +   │
  │ SDC + Liberty │
  └───────┬───────┘
          ▼
  ┌───────────────┐
  │  SYNTHESIS    │  inserts isolation / shifter / retention
  └───────┬───────┘
          ▼
  ┌───────────────┐
  │ NETLIST       │
  └───────┬───────┘
          ▼
  ┌─────────────────────────────────────┐
  │ CHECKS:                              │
  │  • isolation present on all crossings│
  │  • level shifters present            │
  │  • retention flops present           │
  │  • no boundary violations            │
  │  • illegal power-state combos flagged│
  └─────────────────────────────────────┘
Diagram 5 — Synthesis inserts safety-critical cells; post-synth checks verify they survived.

6.4 What the User Must Do (Synthesis Checklist)

  • ✅ Read the golden UPF into synthesis — no edits.
  • ✅ Provide UPF-aware SDC (power modes).
  • ✅ Verify isolation/shifter/retention cells exist in the netlist.
  • ✅ Check no signal crosses a boundary without the mandated cell.
  • ✅ Confirm retention control connections are correct.

7. Timing Constraints (SDC) SDC

For FuSa with power domains, standard SDC is not enough. You need multi-mode timing driven by the Power State Table (PST).

7.1 FuSa-Critical SDC Requirements

RequirementWhy
PST → timing modesEvery valid power-state combination is a mode; each must be timed.
Level-shifter delay in pathIf STA ignores it, the crossing fails in silicon.
Isolation cell delayIsolation adds delay on safety paths — must be timed.
No false paths on safety crossingsIf it's a safety signal, it must be timed in every active mode.
Separate clocks per domainSafety island clock timed independently; root documented for DFA.

7.2 Example SDC Mode Setup

# Clock definitions per domain
create_clock -name clk_safety -period 10 [get_ports clk_safety]
create_clock -name clk_qm     -period 5  [get_ports clk_qm]

# Mode: safety ON, QM OFF
set_case_analysis 0 [get_ports pwr_qm_en]
set_case_analysis 1 [get_ports pwr_safety_en]

# Mode: both ON — all crossings timed
set_case_analysis 1 [get_ports pwr_qm_en]
set_case_analysis 1 [get_ports pwr_safety_en]

# DO NOT false-path safety crossings
# set_false_path -from u_qm/* -to u_safety/*   ← FORBIDDEN
   Power State Table (PST)  →  Timing Modes

   ┌──────────┬──────────┬─────────────────────┐
   │ SAFETY   │  QM      │  Mode               │
   ├──────────┼──────────┼─────────────────────┤
   │   ON     │   ON     │  M0 (full timing)   │
   │   ON     │   OFF    │  M1 (QM isolated)   │
   │   OFF    │   ON     │  M2 (safety off)    │
   │   OFF    │   OFF    │  M3 (shutdown)      │
   └──────────┴──────────┴─────────────────────┘
        Each mode must be STA-clean.
Diagram 6 — The PST drives timing modes; every valid state must pass STA.

7.3 What the User Must Do (SDC Checklist)

  • ✅ Derive timing modes from the PST.
  • ✅ Include level-shifter and isolation delays in paths.
  • ✅ Never false-path a safety-critical domain crossing.
  • ✅ Give each domain its own clock; document clock roots for DFA.
  • ✅ Run STA in all power modes.

8. Physical Design Section PD

Physical Design is the final enforcer. If the layout doesn't prove independence, the ASIL rating collapses.

8.1 The "Lakes" Concept

A Lake is a physical design hierarchy containing specific sub-blocks. The binding rule: Lakes must have separate placement areas, decoupled power, clock, and reset.

  ┌─────────────────────────────────────────────────────────────┐
  │                     SoC DIE (Top View)                      │
  │                                                             │
  │   ┌───────────────────┐        ┌───────────────────┐        │
  │   │   LAKE A (ASIL B) │        │   LAKE B (ASIL B) │        │
  │   │  ┌─────────────┐  │        │  ┌─────────────┐  │        │
  │   │  │  Channel A  │  │        │  │  Channel B  │  │        │
  │   │  │  CPU / Logic│  │        │  │  CPU / Logic│  │        │
  │   │  └─────────────┘  │        │  └─────────────┘  │        │
  │   │   PWR Rail A      │        │   PWR Rail B      │        │
  │   │   Clock Root A    │        │   Clock Root B    │        │
  │   │   Reset Sync A    │        │   Reset Sync B    │        │
  │   └─────────┬─────────┘        └─────────┬─────────┘        │
  │             │                            │                  │
  │      ┌──────┴──────┐              ┌──────┴──────┐           │
  │      │  ISOLATION  │              │  ISOLATION  │           │
  │      │  BUFFER     │              │  BUFFER     │           │
  │      └──────┬──────┘              └──────┬──────┘           │
  │             └──────────┬─────────────────┘                  │
  │                        ▼                                    │
  │              ┌───────────────────┐                          │
  │              │  COMPARATOR /     │                          │
  │              │  VOTER (hardened) │                          │
  │              └───────────────────┘                          │
  │   ◄── Fence ──►  (placement blockage / routing halo)        │
  └─────────────────────────────────────────────────────────────┘
Diagram 7 — Two redundant channels in physically isolated Lakes; signals cross only through buffered isolation.

8.2 Fault Propagation — Why Buffers Are Mandatory

   NO BUFFER (BAD)                    WITH BUFFER (GOOD)

  ┌──────────┐                       ┌──────────┐
  │ Lake A   │                       │ Lake A   │
  │  fault ●─┼──────┐                │  fault ●─┼──►[BUF]──┐
  └──────────┘      │                └──────────┘          │
                    ▼                                       ▼
  ┌──────────┐   ┌─────┐             ┌──────────┐      ┌─────┐
  │ Lake B   │◄──┤short│             │ Lake B   │◄─────┤BUF  │
  │          │   └─────┘             │          │      └─────┘
  └──────────┘                       └──────────┘
  Fault propagates back              Buffer blocks reverse
  → both channels die                propagation → independence
  → CCF, ASIL credit LOST            → ASIL credit OK
Diagram 8 — Unbuffered inter-lake nets let faults back-propagate; buffers preserve independence.

8.3 Power Domain Isolation

  WITHOUT ISOLATION                   WITH ISOLATION

  ┌─────────┐   ┌─────────┐          ┌─────────┐   ┌─────────┐
  │Domain A │   │Domain B │          │Domain A │   │Domain B │
  │ 1.2V ON │   │ 1.2V OFF│          │ 1.2V ON │   │ 1.2V OFF│
  └────┬────┘   └────┬────┘          └────┬────┘   └────┬────┘
       │             │                    │             │
       └──────┬──────┘                    │        ┌────┴────┐
              │                           │        │ISOLATION│
        signal crosses                    │        │ BUFFER  │
              │                     ┌─────┴──┐     │ (I_OFF) │
              ▼                     │  LEVEL │     └────┬────┘
        ╔═══════════╗               │ SHIFTER│          │
        ║ LEAKAGE   ║               └─────┬──┘          │
        ║ PATH      ║                     │             │
        ╚═══════════╝                     └──────┬──────┘
              │                                  │
      Domain A dragged down              Clean crossing,
      by Domain B → CCF                   no leakage path
Diagram 9 — Isolation cells and level shifters break galvanic leakage paths between ON and OFF domains.

9. Physical Bounds & Constraints — What You Actually Give the Tool PD

This is the section you asked for: the exact constraints to hand to the PD tool so the safety separation is physically enforced.

9.1 Floorplan Constraints — The Bounds

ConstraintExample CommandFuSa Purpose
Region / bounds per lake create_region Lake_A -box {0 0 400 400}
create_region Lake_B -box {600 0 1000 400}
Physically constrains each redundant channel; prevents interleaving.
Placement bounds create_bounds -name bnd_safety -coordinate {…} -type hard u_safety/* Keeps safety logic inside its lake.
Placement blockages create_placement_blockage -type hard -bbox {500 0 600 400} Fence between lakes; supports DFA minimum-distance argument.
Routing halos set_route_halo -nets {safety_*} -spacing 2 Prevents unintended coupling across the fence.
Keep-out for QM in safety lake create_bounds -type exclusive u_qm/* -coordinate {…} No QM logic wanders into the safety island.

9.2 Power Grid Constraints

  • Separate power meshes per supply set from UPF. Never merge safety and QM grids unless DFA permits.
  • Isolation cell power must connect to the always-on / destination rail per UPF.
  • Level shifter rails: up-shifters need both rails routed; verify connectivity.
  • No accidental shorts between safety and QM rails — check with LVS.

9.3 Routing Constraints

  • Non-default rules (wider, spacing) for safety-critical nets.
  • No routing through QM regions without buffering.
  • Shielding for high-integrity safety signals where DFA requires.

9.4 Minimum Distance — Defeating Single-Event Upsets

  BAD: Adjacent placement            GOOD: Spaced / interleaved

  ┌───┬───┐                          ┌───┐       ┌───┐
  │ A │ B │  ← one particle          │ A │       │ B │
  └───┴───┘    flips both            └───┘       └───┘
   ▲
   │ particle strike                 ┌───┐       ┌───┐
   ▼                                 │ B │       │ A │
  Both channels corrupted            └───┘       └───┘
  → redundancy defeated
                                     Distance ≥ d_min enforced
                                     → single strike hits one only
Diagram 10 — Minimum-distance / interleaving rules ensure one event corrupts at most one channel.

9.5 What the User Must Do (PD Checklist)

  • ✅ Create one region/bounds per lake; hard bounds for safety logic.
  • ✅ Place a hard placement blockage fence between lakes.
  • ✅ Set routing halos on inter-lake nets.
  • ✅ Keep power meshes separate per UPF supply set.
  • ✅ Enforce minimum-distance / interleaving for redundant flops.
  • ✅ Verify with LVS that no safety/QM rail shorts exist.
  • ✅ Run thermal/EM analysis to ensure no hot spot degrades the safety island.
  • ✅ Confirm no signal crosses a lake boundary without the mandated cell.

10. DFA Audit Checklist

The Dependent Failure Analysis is the auditor. For every shared resource, it asks: "Can a fault in A affect B?" Your evidence must answer it.

  ┌─────────────────────┐
  │  Safety Concept     │
  │  (ASIL D target)    │
  └──────────┬──────────┘
             ▼
  ┌─────────────────────┐
  │ ASIL Decomposition  │
  │  D  →  B(D) + B(D)  │
  └──────────┬──────────┘
             ▼
  ┌─────────────────────┐
  │ Dependent Failure   │◄──────────────┐
  │ Analysis (DFA)      │               │
  │ Shared resources:   │               │
  │  • Power rail?      │               │
  │  • Clock root?      │               │
  │  • Reset?           │               │
  │  • Substrate?       │               │
  │  • Proximity?       │               │
  └──────────┬──────────┘               │
             ▼                          │
  ┌─────────────────────┐               │
  │  PD Constraints     │               │
  │  • Separate Lakes   │               │
  │  • Isolation buffers│               │
  │  • Min spacing rule │               │
  │  • Separate rails   │               │
  └──────────┬──────────┘               │
             ▼                          │
  ┌─────────────────────┐               │
  │  Layout / Signoff   │               │
  │  Evidence           │               │
  └──────────┬──────────┘               │
             ▼                          │
  ┌─────────────────────┐               │
  │  DFA Verification   │───────────────┘
  │  Pass?  ── No ──► iterate
  │    │
  │   Yes
  │    ▼
  ┌─────────────────────┐
  │ Safety Case Closed  │
  └─────────────────────┘
Diagram 11 — The DFA loop forces PD to prove separation; failure to prove collapses the decomposition.

10.1 Evidence Table

Shared ResourceEvidence Required
Power railUPF separate supply sets + PD power-grid separation + LVS
Clock rootSeparate clock definitions in SDC + PD clock-tree separation
ResetSeparate reset synchronizers + verified clamp polarity
SubstrateGuard rings / deep N-well isolation where required
ProximityMinimum-distance rules + interleaving + placement blockages
InterconnectIsolation buffers + routing halos + no unbuffered crossings

11. Summary

Functional Safety separation is a chain of custody:
UPF declares it → RTL verifies it → Synthesis inserts it → SDC times it in every power mode → PD physically enforces it → DFA audits it.

If any link is missing, the ASIL decomposition collapses and the whole chip reverts to the highest ASIL. That is a tape-out killer. The constraints above — UPF strategies, synthesis checks, PST-driven SDC modes, lake regions, placement blockages, routing halos, minimum-distance rules, and power-grid separation — are the concrete inputs that keep the safety case alive.

Remember: Redundancy is meaningless if both channels share a clock, a supply, or a hot spot. Physical Design is where the safety concept becomes physically true — or fails.

Tags: #FunctionalSafety #ISO26262 #UPF #PowerAware #SDC #PhysicalDesign #DFA #FFI #ASIL #Synthesis #AutomotiveSoC

All diagrams are original conceptual illustrations created for this article — free to reuse with attribution.

No comments:

Post a Comment

SiteMap