Factories cannot open every chip and probe millions of nodes. Design-for-Test (DFT) adds structures so manufacturing can detect defects. RTL designers must not accidentally destroy those hooks.
Manufacturing defects happen (shorts, opens, stuck transistors). DFT answers: “Can we tell good die from bad die cheaply?”
You cannot dismantle every suitcase. You design bags and scanners so problems are detectable quickly. DFT is the scanner-friendly suitcase design.
Why it matters: A chip with 40% scan coverage may ship — but factory scrap rate and debug cost explode.
Scan stitches flops into a shift register during manufacturing test.
You may not write scan RTL by hand early on — but your coding style (async resets, clock enables, latches) affects how easily scan can be inserted.
| Mode | What it tests | Who runs it |
|---|---|---|
| Functional (mission mode) | Real use cases, software paths | Board test, system DV |
| Scan (structural) | Stuck-at faults on internal nodes | ATE + ATPG patterns at factory |
| Memory BIST | SRAM bit cells, address decode | On-chip engine + minimal pins |
| Term | Plain English |
|---|---|
| Stuck-at-0 / stuck-at-1 | A node frozen — classic manufacturing defect model |
| Pattern | Bit sequence shifted into scan chains |
| Fault coverage % | Fraction of modeled faults detected |
| Scan enable (SE) | Flips flops into shift mode |
| Capture cycle | One functional clock edge while in test mode |
You rarely hand-code full scan, but you do respect a test-mode mux idea like this:
// Conceptual — DFT tools usually insert this automatically module scan_mux_idea ( input wire func_d, // normal functional data input wire scan_si, // scan chain input input wire scan_en, // 1 = test/shift mode output wire d_to_flop ); assign d_to_flop = scan_en ? scan_si : func_d; endmodule // RTL habit that helps DFT: // - Prefer sync resets / clear clock enables // - Avoid unintentional latches and combo loops // - Document every clock and async set/reset
// BAD: incomplete case → latch inferred → scan insertion pain always @(*) begin if (sel) out = a; // missing else — latch holds previous value end
// GOOD: full assignment every time — maps to mux, scan-friendly always @(*) begin if (sel) out = a; else out = b; end
Gating clocks with random combo logic “to save power” without DFT review — scan chains break and ATPG coverage tanks.
Some blocks (memories especially) include on-chip pattern generators/checkers so external testers do less work.
Awareness level: if architecture says “memory BIST,” leave the interfaces and don’t “optimize away” test ports casually.
Memory BIST typically adds: BIST clock, start/done handshake, repair fuse hooks for redundant rows. RTL designer keeps the wrapper ports visible — DFT fills the engine.
“How does scan help manufacturing?” — Shifts test patterns through flops to detect stuck faults that functional boot tests would miss.
You are not becoming a DFT engineer today. You are learning why “just combo hacks” create expensive DFT pain later.
| Acronym | Meaning |
|---|---|
| DFT | Design for test |
| ATPG | Automatic test pattern generation |
| ATE | Automated test equipment (factory tester) |
| MBIST | Memory built-in self-test |
| SI / SO | Scan in / scan out chain pins |