Etch Plasma Ignition Budget

# Etch Plasma Ignition Budget

An etch plasma ignition budget defines the allowed startup behavior, the evidence that confirms ignition and the disposition of wafers exposed to incomplete or repeated startup attempts. Its purpose is to make the beginning of plasma operation observable and reviewable.

Ignition confirmation is a defined equipment or process event. It is not proof that the complete etch step has achieved its required removal, profile or material integrity.

## Distinguish three events

A request for RF power, confirmation of ignition and acceptance of sustained operation answer different questions. Preserve their timestamps and definitions instead of treating them as a single start time.

Comet describes RF generators and matching networks as components used to ignite plasma. Its matching-network documentation also describes tuning behavior that depends on preset points. Those product descriptions do not provide a universal ignition time or a wafer acceptance criterion.

An etcher can have more than one RF source or power path. Identify the source, operating mode and diagnostic being evaluated. Oxford Instruments describes ICP systems with separate source and substrate bias controls; a status from one path does not establish every condition in the other.

## Define what confirms ignition

Use the equipment's qualified diagnostic and specify its threshold, evaluation interval, validity conditions and any required persistence. Depending on the system, available evidence can include RF diagnostics, optical signals or an equipment status derived from defined measurements.

Do not invent a common reflected-power threshold for all etchers. A reading has meaning within its measurement location, calibration, timing and control scheme. A low reflected-power reading alone does not establish all plasma properties or the resulting wafer condition.

The cited MKS foreline-cleaning manual provides a specific example of ignition and extinguish states evaluated using reflected power. It concerns a foreline cleaning system, not a wafer etch recipe. Its numerical limits must not be transferred to an etcher.

## Measure latency consistently

Define the start marker and the confirmation marker before calculating ignition latency. Record the timestamp source, synchronization, sampling and filtering limitations.

If a diagnostic is sampled periodically, the recorded confirmation time may only bound the physical event within the measurement resolution. Preserve that uncertainty rather than reporting unsupported precision.

Keep command-to-confirmation latency separate from later tuning or stabilization intervals when the procedure distinguishes them. An ignition budget complements the recipe transition budget; it does not replace evaluation of subsequent process behavior.

## Retain failed attempts and retries

For each attempt, retain the commanded sequence, elapsed interval, diagnostic evidence and equipment fault state. A failed confirmation does not necessarily mean that the wafer experienced no partial plasma or other exposure.

A later successful attempt does not erase earlier history. Evaluate the complete sequence when deciding wafer disposition, including time under gas, any applied RF and the relevant thermal or surface history.

Retry only according to the qualified equipment procedure. This budget does not authorize bypassing an interlock, changing ignition settings or repeatedly restarting a wafer until it passes.

## Separate ignition from extinction

A plasma that fails to meet its startup criterion and one that meets it and later extinguishes are different event histories. Preserve the ordering and relevant diagnostic interval.

Define how an interruption affects the remainder of the segment and wafer disposition. Avoid combining interrupted segments into a nominal duration unless that interpretation is qualified for the process.

For deliberately pulsed operation, use the intended pulse and restart definitions. A diagnostic developed for continuous operation cannot automatically classify every intended off interval as a fault.

## Connect the record to wafer acceptance

Qualify the sequence using the required material and feature results. Stable equipment status alone does not demonstrate critical dimension, selectivity, surface condition or electrical integrity.

Record recipe revision, relevant hardware configuration and chamber state when evaluating startup repeatability. Changes to the configuration or diagnostic can require requalification of the acceptance rule.

A useful review separates event classification, likely cause and wafer disposition. The same symptom can require additional evidence before assigning a root cause; an equipment alarm is not a complete causal explanation.

Close the budget with the full startup record and the applicable wafer evidence. The result should show what was requested, what was confirmed, what persisted and why the final disposition meets the defined requirements.

## Sources and scope

• [Comet — Synertia RF platform introduction](https://comet.tech/pct/news/23-05-synertia): RF delivery components and plasma ignition.
• [Comet — Synertia RF matching network](https://pct.comet.tech/en/products/synertia_rf_power_delivery_platform/synertia_rf_matching_network): product-specific tuning and diagnostic capabilities.
• [Oxford Instruments — ICP RIE](https://plasma.oxinst.com/technologies/icp-rie): separate source and substrate bias controls.
• [MKS — Cleanline Foreline Plasma Clean System Manual](https://api.p1.mks.com/medias/sys_master/mksresources/hd0/h06/9954695938078/Cleanline-20032965-MAN/Cleanline-20032965-MAN.pdf): equipment-specific ignition and extinguish classifications, provided only as a diagnostic example.

Original diagrams and explanatory synthesis. No universal ignition threshold, retry policy or qualified etch recipe is implied.