Why Design for Test Exists
Catching manufacturing defects in real silicon
every chip that comes off a wafer has to be tested before it is shipped, and some will have manufacturing defects. Design for Test is the set of extra logic and techniques we add so that testing is even possible. DFT is a steady, in-demand specialty and a common interview area, yet it is poorly covered by free material.
Verification versus test - not the same thing
These two words are often confused. Verification asks: is the design correct? It is done before manufacturing, in simulation. Test asks: was this particular physical chip manufactured correctly? It is done after manufacturing, on a tester, on every single die. DFT is about the second one.
| Verification | Manufacturing test | |
|---|---|---|
| Question | Is the design right? | Was this chip built right? |
| When | Before tape-out | After fabrication, per die |
| Finds | Design bugs | Physical defects |
| Where | Simulation / formal | On a hardware tester |
What a manufacturing defect looks like
Tiny imperfections in fabrication can leave a wire permanently shorted to power or ground, an open connection, or a bridge between two nets. The logic was designed correctly, but this particular chip has a physical flaw that makes a gate output stuck or a path broken. Test exists to find those chips and throw them out.
Why you cannot just run the functional tests
Running the real application to catch every possible internal defect would take far too long and could never reach every internal node. DFT replaces that with structured, efficient tests that can reach deep inside the chip and get very high defect coverage in a short time on the tester, which keeps test cost down.
test cost is real money. Every extra second a chip spends on an expensive tester adds to its price. A big part of DFT is getting high defect coverage in as little test time and test data as possible.