"IEEE1450.1标准pdf：数字测试矢量数据设计扩展的接口语言"

需积分: 5 47 浏览量更新于2024-03-19 收藏 659KB PDF 举报

The IEEE1450.1 standard pdf, also known as P1450.1 Working-Draft 14, Aug 1, 2002, is a document created by the STIL Working Group of the Test Technology Standards Committee. This standard focuses on the development of the Standard Test Interface Language (STIL) for Digital Test Vector Data Design Extension. The purpose of this standard is to provide guidelines and specifications for the creation of test vector data design extensions for digital testing. The document is copyrighted by the Institute of Electrical and Electronics Engineers, Inc., and is subject to change as it is still in the draft stage. The standard outlines the requirements for the design and implementation of digital test vector data, including the format and structure of the data, as well as the communication protocols and interfaces that should be used. The STIL Working Group has worked diligently to ensure that the standard meets the needs of the industry and provides a comprehensive framework for digital testing. The standard is designed to be flexible and adaptable to a wide range of testing scenarios, allowing for seamless integration into existing testing processes. Overall, the IEEE1450.1 standard pdf is a valuable resource for those involved in digital testing, providing detailed guidelines and specifications for the design and implementation of test vector data design extensions. It represents the latest advancements in digital testing technology and serves as a benchmark for excellence in the field.

P1450.1 Working-Draft 14, Aug 1, 2002

This is an unapproved IEEE Standards Draft, subject to change.

// of WaveformCharacter expressions):

C { ’w = ABBA’;}

V { siggrp = ’w’;}

} // end Pattern

6.7 Real Expressions (

real_expr

)

A real expression is deﬁned in a Spec table as deﬁned in IEEE Std. 1450-1999. The term real_expr is used in the syn-

tax deﬁnition to indicate where a real number is to be used. A real number can be expressed in one of two formats.

A real number can be of the form: <number>e<+\-><number>. A real number can be used to represent values that are

not standard SI units, for example a slew rate in volts/ns.

A real number can also be of the form <number><preﬁx><SI unit>. For example, ‘23ns’ is a time expression, ‘10uf’

is a capacitance expression. This generic reference can be used whenever one of the standard unit deﬁnitions is

allowed.

The following are examples of real number expressions:

STIL 1.0 { Design 2001; }

Header {

Source "P1450.1 Working-Draft 14, Aug 1, 2002";

Ann {* clause 6.7 *}

}

Spec {

Category cat {

time = ’25ns’;

wattage = ’25mw’;

slewrate = ’1v/1ns’;

realvar = ’25e-9’;

} // end Category

} // end Spec

Pattern pat {

C { ’time = 23.5ns + 1.5ns/2’; } // time expression

C { ’wattage = 5v * 2ua’; } // where wattage is of type ’Watts’

C { ’slewrate = 5v/1ns’; } // where slewrate is of type ’Real’

C ( ’realvar = 5v’; } // where realvar is of type ’Real’

C { ’realvar = 5ma’; } // where realvar is of type ’Real’

C { ’realvar = 5e-3’; } // where realvar is of type ’Real’

} // end Pattern

6.8 SignalVariable Expression (

sigvar_expr

)

SignalVariable expressions are enclosed in single quotes. Variables declared to be of type SignalVariable are assigned

WaveformCharacter list values, and signal references are assigned the value of Variables of type SignalVariable.

A WaveformCharacter list value results by direct assignment of a WaveformCharacter list, variable of type SignalVa-

riable, or variable of type SignalVariableEnum in a sigvar_expr. It is an error to manipulate a WaveformCharacter list

with operators or functions.

The application of signal variables is to hold signal data and to pass signal data from pattern vectors, macro calls or

procedure calls to macros, procedures or other vectors.

Signal variables are always have global scope and always retain their value upon return from a procedure or macro.

The following are examples of signal variable usage:

P1450.1 Working-Draft 14, Aug 1, 2002

This is an unapproved IEEE Standards Draft, subject to change.

Table 5 is expanded from Table 5 of IEEE Std. 1450-1999, to identify operator usage in additional expression types,

