12.12.2012 Views

characterization, modeling, and design of esd protection circuits

characterization, modeling, and design of esd protection circuits

characterization, modeling, and design of esd protection circuits

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

158 Chapter 5. Design <strong>and</strong> Optimization <strong>of</strong> ESD Protection Transistor Layout<br />

from Fig. 5.60, the condition for which the model predicts ITLP,ws < 0 for large DGS is<br />

< 0.013µm-1 1 ⁄<br />

W<br />

(W > 76µm). This nonphysical aspect <strong>of</strong> the model is a result <strong>of</strong><br />

having to extrapolate beyond the <strong>design</strong> space, which does not cover the large DGS-large<br />

W corner, <strong>and</strong> could be corrected by exp<strong>and</strong>ing the <strong>design</strong> space to this corner.<br />

Fortunately, the largest DGS <strong>of</strong> any <strong>of</strong> the SRAM <strong>protection</strong> <strong>circuits</strong> is 4.2µm, so the<br />

model predictions for the <strong>circuits</strong> <strong>of</strong> interest are accurate.<br />

5.3.2 SRAM Model Prediction<br />

As mentioned previously, HBM withst<strong>and</strong> levels <strong>of</strong> an IC cannot be predicted unless the<br />

stress current paths are known. The SRAM test circuit used for this study has only one<br />

VCC <strong>and</strong> one VSS supply, which simplifies the ESD analysis. For reasons discussed in<br />

Section 5.1.4, I/O vs. VSS failures are expected to occur in the NMOS pull-down circuit,<br />

while I/O vs. VCC <strong>and</strong> VCC vs. VSS failures are expected to occur in the VCC-VSS supplyclamp<br />

circuit (refer to Fig. 5.59). The observed failure mode for I/O vs. VSS SRAM<br />

testing is pin leakage to VSS , while the failure mode for I/O vs. VCC <strong>and</strong> VCC vs. VSS is<br />

increased st<strong>and</strong>-by current. These failures indicate damage to pull-down <strong>and</strong> supply-clamp<br />

<strong>circuits</strong>, respectively, confirming the expected failure mechanisms. Emission microscopy<br />

was also attempted for failure analysis but no emission sites were seen due to the metal<br />

busing over the pull-down <strong>and</strong> clamp <strong>circuits</strong>.<br />

Although the pull-down <strong>protection</strong> <strong>circuits</strong> <strong>of</strong> bi-directional (“Full I/O” in Table 5.2) <strong>and</strong><br />

input-only (“Input”) I/O pins have the same layout parameters, separate HBM stressing <strong>of</strong><br />

each type <strong>of</strong> I/O results in higher withst<strong>and</strong> voltages for the input-only pins. For the inputonly<br />

pull-down <strong>circuits</strong>, all 10 gate fingers are tied to a dummy inverter which provides<br />

the needed gate bounce to reduce the trigger voltage. For the bi-directional I/Os, however,<br />

half <strong>of</strong> the gate fingers are tied to a dummy pre-driver while the other half are driven by<br />

internal circuitry, i.e., they drive the output. Since the two pre-drivers are <strong>of</strong> different size<br />

<strong>and</strong> thus <strong>of</strong>fer different degrees <strong>of</strong> gate bounce, we hypothesize that only half <strong>of</strong> the<br />

fingers are turning on due to different trigger voltages, which would explain why the bidirectional<br />

I/Os are less robust than the input-only I/Os. For <strong>modeling</strong> purposes, then, an n<br />

value <strong>of</strong> 10 is used for the input-only stress while a value <strong>of</strong> 5 is used for the bi-directional<br />

I/Os. (Actually, an n value <strong>of</strong> 1 is used in determining the normalized VHBM,ws because in<br />

the layout every other finger is tied to the same pre-driver <strong>and</strong> thus the five fingers are

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!