Etch Machining Damaged Germanium

# Etch Machining-Damaged Germanium: A Depth Bounded on Both Sides

Step twenty-two's margin budget set aside enough distance between each cut face and the nearest junction to contain the saw's damage zone — but setting aside margin and actually removing the damage inside it are two different things, and this step is where the removal finally happens. Electrolytic etching dissolves a controlled depth of germanium from every cut and machined surface, eating into exactly the mechanically disturbed material the saw left behind in steps twenty-two and twenty-three. But etch depth here isn't free to be as generous as possible: because the bar's exposed faces sit close to the base region on both sides, etching too aggressively removes base material along with the damage, narrowing $W_B$ toward the punch-through threshold step eighteen already established as a hard electrical limit.

## 1. Etch Depth Is Bounded Below by Damage and Above by Base-Width Safety

$$d_{\text{saw damage}} < d_{\text{etch}} < \frac{W_B^{\text{(grown)}} - W_B^{\text{(min safe)}}}{2}$$

The lower bound comes directly from step twenty-two: etching has to remove at least as much depth as the saw's own damage zone, or disturbed, dislocation-rich material survives at the surface regardless of how much margin was originally left. The upper bound comes from step eighteen's punch-through condition: because etching removes material from exposed faces on both sides of the base simultaneously, the effective base width shrinks by roughly twice the etch depth, and that shrinkage can't be allowed to push $W_B$ below the minimum the two depletion regions require to stay separated. This is a genuine two-sided optimization window, not a single target value — too little etch leaves damage behind, too much etch threatens the same punch-through failure step eighteen was built around avoiding.

## 2. Real Diagram: The Etch Window Between Two Failure Modes

Etching Removes Damage Without Eroding the Base Past Safety two independent constraints bound the same single etch-depth decision n region base n region damage, removed by etch damage, removed by etch if the etch reaches too far toward the base, W_B itself starts eroding

## 3. The Same Bar Now Carries Two Separate Safety Margins Against Base Width

$$W_B^{\text{(remaining)}} = W_B^{\text{(grown)}} - 2\,d_{\text{etch}}$$

Base width has now been constrained by every step since step sixteen first scheduled its pull-time target: step eighteen's punch-through condition set the electrical floor, step twenty-four's inspection confirmed no mechanical defect had already compromised it, and this step's etch depth is the last process operation with the power to change $W_B$'s actual value before the device is finished. Everything downstream — lead-wire positioning, final parametric test — inherits whatever $W_B^{\text{(remaining)}}$ this etch step actually leaves behind, which is why etch depth is controlled as precisely as any of the earlier timing-based dimensions in this process, even though it's governed by a chemical rate rather than a pull-time interval.

The Permitted Etch-Depth Window d_saw damage < d_etch < (W_B,grown − W_B,min safe) / 2 etch depth, d_etch → too little — damage remains valid window too much — W_B erodes past safety a single etch step, bounded by two unrelated earlier constraints meeting at once

## Etch Machining-Damaged Germanium's Place in the Process Lineage

Etching machining-damaged germanium is step twenty-seven of the 1951 grown-junction transistor's full manufacturing sequence — immediately after the bar's two ends have been attached, and before the bar is rinsed and dried for base contacting. It is the step that finally removes the saw damage step twenty-two's margin only set aside, bounded on its other side by the same punch-through base-width floor step eighteen established, making this the last operation able to change the finished device's base width before probing and bonding begin.

Take etch machining damaged germanium further

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

Ask CFSGPT about this → Request a technical assessment → Open the CFS app