IEEE 1450标准：半导体设计环境的STIL扩展指南

需积分: 10 154 浏览量更新于2024-07-09 收藏 956KB PDF 举报

IEEE Std 1450™1999, 简称STIL（标准测试接口语言），是一项由IEEE Computer Society的Test Technology Standards Committee发起并维护的行业标准，专为半导体设计环境提供测试接口扩展规范。该标准于1999年发布，并在后续版本中不断发展和完善，如IEEE Std 1450.1™-2005 (R2011)，它定义了STIL与数字测试生成工具和测试设备之间的接口，旨在增强测试过程的效率和一致性。 STIL的核心目标是建立一个标准化的测试接口，使得不同的测试工具能够无缝地与各种测试设备交互，从而实现测试流程的模块化和自动化。这包括但不限于支持自定义测试脚本、测试数据管理和测试结果分析等功能。通过STIL标准，测试工程师可以编写统一的测试程序，而无需关心底层硬件或设备的具体细节，提高了测试的灵活性和重用性。 1450.1™-2005版本对原版进行了扩展，可能包含了新的测试方法、测试策略、错误模型以及更高级的自动化功能。它可能涵盖了测试覆盖率分析、故障注入测试、模拟器接口、并行测试架构等关键领域的具体实现和指导。此外，这份标准还强调了文档的完整性和一致性，确保所有参与者都能理解和遵循相同的测试框架。值得注意的是，下载此标准时，用户必须遵守NORTH DAKOTA STATE UNIVERSITY的许可证限制，且可能受到来自IEEE Xplore平台的访问权限约束。这表明STIL是一个受版权保护的知识产权，仅在特定条件下允许使用。 IEEE Std 1450™1999/1450.1™-2005 (R2011) 是半导体行业测试自动化的重要里程碑，它通过标准化测试接口语言，推动了测试技术的进步，促进了测试工具厂商和设计工程师之间的协作，对于提升产品质量和缩短上市时间具有显著作用。随着技术的发展，未来可能会有更多针对新需求和技术更新的STIL扩展出现。

IEEE

Std 1450.1-2005 IEEE STANDARD FOR EXTENSIONS TO STIL (IEEE STD 1450-1999)

4.2 Reserved characters

Several reserved characters identified in STIL.0 are applied in additional contexts for this standard. Table 2

lists additional STIL reserved characters defined in this standard as well as additional contexts of previously

identified reserved characters. No change to reserved characters as defined in STIL.0 is made by this

standard. New reserved characters are so indicated in column two. All other characters in this table have

extended capability beyond that defined in STIL.0.

Table 2—Additions to STIL reserved characters

Char

New in

STIL.1

Usage

! exclamation (NOT sign): An inversion operator in expressions

% percent sign: Is used as the modulus in expressions and for parameter passing

to procedures and macros

( ) parentheses: Are used in expressions

* multiply: Is used in expressions

+ add: Is used in expressions

- subtract: Is used in expressions

&YESand: Is used in expressions

|YESor: Is used in expressions

^YESxor: Is used in expressions

~YESbit-wise negation: Is used in logic expressions

error return value: Is used when \W has no WFC chars to return

< less than: Is used in integer and real expressions

> greater than: Is used in integer and real expressions

<= less than or equal to: Is used in integer and real expressions

>= greater than or equal to: Is used in integer and real expressions

== equal to: Is used with pattern data expressions (i.e., to compare strings of

WFCs)

!= not equal to: Is used with pattern data expressions (i.e., to compare strings of

WFCs)

Authorized licensed use limited to: NORTH DAKOTA STATE UNIV. Downloaded on July 01,2014 at 03:50:26 UTC from IEEE Xplore. Restrictions apply.

IEEE

Std 1450.1-2005 IEEE STANDARD FOR EXTENSIONS TO STIL (IEEE STD 1450-1999)

4.4 Signal and group name characteristics

This clause defines extensions to STIL.0, Subclause 6.10.

All constructs and definitions in STIL.0, Subclause 6.10 are in effect. In addition, signals expressed with a

bracketed construct shall allow the use of a previously declared integer-constant, in which integer values are

allowed. See 5.1 for the definition of IntegerConstant.

4.5 STIL name spaces and name resolution

Additions to STIL.0, Subclause 6.16.

