Esp32 Verification Flow
Verification and sign-off is the stage where a finished floorplan has to prove, check by check, that it actually works before anyone is allowed to send it to a foundry — and for a radio-integrated chip like an ESP32-class SoC, that list of checks is longer than a pure-digital design ever has to run. A digital-only chip closes timing, checks power, and runs DRC/LVS; this design adds a fourth category on top of those three — RF isolation and mixed-signal verification — because a clean digital sign-off says nothing about whether the radio actually meets its noise-figure and spectral-mask specs once it's sitting next to a switching CPU.
Static timing analysis has to run across process-voltage-temperature corners, not just one nominal condition, because the chip will actually be manufactured across a real distribution of silicon, not one ideal sample. A path that closes comfortably at typical process, nominal voltage, and room temperature can fail at slow process, low voltage, and high temperature — the corner that represents a worst-case real unit — so sign-off STA has to verify every timing path holds across the full matrix of corners the foundry's process allows, and a single corner failure anywhere on the chip is enough to block tape-out until it's fixed.
Substrate noise coupling is the check that doesn't exist at all on a non-radio chip, and it's checked with its own dedicated simulation, not inferred from the digital and RF checks passing separately. The digital core's switching current injects noise into the shared silicon substrate, and that noise can couple directly into the RF front end's sensitive low-noise stages even when every digital timing path and every standalone RF parameter looks fine in isolation — which is why sign-off for this class of chip runs a specific substrate-coupling simulation that models the physical distance, guard rings, and separate ground domains between the digital core and the RF block, rather than trusting that passing digital sign-off and passing RF sign-off separately is the same thing as passing them together.
ESD and latch-up checks matter disproportionately at every domain boundary, because that's exactly where a stray current path between two independently-powered regions can do real damage. A chip with several independent power domains — digital, RF, I/O, RTC — has more domain-crossing boundaries than a single-rail design, and each one needs its own ESD clamp and latch-up guard-ring verification at every signal that crosses between domains, since an ESD event or a latch-up condition at one of those boundaries can propagate current between domains in a way a single-domain chip's checks were never built to catch.
Verification and sign-off is the stage that turns a design the team believes works into a design the foundry is willing to manufacture — and for an ESP32-class chip, that belief has to survive not just standard digital timing, power, and DRC/LVS checks, but a parallel set of RF and mixed-signal checks confirming that putting a radio and a CPU on the same die didn't quietly break either one.