From: owner-stds-1450-4@majordomo.ieee.org on behalf of Ernst_Wahl [wahl@dcf105.agere.com] Sent: Thursday, October 30, 2003 5:55 AM To: stds-1450-4@majordomo.ieee.org Subject: stds-1450.4: Action set starter kit The following is intended as a starting point for defining a set of STIL.6 Actions. Minimum requirements are the existence of: 1. integer/boolean symbols 2. logical expressions using operators ! && || == != > >= < <= () I'm short on time so i ripped the following out of my header file comment section. Action set starter kit: ExecIf (Pre Action): if LogicExpr is True, the associated Test and either the Pass or Fail Actions are executed, else testing continues without executing Pass Actions at the Pass TestFlownode. Actions preceding ExecIf in the ActionList are executed unconditionally. Actions following ExecIf, like the associated Test, are executed only if LogicExpr is True. Invert (PreAndOrPost Action): logically invert an IntSym. InvertIf (PreAndOrPost Action): if LogicExpr is True, then logically invert an IntSym. Assign (PreAndOrPost Action): assign a value to an IntSym. AssignIf (PreAndOrPost Action): if LogicExpr is True, then assign a value to an IntSym. Bin (Post Action): if the bin associated with this Action is SoftwareBin::Default, then set the default Test fail bin if defined or generate a WARNMSG if not. If the bin associated with this Action is is SoftwareBin::Undefined, set no bin. If the bin is any other value, then set that bin. If this is a pass bin continue testing. If this is a fail bin, stop if in production mode, or continue testing if in override-on or characterization mode. Accumulate bins if the tester allows. See SoftwareBin::FailBin for predefined failbins (multiply by -1, i.e., pass bins are positive numbers, fail bins are negative). BinIf (Post Action): if LogicExpr is True then set bin "binThen", else set bin "binElse". If "binThen" or "binElse" is SoftwareBin::Default, then set the default Test bin if defined or generate a WARNMSG if not. If "binElse" is SoftwareBin::Undefined, don't bin ("binThen" should never be SoftwareBin::Undefined). If this is a pass bin continue testing. If this is a fail bin, stop if in production mode, or continue testing if in override-on or characterization mode. Accumulate bins if the tester allows. See SoftwareBin::FailBin for predefined failbins (multiply by -1, i.e., pass bins are positive numbers, fail bins are negative). ActIf (PreAndOrPost Action depending on content): nested and/or unsymmetric Action(s) inside an if-then-else form. If LogicExpr is True then carry out Action "actionThen" else carry out Action "actionElse". "actionThen" and "actionElse" may be of type ActionList, Assign, AssignIf, Bin, BinIf, or ActIf. ActionList (PreAndOrPost Action depending on content): represents one or more Actions for use with Action ActIf. The Actions may be of type Assign, AssignIf, Bin, BinIf, or ActIf. Perhaps you noted the absence of a separate "Stop" entity or parameter to "Bin". This was merely an admission of impotence: tester manufacturers do what they want. This is where a standard mught do some good. ----------------------------------------------------------------------- Ernie Wahl Agere Systems Tel: 610.712.6720 Computer-Aided Test 22F-218B, 555 Union Blvd Fax: 610.712.4235 Allentown, PA, 18109 Email: ejwahl@agere.com -----------------------------------------------------------------------