The Environment block augments the STIL name space as defined in Table 4. This table is incremental to

STIL.0, Table 6; all definitions present in that table remain unchanged.

Variable names and constant names are used by expressions. This name space also contains signal names,

signal group names, and spec variables defined for the context of that expression. Referenced variable-

names shall be unique against all signal names, signal groups names, and spec variable names defined for a

PatternBurst or application of a Pattern referenced by that PatternBurst.

Table 4—Additions to STIL name spaces

STIL block Type of name Domain restrictions

Environment Environment domain names Supports a single unnamed block and domain named

blocks. Domain names shall be unique across all

Environment blocks.

Variables Variables domain names Supports a single unnamed block and domain named

blocks. Domain names shall be unique across all

Variables blocks.

Variable s,

Signals,

SignalGroups,

Spec

Signal names

SignalGroup names

SignalVariable names

Spec variable names

Integer names

IntegerConstant names

WFCConstant names

Names present in this name space are dependent on

the domain reference statements in the PatternBurst

(SignalGroups domains, Variables domains) and the

PatternExec (Category domains).

It is an error for defined Variable or Constant names to

conflict with Signals, SignalGroups, or Spec variable

names accessible in the same context.

ScanStructures ScanCell names

ScanChain names (also used

for scan segments and cell

groups)

Names present in this space are dependent on the

domain reference statements for ScanStructures in the

PatternBurst. Scan cell names, scan chain names, and

cell group names in this common name space are

unique except if an unnamed ScanStructures block

exists. Names present in an unnamed block are

available unless hidden by a definition of the same

name in a named and referenced ScanStructure block.

Authorized licensed use limited to: NORTH DAKOTA STATE UNIV. Downloaded on July 01,2014 at 03:50:26 UTC from IEEE Xplore. Restrictions apply.

IEEE

FOR SEMICONDUCTOR DESIGN ENVIRONMENTS Std 1450.1-2005

5. Expressions

This clause defines extensions to STIL.0, Clause 6.

STIL.0 defines a limited usage of expressions; see STIL.0, Subclause 6.13 and Subclause 6.14. This standard

extends these expression capabilities with additional variable types (SignalVariable, Integer, IntegerConstant,

WFCConstant) and additional expression constructs. The use of operators and the expression constructs as

defined for STIL.0 is unchanged. The full set of STIL.0 and STIL.1 expression operations are defined in

Table 7. The detail of syntax and usage of the new expressions are defined in 5.1 – 5.13.

5.1 Constant and variable expressions

Expression constructs (which are defined in 5.2 – 5.13) can be divided into two classes: those that can be

completely resolved at parse time (i.e., constant expressions) and those that can only be resolved at run time

(i.e., variable expressions).

Constant expressions are those that contain only literal values (e.g., ‘5ns’ or ‘10ns’), or named constants

(e.g., Spec-Variable, IntegerConstant, and WFCConstant). As in STIL.0, statements that contain constant

expressions can be fully resolved once the STIL file/stream has been fully parsed and the domain references

have been resolved. Constant expressions can be used anywhere that the syntax definitions allow a literal

value. The use of constant expressions provides for (1) improved readability, (2) parameterized STIL data,

(3) enhanced reuse, and (4) improved maintainability.

Variable expressions are those that contain named variables, such as SignalVariable and Integer. The use of

variable expressions is intended primarily to support “design” applications. The ability of an ATE system to

support variable expressions may be limited, if possible at all.

Both constant and variable expressions can be further classified into “arithmetic expressions” and “pattern

data expressions.” The allowed constructs of each of these expression types are defined in 5.2 – 5.13.

5.2 Expression delimiters—single quotes and parentheses

Single quotes are defined in STIL.0 as the delimiter to be used around expressions. This usage is unchanged

with the introduction of new expression capabilities in STIL.1, and a STIL.0 file is completely compatible

with all STIL.1 rules. However, the rules governing the use of single quotes and parentheses are relaxed. The

following rules apply to the use of single quotes in STIL.1:

a) Single quotes, when used, are always the outermost symbols of an expression.

’T2+5ns’ // timing expression

’SIG1+SIG2+SIG3’ // signal group expression

b) Assignment and boolean operators shall not be used inside a single-quoted expression.

V { ’INT := INT+5’; } // illegal

