SC GROUP PRODUCTION TEST STANDARDSMINIMUM STANDARDS FOR TEST PROGRAM NAMING

TEXAS INSTRUMENTS PROPRIETARY INFORMATIONPROPERTY OF TEXAS INSTRUMENTS ONLY

Revision Date Description1.0 11/04/02 Original 1.1 11/21/02 Added clarification regarding use of extensions in test program file names.1.2 11/22/02 Clarification of scope. Addition of upper case requirement.1.3 04/03/03 Add extension definition for Integra Flex1.4 05/08/03 Add requirement for program directory name

1.5 06/27/06 Add “.load” as std extension for Teradyne Image tester programs (A5xx / Catalyst)

1.6 06/11/09 Added Eagle tester to the list of supported tester platforms.1.7 03/08/10 Added standard test program name extension for Verigy.1.8 11/30/11 Add Assembly Check test program name example.1.9 01/16/12 Removed reference to HP94000 tester.2.0 07/20/12 Clarified test program directory structure. Removed dataPOWER specific note.

Scope

Iso All new or revised test programs after November 4, 2002

o VLCT+Assembly Check, Vseries, Polaris, Fusion, Eagle, IntegraFlex, V93000, Teradyne Catalyst and A5xx test platforms

o All Fab and A/T (TI and foundry) sites. 

o Multiprobe and final test programs

o Site requirements may meet or exceed these minimum standards.

o Definition of each component of the test program name, and the required order of these components (base name, revision, extension)

o Program names generated automatically for all tester types in use at MSP test sites, through the web tool at http://www1.msp.sc.ti.com/test/ (Test Prog Num Req), already meet or exceed these requirements. 

Is not

o Specific requirements defining the syntax of the test program base name.

Requirements

Syntax

o Test program names will be UPPER CASE.

o Test program names will be composed of the following 3 components / fields: 

1. [base name] (the part of the test program name that doesn't change): Alphanumeric value 6 to 14 characters in length.

In cases where test program names includes one or more underscores "_", the base name will be defined as the portion of the test program following the last "_" and prior to the revision field.  Example: If the original program name was F711460a_75199202.itp, the the base name would be "751992".   Note: The test program will be physically stored as 75199202.itp at the production site.

2. [revision]: 1 alphanumeric character + 1 numeric digit

The 1st (leftmost) character of the revision field is recommended to denote "major" program revisions...significant changes to the test list or test order. (From 0 [zero] through the letter "Z", 36 possible values)   The major revision would be "0" for a new program, and would be incremented as follows: 0,1,2,3,4,5,6,7,8,9,A,B,C...   Existing test programs already using this convention would continue to increment from the current revision.

The 2nd (numeric only, 0-9) digit defines a "minor" program revisions...i.e. adjustments to test conditions or limits. See "impact to dataPOWER" note below:

3. [extension]: (refer to the list of extensions to be used for each test platform...see below)       Tester                         Extension

Assembly Checker                  .itpEagle .dllFusion                          .evaIntegra Flex           .xlsPolaris                         .<no extension>Teradyne Catalyst and A5xx      .loadVerigy V93K                                .tpgVLCT                            .itp Vseries                         .itp

In summary, the test program name will be specified (SMS kparm or dit file, etc.) and physically stored in the production test program directory as [base name]+[revision]+"."+[extension]

Additional examples: [K4A734T]+[01] = K4A734T01 (no extension needed) [K734A502P1ST]+[A1] = K734A502P1STA1 [712345]+[00].[itp] = 71234500.itp (Vseries example, requires .itp extension)[AC104600] = Assembly checker program example: TTFFFFRR ||||||++--- = Revision (1 alphnumeric + 1 numeric) |||||| ||++++----- = Freeform text for characters 3-6.       ++--------- = Tester Type (“AC” for assembly check programs)

Test program production program directory structure (general form) o <*productionDirName>/<*productionDirName>/$TESTER_TYPE/<Test

program name w/o extension>/<Test program with extension> o The default production program directory path (in bold/italics) used by

Testware is: /twprog/prod/$TESTER_TYPE/<base name>+<revision>/<base name>+<revision>+”.”+<extension>

$TESTER_TYPE is the value of  the lotinfo tag: TITESTERTYPE The test program owner is to insure that the test program directory

matches the test program name (minus the extension).

**end