Production test is necessarily built around decisions. PASS. FAIL. Bin 1. Bin 2. Ship. Do not ship. Characterization has a different objective. It asks not only whether the device meets specification, but how far it is from the boundary.
That distinction becomes increasingly important as processors integrate compute, memory, high speed interfaces, multiple power domains and advanced packaging into increasingly complex systems.
Suppose five devices all pass the product specification, but under the same controlled workload their minimum stable operating voltages are:
0.70 V | 0.71 V | 0.73 V | 0.76 V | 0.79 V
Production test sees five passing devices. Characterization sees five different levels of margin. That changes the engineering question from “Why did this device fail?” to something potentially much more useful:
PVTW (process, voltage, temperature, workload) gives us a framework for exploring that question.
Take the same device and establish its voltage and frequency boundary using conventional ATE content. Then establish another boundary while running a deterministic compute workload. Repeat with SRAM, memory, PCIe and combined workloads. We may discover that the boundaries are different.
That difference can tell us which workload is exposing the limiting condition and where deeper characterization should begin.
Rather than testing at one nominal operating point, deliberately approach the boundary. Sweep voltage at fixed frequency, temperature and workload. Sweep frequency while the other conditions remain fixed. Repeat across temperature. Then manipulate individual power domains.
A compute workload may be characterized while the core rail is swept and memory and I/O rails remain fixed.
Source link