and to deﬁne the following operators not supported in IEEE Std. 1450-1999: % (modulus), ! (negation), && (boolean

and), || (boolean or), ~ (tilde, bit-wise negation), & (bit-wise and), | (bit-wise inclusive or), ^ (bit-wise exclusive or),

and ^~, ~^ (bit-wise equivalence). Logical behavior of these operators is the same as deﬁned in IEEE Std. 1364.

Table 5 deﬁnes the allowed operators on each type of variable. The table is ordered by precedence. Operators within

the bold line are of equal precedence and are processed left to right. Operators in each bold line separated group have

higher precedence that the groups below them and shall be processed ﬁrst.

sigvar_expr SignalVariable SignalGroups Pattern V { grp = ‘sv1’; }

V { grp = ‘sv2[1..5]’; }

V { grp = ‘sv3[5 4 2 3 1]’; }

logical_expr integer

time

real

SignalVariable

Signal

SignalGroup

SignalGroups

Spec

SignalGroups

Pattern Loop ’x*25’ { }

boolean_expr integer

time

real

SignalVariable

Signal

SignalGroup

SignalGroups

Spec

SignalGroups

Pattern

ScanStructures

If ‘i == 0’ {}

If ‘period > 23.0ns’ {}

If ‘value < 3e-6’ {}

If ‘sv2[1..5] == 11000’ {}

If ‘(s1==H) | (s2==H)’ {}

If ‘grp != HHHH’ {}

ScanEnable ’sig1==U’;

Table 5—Operators and functions allowed in expressions

Op Deﬁnition time real

int

eger

logic

bool

ean

sig

var

sig

ref

cell

ref

min() minimum value YES YES YES YES NO NO NO NO

max() maximum value YES YES YES YES NO NO NO NO

Merged-

Scan()

boolean function that returns true

to select BreakPoint or other

option during scan operation. See

clause 6.9.1.

NO YES YES YES YES NO NO NO

() parenthesis YES YES YES YES YES NO NO NO

table 3,

table 4 of

IEEE Std.

1450-1999

SI units & preﬁxes YES NO NO NO YES NO NO NO

/ divide YES YES YES YES NO NO NO NO

* multiply YES YES YES YES NO NO NO NO

% modulus NO NO YES YES NO NO NO NO

Table 4—Variable and Expression Usage

expr-type variable types where deﬁned where used syntax examples

P1450.1 Working-Draft 14, Aug 1, 2002

This is an unapproved IEEE Standards Draft, subject to change.

6.9.1 MergedScan function

The MergedScan() function returns a boolean value which is used to determine if scan operations are to be applied in

a merged or unmerged fashion. The behavior of merged and unmerged scan is described in clause 5.5 of IEEE Std.

1450-1999. The evaluation of this function shall be in the context of the STIL consumer environment. If the STIL

consumer environment has no speciﬁc needs for altering the merged scan operation then this function shall return a

default value of True.

This construct in conjunction with the If and Else constructs allow the STIL producer to generate STIL patterns/pro-

cedures/macros which represent both merged and unmerged scan operations. See annex N for an example.

7. Statement structure and organization of STIL information

This standard deﬁnes two additional top-level STIL blocks: Environment (clause 19), and BistStructures (clause 20).

These blocks relate to the top-level blocks of IEEE Std. 1450-1999 as deﬁned below.

+ add YES YES YES YES NO NO YES YES

- subtract YES YES YES YES NO NO YES NO

< less than (boolean value) YES YES YES YES YES NO NO NO

> greater than (boolean value) YES YES YES YES YES NO NO NO

<= less or equal (boolean value) YES YES YES YES YES NO NO NO

>= greater or equal (boolean value) YES YES YES YES YES NO NO NO

! negation (boolean value) NO NO YES YES YES NO NO YES

&& and (boolean value) NO NO YES YES YES NO NO NO

|| or (boolean value) NO NO YES YES YES NO NO NO

== equal (boolean value) NO NO NO YES YES NO NO NO

!= not equal (boolean value) NO NO NO YES YES NO NO NO