If ’INT :== 5’ { } // illegal

c) Single quotes shall not be nested.

V {’BUS[1..’K+1’]’ = XXX; } // illegal - nesting of quotes

d) Wherever expressions are allowed, a single token may be used without delimiters. A single token

may be a literal value, a named constant, or a named variable.

V { INT := ’5’; } // single token with quotes

V { INT := 5; } // single token without quotes

V { INT1 := INT2; } // single token without quotes

Authorized licensed use limited to: NORTH DAKOTA STATE UNIV. Downloaded on July 01,2014 at 03:50:26 UTC from IEEE Xplore. Restrictions apply.

IEEE

Std 1450.1-2005 IEEE STANDARD FOR EXTENSIONS TO STIL (IEEE STD 1450-1999)

e) Wherever expressions are allowed, they may be represented without delimiters, with the exception

that if a multiterm expression is within a complex data stream, then the delimiters are required.

Examples of cases in which delimiters are required are shown in the later examples, using

parentheses.

V { INT := ’INT+1’; }

V { INT := INT+1; }

f) Parentheses may be used inside a single-quoted expression.

V { INT := ’(INT+1)*2’; }

V { ’(GRP-SIG)+SIG’ = 00001; } // make SIG the last WFC in the list

Parentheses are the preferred method of delimiting expressions in STIL.1. Parentheses can be used around

the entire expression or inside the expression to specify the order of processing. The following rules apply to

the use of parentheses:

g) Parentheses are allowed anywhere that single quotes are allowed in STIL.0.

V { (SIG1+SIG2) = XX; }

01 { (T2+5ns) D/U; }

h) Assignment expressions may be constructed with or without the use of delimeters.

V { INT := INT+1; }

V { INT := (INT+1); }

V { (INT := INT+1); }

V { INT := (X+2)*2; } // parens required to define order

V { SIG1+SIG2 = XX; }

V { (SIG1+SIG2) = XX; }

V { (SIG1+SIG2 = XX); }

i) Parentheses are not required to delimit boolean expressions; however, in practice, they are

commonly used.

If (\W(A+B) == \wxx) { }

If \W(A+B) == \wxx { }

If (\WGRP != \w\r(K+12) X) { }

If \WGRP != \w\r(K+12) X { }

j) Parentheses may be nested.

V {SIG = \r(K+12) X; }

If (\WBUS[1..(K-1) != \wXXX) { }

k) Parentheses are used to delimit parameters to functions within expressions.

V { INT := Min(X,Y); }

l) If a multiterm expression is within a complex data stream, then delimiters around the expression are

required.

SIG1 + SIG2 = XX;

\W(SIG1 + SIG2) == XX; // parens required

AB { 2ns D/U; }

AB { TIM D/U; }

AB { (TIM + 2ns) D/U; } // parens required

V { GRP = \r2 X YZ; }

V { GRP = \rTWO X YZ; }

V { GRP = \r(TWO+1) X YZ; } // parens required

V { GRP[5 9] = XX; }

V { GRP[K5 K9] = XX; }

V { GRP[(KK+5) (KK+9)] = XX; } // parens required

Authorized licensed use limited to: NORTH DAKOTA STATE UNIV. Downloaded on July 01,2014 at 03:50:26 UTC from IEEE Xplore. Restrictions apply.

剩余123页未读，继续阅读

mauser90

粉丝: 3
资源: 5

IEEE 1450标准：半导体设计环境的STIL扩展指南

Standard Test Interface Language (STIL)手册

Standard Test Interface Language (STIL) for Digital Test Vector Data.pdf

Standard Test Interface Language (STIL) for Digital Test Vectors原版

IEEE Standard for Extensions to Standard Test Interface Language

Alibaba-Dragonwell-Standard-11.0.18.14.9-x64-linux.tar.gz

com.springsource.osgi.extensions.equinox-2.0.5.release.jar

The.C.plus.plus.Standard.Library.Extensions.A.Tutorial.and.Reference.Jul.2006.chm

org.springframework.osgi.extensions.annotation-1.2.1.jar

pulp-rpm-consumer-extensions-2.16.4.1-5.1.el7.noarch.rpm

pulp-rpm-admin-extensions-2.13.4.8-1.el7.noarch.rpm

最新资源