Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • How to Use This Course
  • AMS Metrics Reference
  • AMS Interface Glossary
  • Reading Path
  • Analog-Digital Boundaries61
    • Boundary Cell Design
    • ESD & Isolation
      • ESD & Isolation: Mechanism
      • ESD & Isolation: Inputs & Outputs
      • ESD & Isolation: Reports & Metrics
      • ESD & Isolation: Debug Playbook
      • ESD & Isolation: Worked Example
      • ESD & Isolation: Pitfalls & Red Flags
      • ESD & Isolation: Interview Drills
      • ESD & Isolation: Review Checklist
      • ESD & Isolation: Theory Deep Dive
      • ESD & Isolation: Design Space
      • ESD & Isolation: Expanded Case Study
      • ESD & Isolation: Step-by-Step Walkthrough
      • ESD & Isolation: Comparison Matrix
      • ESD & Isolation: Software / Programmer View
      • ESD & Isolation: Silicon PPA Impact
    • Noise Coupling Basics
    • AMS Handoff Contract
    • Analog-Digital Boundaries: Tricky Q&A
  • PLL & DLL Clocking61
  • SerDes & High-Speed I/O61
  • ADC / DAC Interfaces61
  • Mixed-Signal Integration61
  • Noise & IR at the Boundary61
  • AMS Interface Interview Prep61
  • AMS Interface Cheatsheet
Loading lesson

‹ESD & Isolation
  1. Topics
  2. Analog & Mixed-Signal
  3. Analog-Digital Boundaries
  4. ESD & Isolation
  5. ESD & Isolation: Review Checklist

AMS Interface · All levels

ESD & Isolation: Review Checklist

Review Checklist for ESD & Isolation.

On this page

    Review checklist

    Review Checklist for ESD & Isolation focuses on ESD path completeness, latch-up risk flags, isolation waiver backlog. The goal is to connect observed symptom to boundary mechanism, ownership, and signoff risk.

    • Boundary assumptions are versioned and signed.

    • Mode matrix (power/clock/reset/stress) is explicit.

    • Physical context (floorplan/package/power) is included where relevant.

    • Metric and artifact references are reproducible.

    • Waivers have owner, expiry, and mitigation.

    • Owners signed: ESD owner, AMS top owner, physical verification owner.

    Sign-off ownership

    Diagram
    OWNERSHIP MAP — ESD & Isolation
    
    artifact                  owner
    ----------------------    -----------------------------
    integration artifact    ESD owner
    implementation artifact AMS top owner
    signoff artifact        physical verification owner
    
    Every boundary issue needs a named owner before fixes start.

    AMS deep dive

    Boundary assumptions must be explicit, versioned, and testable.

    Concept diagram

    Diagram
    BOUNDARY CONTRACT FLOW
    
    analog intent -> boundary implementation -> digital wrapper -> signed review

    Metric graph

    Diagram
    BOUNDARY RISK MIX
    
    missing boundary cells    ███████
    stale handoff assumptions ██████
    silent mode changes       ████

    Reports and artifacts

    • boundary-cell coverage

    • isolation/ESD review

    • handoff contract checklist

    • integration waiver log

    Mini case study

    Noise bursts traced to missing isolation clamp on one low-power transition mode.

    Debug branches

    • Validate boundary-cell insertion

    • Diff handoff assumptions

    • Reproduce with tagged mode sequence

    Senior review question

    Ask: what boundary condition proves this topic is actually closed?

    Key takeaways

    • State boundary, mode, and evidence tag with every claim.

    • Always align analog, digital, and physical owners before signoff decisions.

    Common pitfalls

    • Fixing averages while tails still fail.

    • Skipping package/supply evidence in jitter or SerDes issues.

    • Shipping with waivers that lack owner and expiration criteria.

    Principal AMS review addendum

    ESD and isolation structures create safe discharge and domain separation paths so transients do not propagate into sensitive digital flops or analog macros.

    Metric: ESD path completeness, latch-up risk flags, isolation waiver backlog

    This content block can't be displayed here.

    Block type: unknown

    This content block can't be displayed here.

    Block type: unknown

    This content block can't be displayed here.

    Block type: unknown

    Previous

    27 / 432

    Next: ESD & Isolation: Theory Deep Dive

    Up next

    Up nextESD & Isolation: Theory Deep Dive

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • ESD & Isolation: Mechanism
    • ESD & Isolation: Inputs & Outputs
    • ESD & Isolation: Reports & Metrics