~ bit-wise negation NO NO YES YES NO NO NO NO

& bit-wise and NO NO YES YES NO NO NO NO

| bit-wise inclusive or NO NO YES YES NO NO NO NO

^ bit-wise exclusive or NO NO YES YES NO NO NO NO

^~, ~^ bit-wise equivalence NO NO YES YES NO NO NO NO

?: conditional expression YES YES YES YES YES NO NO NO

= assignment YES YES YES YES NO NO NO NO

.. range operator (ellipsis) NO NO NO NO NO YES YES YES

Table 5—Operators and functions allowed in expressions

Op Deﬁnition time real

int

eger

logic

bool

ean

sig

var

sig

ref

cell

ref

P1450.1 Working-Draft 14, Aug 1, 2002

This is an unapproved IEEE Standards Draft, subject to change.

7.1 Top-level statements and required ordering

The BistStructures blocks, if present, have a required ordering with respect to other STIL clauses deﬁned in IEEE

Std. 1450-1999. This ordering is shown in table 6. This table is incremental to table 7 in IEEE Std. 1450-1999 and

indicates the required position of the BistStructures block is following the ScanStructures blocks (if present). All

other deﬁnitions and requirements speciﬁed in Table 7 of IEEE Std. 1450-1999 remain unchanged.

7.2 Optional top-level statements

Environment blocks, if present, do not have a deﬁned order with respect to other STIL clauses deﬁned in IEEE Std.

1450-1999. Environment blocks may appear any place a top-level STIL statement is allowed. This is delineated in

table 7, which is provided to be complete with table 8 in IEEE Std. 1450-1999.

Some applications of the Environment block may place ordering constraints to satisfy issues speciﬁc to the applica-

tion of this data.

8. STIL statement - Extensions to STIL0 clause 8

The STIL statement identiﬁes the primary version of IEEE Std. 1450-1999 information contained in a STIL ﬁle, and

the presence of one or more standard Extension constructs. The primary version of STIL is deﬁned in IEEE Std.

1450-1999.

The extension to the STIL statement allows for a block containing extension identiﬁers that allow for additional con-

structs in the STIL ﬁle. There may be multiple Extension statements present, to identify the presence of multiple

extension environments. The extension name and the extension statements are deﬁned in the individual documents for

those standards.

All other constructs and restrictions for IEEE Std. 1450-1999 clause 8 are in effect here.

8.1 STIL syntax

STIL IEEE_1450_0_IDENTIFIER { (1)

( EXT_NAME EXT_VERSION; )+ (2)

} // end STIL

Table 6—Additions to STIL top-level statements and ordering requirements

Statement Purpose

ScanStructures As deﬁned in IEEE Std. 1450-1999.

BistStructures Deﬁnes internal BIST structure information. The BistStructures block or blocks are

optional. If there are multiple BistStructures blocks they shall be named. The Pattern

may contain a reference to a named BistStructures. BistStructures blocks shall be

deﬁned before the Pattern blocks.

Spec As deﬁned in IEEE Std. 1450-1999.

Table 7—Additions to Optional top-level statements

Statement Purpose

Environment Deﬁnes relationships of STIL data to external environments. Environment blocks, if

referencing other STIL data, shall be deﬁned after the blocks that deﬁne that STIL data,

unless those references are to information contained in MacroDefs, Procedures, or Pat-

tern blocks, which are allowed to be forward-references.

剩余100页未读，继续阅读

Nx9001

粉丝: 0
资源: 2

"IEEE1450.1标准pdf：数字测试矢量数据设计扩展的接口语言"

IEEE 802.11 pdf文件

IEEE 802.11标准官方PDF文档免费下载1

IEEE 1474.1.pdf

IEEE802.3协议PDF标准版

2021.01 IEEE 1003.13.pdf

IEEE1149.1标准

System Test Methodologies Using IEEE 1149.4.pdf

IEEE 802.3标准，IEEE 802.3-2018

IEEE 802.11标准官方PDF文档免费下载2

IEEE 802.11标准官方PDF文档免费下载5

最新资源