Semi E122.1

SEMI E122.1 defines the exact SECS-II message set for TSEM — the specific status-variable IDs (SVIDs), report IDs (RPTIDs), and collection-event IDs (CEIDs) a tester uses to report test-program identity, bin/sort results, and site status over the wire — rather than the general tester-vocabulary concept E122 establishes. E122 says a TSEM-compliant tester has to expose test-program, bin, and site-state information through a defined vendor-neutral vocabulary; E122.1 is the protocol-binding companion that fixes precisely which SECS-II messages and variable numbers carry that vocabulary, the same relationship E99.1 has to E99 and E116.1 has to E116, now applied to the test floor.

SEMI E122 says: expose test program, bin, and site status
Defined vocabulary, but no fixed wire-level message set
SEMI E122.1 — SECS-II protocol binding for TSEMFixes the actual SVID/RPTID/CEID numbers
Defined SVIDs for test-program ID, bin result, site state
Same variable numbers across every compliant tester
Defined CEIDs for test-run start/stop and result events
No vendor-specific interpretation of the report structure
Host's GEM driver parses any tester's TSEM report identically
No per-vendor translation layer for bin/site reporting

The reason E122 needed its own protocol-binding companion is the same gap every other CEM specialization closes the same way: a defined vocabulary in prose still leaves the SVID, RPTID, and CEID numbers open to each tester vendor's own implementation, so two E122-compliant testers can report the same bin result using different variable IDs the host has to reconcile by hand. E122.1 removes that gap by fixing the SECS-II message set itself, so a fab's test-floor host software can write one GEM driver against E122.1's defined numbering scheme and have it work against any tester implementing TSEM, rather than maintaining a per-vendor mapping table for test-program, bin, and site data.

SEMI E122.1 — Fixing TSEM's Wire-Level Numbers a shared vocabulary still needs shared variable numbering SEMI E122 (TSEM) "Expose test program, bin, and site state" Vocabulary, numbering left open SEMI E122.1 Fixed SVID/RPTID/CEID numbers for every field Wire-level protocol binding Two E122-compliant testers can still number their bin SVIDs differently E122.1 is what makes their reports byte-for-byte interchangeable

E122.1 completes TSEM the same way every ".1" protocol binding completes its base standard: E122 defines what a tester has to communicate, and E122.1 is the fixed SECS-II numbering scheme that makes that communication identical across vendors, so a fab's test-floor host software never has to special-case a tester by brand to get usable bin and site data out of it.

Take SEMI E122.1 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