Use these drills after completing all topics in Analog-Digital Boundaries. Answer with boundary, mode, metric, artifact, owner, and regression.
[INT][AMS][ANALOG-DIGITAL-BOUNDARIES]
Q: What is the first sign boundary cells are underspecified?
A:
Mode-specific failures where voltage or state assumptions differ between analog and digital domains.
FOLLOW-UP TRAP: Treating them as random lab noise.[INT][AMS][ANALOG-DIGITAL-BOUNDARIES]
Q: When is an ESD waiver acceptable?
A:
Only with foundry-backed rationale, explicit affected modes, and mitigation/monitoring plan.
FOLLOW-UP TRAP: Using schedule pressure as justification.[INT][AMS][ANALOG-DIGITAL-BOUNDARIES]
Q: How do you prove a handoff contract is complete?
A:
Every clock/reset/power/mode assumption maps to a check, owner, and artifact.
FOLLOW-UP TRAP: Reviewing only functional paths.BOUNDARY -> MECHANISM -> METRIC -> ARTIFACT -> FIX -> REGRESSIONBOUNDARY CONTRACT FLOW
analog intent -> boundary implementation -> digital wrapper -> signed reviewState boundary, mode, and evidence tag with every claim.
Always align analog, digital, and physical owners before signoff decisions.
Fixing averages while tails still fail.
Skipping package/supply evidence in jitter or SerDes issues.
Shipping with waivers that lack owner and expiration criteria.