Work it through
Three vectors, one detecting choice
01 and 10 do not expose this stuck-at-zero fault at y; 11 does, provided the capture path is controlled and observable.
A detecting pattern needs activation, propagation, and observation together.
Your next page is on its way.
Chapter 1 · DFT & memory test
Carry implementation intent through explicit handoffs, then trace controllability, capture, observability, compaction, memory test, and access ownership end to end.

A worked mechanism
Use the illustrative gate y = a AND b, with a stuck-at-zero fault on the a input and a scan-observable capture register at y.
No difference
a=0, b=1 produces y=0 in both the good and faulty circuits.
Both outputs 0
a=1, b=0 activates the fault at a, but b=0 blocks it at y.
Observable difference
a=1, b=1 produces good y=1 and faulty y=0.
Detect only if observed
The test clock samples y and the defined scan path carries the response to comparison.
Work it through
01 and 10 do not expose this stuck-at-zero fault at y; 11 does, provided the capture path is controlled and observable.
A detecting pattern needs activation, propagation, and observation together.
A scan path can be present yet the captured effect can be masked or contaminated by an X source.
Use gate-level fault simulation and the actual scan/capture/compaction protocol; this two-input example does not claim full chip fault coverage.
Choose a question to apply the mechanisms in this chapter.
16 of 16 practice questions shown.
Treat RTL-to-GDS as a chain of explicit contracts. Each stage consumes design intent, changes the implementation, and produces evidence for the next owner.
Synthesis, test insertion, floorplanning, placement and clocking, routing, extraction, and signoff refine the same design. A handoff is complete only when the data and its assumptions travel together.
A complete handoff includes the design database, the constraints and intent used to interpret it, and evidence that the producing stage met an agreed acceptance contract.
DFT architecture starts before synthesis, scan insertion usually operates on a synthesized test-ready netlist, and its added clocks, modes, chains, and timing paths remain part of physical implementation and signoff.
Routing creates geometry, but tapeout requires extracted electrical analysis, manufacturing-rule checks, connectivity agreement, reliability checks, and proof that late implementation changes preserved logic.
Scan converts difficult sequential state into controllable and observable test state. ATPG still needs a sensitized path and a capture event that preserves the fault effect.
scan_en=1Load statescan_en=1Load statescan_en=0Launch transitionscan_en=0Sample responsescan_en=1Observe statescan_en=1Observe stateIllustrative launch-on-capture sequence; launch-on-shift changes the launch edge, not the activation–propagation–observation obligation.
Shift cycles load and unload scan state with scan enable asserted. One or more functional-speed capture edges launch and sample the response before the chain returns to shift mode.
Shift mode connects scan flops as serial chains to load and unload state. Capture mode restores the functional data paths so one or more controlled clock edges record the circuit response.
ATPG drives the fault site to the opposite of the faulty value, chooses side inputs that sensitize a path, and propagates the resulting difference to a scan cell or observable output.
A transition test launches a value change and captures its arrival using the functional-speed edge spacing, so excessive path delay can be observed as an incorrect sampled value.
Memory BIST, scan compression, and JTAG solve different access problems. Their controllers, clocks, resets, and result paths must compose without contention.
w0r0 · w1r1 · w0r0 · w1r1 · w0r0A TAP or chip test controller selects an instrument. Scan logic tests random logic, MBIST applies memory-specific operations, and status returns through an owned, deterministic path.
An unknown entering a linear compactor can contaminate many signature bits and hide otherwise deterministic fault effects, so known X sources need masking, blocking, control, or bypass before compaction.
A March test applies ordered read and write operations while traversing addresses in specified directions, creating the background and neighbor activity needed to expose cell, transition, address, and coupling faults.
Scan and ATPG target random logic, MBIST applies memory-specific algorithms, and JTAG or an embedded-instrument network provides external access and selection. A chip test controller coordinates shared clocks, resets, modes, and status.