Detecting Redundant or Missing Isolation: Theory Deep Dive

Foundational theory

Detecting Redundant or Missing Isolation is core to Isolation & Level Shifting. Treat each power behavior change as a correctness and signoff risk decision.

Core concepts explained

• Missing isolation is dangerous because it permits unknowns or unsafe logic levels to leak into live domains, but redundant isolation is also costly: extra cells increase area, delay, dynamic power, and debug complexity. Effective analysis classifies every crossing by sink sensitivity, power-state overlap, and existing protection path so true missing cases are separated from safe-by-architecture paths such as retained always-on sources or protocol-gated receivers. Redundancy checks should identify stacked isolation on the same functional path, overlapping tool insertions from hierarchical UPF, and dead isolation enables that never toggle in legal modes. Teams should run iterative static analysis plus scenario-driven simulation to verify that waivers are evidence-based, ensuring no crossing is over-protected by default or left exposed by assumption.

• Primary metric: Missing-isolation high-severity findings and redundant-cell area/timing overhead eliminated before low-power signoff freeze.

• Primary artifact: Risk-ranked crossing ledger showing missing, justified-exempt, and redundant isolation candidates with closure action and waiver evidence.

• Owners: power intent signoff lead, RTL integration owner, verification triage owner, timing and power optimization owner, program quality manager

• Power intent and RTL behavior must stay aligned through transitions

• Proof quality beats broad waive strategies in low-power closure

Why this matters in low-power signoff

Isolation and level-shifting quality is measured at crossing correctness, clamp safety, and timing of control intent. Teams that enforce this reduce false alarms and real escapes.

Mental model

ISOLATION + LEVEL SHIFTER VIEW

       Domain A (0.75V)                       Domain B (0.95V)
   +----------------------+               +----------------------+
   |  producer flops      |--data_low--->| [LS_UP] -> consumer  |
   |  valid_low           |--valid_low-->| [ISO]   -> sink       |
   +----------------------+               +----------------------+
               ^                                     |
               |---------- iso_en / clamp -----------|

Rules to verify:
- LS direction matches voltage relationship
- ISO active before source domain turns OFF
- clamp value is protocol-safe during OFF windows

Worked intuition

1. Classify symptom first: illegal transition, corruption, isolation break, retention drift, or X-prop ambiguity.

2. Pinpoint first phase boundary where expected low-power behavior diverges.

3. Quantify movement in Missing-isolation high-severity findings and redundant-cell area/timing overhead eliminated before low-power signoff freeze. before broad refactors.

4. Collect Risk-ranked crossing ledger showing missing, justified-exempt, and redundant isolation candidates with closure action and waiver evidence. with fixed run metadata and mode sequencing.

5. Apply one bounded fix and replay both targeted and broader scenarios.

6. Publish owner-signed closure note with rollback trigger.

Common misconceptions

• Passing nominal ON/OFF smoke proves transition correctness.

• UPF compile clean means all intent semantics are correct.

• All X-prop failures indicate real product escapes.

• Retention behavior can be trusted without multi-cycle restore stress.

Low-power verification deep dive

Boundary correctness depends on timing: isolate and shift at the right crossings and right phases.

Concept diagram

BOUNDARY SAFETY VIEW

domain crossing -> level-shift requirement -> isolation control -> OFF/ON transition behavior

Metric graph

BOUNDARY BUG CLASSES

missing isolation      █████
late isolation         ████
LS misdirection        ███

Metrics and artifacts to collect

• cross-domain boundary inventory

• clamp-value correctness report

• LS direction and threshold checks

• missing or redundant boundary action list

Mini case study

A boundary bug escaped unit tests until domain-off traffic stress revealed late isolation enable timing.

Debug branches

• Map each crossing to expected LS and isolation behavior.

• Verify enable timing against collapse and restore edges.

• Check clamp safety for protocol-facing signals.

Senior review question

Ask: what exact low-power transition boundary failed first, and which artifact proves the closure claim reproducibly?

Key takeaways

• Tie each LPV claim to a concrete transition boundary and one proving artifact.

• Prefer minimal reversible fixes with explicit owner and rollback criteria.

Common pitfalls

• Treating power-aware failures as random before boundary classification.

• Waiving X-prop failures before proving impact and root cause.

• Declaring closure without deterministic replay across key modes.

Theory reinforcement

Theory matters when it predicts concrete failure signatures and closure boundaries.

Translate LPV semantics into reproducible verification outcomes.