Micrologic 1960 Verify Circuit Function Wafer Truth Table

# Verify Circuit Function on the Wafer, Not Just One Transistor's Parameters: Testing a Truth Table, Not a Number

## 1. Why Passing Every Parameter Test Still Does Not Mean the Gate Works

This step probes each finished circuit while it is still on the wafer, exactly as the 1957 series documented at its own Step 16, except that the probe now exercises every combination of logic inputs this gate can receive and checks the output against the truth table the circuit was designed to implement, rather than measuring any single transistor's electrical parameters. A transistor measured individually can meet every specification — correct current gain, correct breakdown voltage, correct leakage — while the circuit built from several such transistors still fails to perform its logic function, because a wiring error, a resistor shifted by the contact effects Step 4 characterized, or an isolation island merged by the depletion-region overlap Step 3 warned against, would never show up in a single-transistor measurement at all. For a gate with $n$ logic inputs, this test can, in principle, be made exhaustive:

$$N_{\text{vectors}} = 2^n, \qquad C = \frac{\text{faults detected}}{\text{total possible stuck-at faults}}$$

where $N_{\text{vectors}}$ is the number of distinct input combinations a complete test applies, and $C$ the fraction of possible single-node stuck-at-high or stuck-at-low faults this test set actually catches. For the small gates this series produces — two or three inputs — $N_{\text{vectors}}$ is small enough that exhaustive testing is entirely practical, and $C$ can approach completeness in a way this project's later, more complex circuits will not be able to afford.

Every Input Combination, Checked Against the Truth Table a small gate's exhaustive test set, applied and compared TRUTH TABLE VERIFICATION, THREE-INPUT GATE ABCexpectedmeasuredresult 00011pass 00111pass 01010FAIL 01100pass 10011pass one wrong row fails the chip, even though every transistor measured fine alone Nvectors = 2n — for a small gate, exhaustive coverage is affordable, and C can approach one this is the first test in the project that checks a function, not a parameter

## 2. Real Diagram: A Probe Card Applying Logic, Not Reading a Number

Where the 1957 series' wafer probe read a single electrical parameter from each die, this probe applies a sequence of input voltage patterns to the gate's input pads and compares the measured output pattern against the truth table — a fundamentally different kind of measurement, exercising the circuit's behavior rather than reading a static value.

Applying Patterns, Not Reading a Static Value the probe exercises the gate through its full input sequence gate under test A: 0,0,0,0,1... B: 0,0,1,1,0... output, compared to expected the circuit either behaves correctly across the whole sequence, or it does not

## 3. Why Every Earlier Wafer Probe in This Project Checked a Number, and This One Checks a Behavior

The 1957 series' own wafer probe at Step 16 read a parameter — cutoff frequency, current gain, leakage — and compared it against a single acceptance band, exactly the kind of static measurement every transistor-level test this project has performed since 1954. This step cannot be satisfied with a static reading, because the thing it is testing is not a number a transistor produces but a *behavior* a circuit exhibits across a sequence of different conditions. That distinction — testing a function rather than a parameter — is the direct and necessary consequence of this series' first four steps building something with more than one component whose correctness depends on how those components cooperate, not merely on how any one of them measures in isolation.

Step 6 does not measure the chip; it interrogates it, across every input condition this test set can afford, to confirm that what several components built together is actually doing the one thing the circuit was designed to do.

Take micrologic 1960 verify circuit function wafer truth table further

Ask the copilot about this term, or have our engineers assess it against your process.