IEC 62528:2007
(Main)Standard Testability Method for Embedded Core-based Integrated Circuits
Standard Testability Method for Embedded Core-based Integrated Circuits
Defines a mechanism for the test of core designs within a system on chip (SoC).This mechanism constitutes a hardware architecture and leverages the core test language (CTL)to faciliate communication between core designers and core integrators.
General Information
Standards Content (Sample)
IEC 62528
Edition 1.0 2007-11
™
IEEE 1500
INTERNATIONAL
STANDARD
Standard Testability Method for Embedded Core-based Integrated Circuits
All rights reserved. IEEE is a registered trademark in the U.S. Patent & Trademark Office, owned by the Institute of
Electrical and Electronics Engineers, Inc.
Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from the IEC Central Office.
Any questions about IEEE copyright should be addressed to the IEEE. Enquiries about obtaining additional rights
to this publication and other information requests should be addressed to the IEC or your local IEC member National
Committee.
IEC Central Office The Institute of Electrical and Electronics Engineers, Inc
3, rue de Varembé 3 Park Avenue
CH-1211 Geneva 20 US-New York, NY10016-5997
Switzerland USA
Email: inmail@iec.ch Email: stds-info@ieee.org
Web: www.iec.ch Web: www.ieee.org
About the IEC
The International Electrotechnical Commission (IEC) is the leading global organization that prepares and publishes
International Standards for all electrical, electronic and related technologies.
About IEC publications
The technical content of IEC publications is kept under constant review by the IEC. Please make sure that you have the
latest edition, a corrigenda or an amendment might have been published.
ƒ Catalogue of IEC publications: www.iec.ch/searchpub
The IEC on-line Catalogue enables you to search by a variety of criteria (reference number, text, technical committee,…).
It also gives information on projects, withdrawn and replaced publications.
ƒ IEC Just Published: www.iec.ch/online_news/justpub
Stay up to date on all new IEC publications. Just Published details twice a month all new publications released. Available
on-line and also by email.
ƒ Electropedia: www.electropedia.org
The world's leading online dictionary of electronic and electrical terms containing more than 20 000 terms and definitions
in English and French, with equivalent terms in additional languages. Also known as the International Electrotechnical
Vocabulary online.
ƒ Customer Service Centre: www.iec.ch/webstore/custserv
If you wish to give us your feedback on this publication or need further assistance, please visit the Customer Service
Centre FAQ or contact us:
Email: csc@iec.ch
Tel.: +41 22 919 02 11
Fax: +41 22 919 03 00
IEC 62528
Edition 1.0 2007-11
™
IEEE 1500
INTERNATIONAL
STANDARD
Standard testability method for embedded core-based integrated circuits
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
PRICE CODE
XF
ICS 31.220 ISBN 2-8318-9481-6
– 2 – IEC 62528:2007(E)
IEEE 1500-2005(E)
CONTENTS
FOREWORD . 4
IEE Introduction . 7
1. Overview.9
1.1 Scope.10
1.2 Purpose.10
2. Normative references.10
3. Definitions, acronyms, and abbreviations.11
3.1 Definitions .11
3.2 Acronyms and abbreviations .16
4. Structure of this standard .17
4.1 Specifications.17
4.2 Descriptions . 18
5. Introduction and motivations of two compliance levels. 18
6. Overview of the IEEE 1500 scalable hardware architecture . 19
6.1 Wrapper serial port (WSP) . 19
6.2 Wrapper parallel port (WPP) . 19
6.3 Wrapper instruction register (WIR).20
6.4 Wrapper bypass register (WBY).20
6.5 Wrapper boundary register (WBR).20
7. WIR instructions .21
7.1 Introduction.21
7.2 Response of the wrapper circuitry to instructions .13
7.3 Wrapper instruction rules and naming convention .23
7.4 WS_BYPASS Instruction .24
7.5 WS_EXTEST instruction .25
7.6 WP_EXTEST instruction .27
7.7 Wx_EXTEST instruction. 29
7.8 WS_SAFE instruction.30
7.9 WS_PRELOAD instruction.32
7.10 WP_PRELOAD instruction.32
7.11 WS_CLAMP instruction.34
7.12 WS_INTEST_RING instruction.36
7.13 WS_INTEST_SCAN instruction.37
7.14 Wx_INTEST instruction.40
8. Wrapper serial port (WSP) .41
8.1 WSP terminals .42
9. Wrapper parallel port (WPP) .43
9.1 WPP terminals .43
10. Wrapper instruction register (WIR).43
10.1 WIR configuration and DR selection.43
10.2 WIR design .44
10.3 WIR operation.47
11. Wrapper bypass register (WBY). 49
11.1 WBY register configuration and selection. 49
Published by IEC under licence from IEEE. © 2005 IEEE. All rights reserved.
IEEE 1500-2005(E)
11.2 WBY design. 50
11.3 WBY operation .51
12. Wrapper boundary register (WBR).52
12.1 WBR structure and operation .54
12.2 WBR cell structure and operation.55
12.3 WBR operation events .56
12.4 WBR operation modes. 59
12.5 Parallel access to the WBR.61
12.6 WBR cell naming.63
12.7 WBR cell examples .64
12.8 IEEE 1500 WBR example . 68
13. Wrapper states.71
13.1 Wrapper Disabled and Wrapper Enabled states .71
14. WSP timing diagram.72
14.1 Specifications.72
14.2 Description.73
14.3 Synchronous reset timing.77
15. WSP configurations for IEEE 1500 system chips . 78
15.1 Connecting multiple WSPs. 78
16. Plug-and-play (PnP).81
16.1 Background and definition.81
16.2 PnP aspects of standard instructions.82
16.3 PnP limitations on protocols .83
16.4 Non-PnP in IEEE Std 1500.83
17. Compliance definitions common to wrapped and unwrapped cores .83
17.1 General rules .83
17.2 Per-terminal rules.85
17.3 Test pattern information rules.86
18. Compliance definitions specific to unwrapped cores .89
18.1 General rules . 89
18.2 Per-terminal rules.90
18.3 Additional test information rules .90
19. Compliance definitions specific to wrapped cores .91
19.1 General rules .91
19.2 Per-terminal rules.92
19.3 Wrapper protocol information rules .92
20. IEEE 1500 application .93
20.1 CTL (IEEE P1450.6) overview .93
20.2 IEEE 1500 examples.94
Annex A (normative) Bubble diagram definition. 110
Annex B (informative) WBR cell examples. 112
Annex C (informative) Relationship of IEEE Std 1500 to IEEE Std 1149.1 . 121
Annex D (informative) List of participants. 124
Published by IEC under licence from IEEE. © 2005 IEEE. All rights reserved.
– 4 – IEC 62528:2007(E)
IEEE 1500-2005(E)
INTERNATIONAL ELECTROTECHNICAL COMMISSION
___________
STANDARD TESTABILITY METHOD
FOR EMBEDDED CORE-BASED INTEGRATED CIRCUITS
FOREWORD
1) The International Electrotechnical Commission (IEC) is a worldwide organization for standardization
comprising all national electrotechnical committees (IEC National Committees). The object of IEC is to
promote international co-operation on all questions concerning standardization in the electrical and
electronic fields. To this end and in addition to other activities, IEC publishes International Standards,
Technical Specifications, Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter
referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC National
Committee interested in the subject dealt with may participate in this preparatory work. International,
governmental and non-governmental organizations liaising with the IEC also participate in this preparation.
IEC collaborates closely with the International Organization for Standardization (ISO) in accordance with
conditions determined by agreement between the two organizations.
2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an
international consensus of opinion on the relevant subjects since each technical committee has
representation from all interested IEC National Committees.
3) IEC Publications have the form of recommendations for international use and are accepted by IEC National
Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC
Publications is accurate, IEC cannot be held responsible for the way in which they are used or for any
misinterpretation by any end user.
4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications
transparently to the maximum extent possible in their national and regional publications. Any divergence
between any IEC Publication and the corresponding national or regional publication shall be clearly
indicated in the latter.
5) IEC provides no marking procedure to indicate its approval and cannot be rendered responsible for any
equipment declared to be in conformity with an IEC Publication.
6) Attention is drawn to the possibility that some of the elements of this IEC Publication may be the subject of
patent rights. IEC shall not be held responsible for identifying any or all such patent rights.
International Standard IEC/IEEE 62528 has been processed through Technical Committee
93: Design automation.
The text of this standard is based on the following documents:
IEEE Std FDIS Report on voting
1500(2005) 93/250/FDIS 93/261/RVD
Full information on the voting for the approval of this standard can be found in the report on
voting indicated in the above table.
The committee has decided that the contents of this publication will remain unchanged until
the maintenance result date indicated on the IEC web site under "http://webstore.iec.ch" in
the data related to the specific publication. At this date, the publication will be
• reconfirmed,
• withdrawn,
• replaced by a revised edition, or
• amended.
Published by IEC under licence from IEEE. © 2005 IEEE. All rights reserved.
IEEE 1500-2005(E)
IEC/IEEE Dual Logo International Standards
This Dual Logo International Standard is the result of an agreement between the IEC and the Institute of
Electrical and Electronics Engineers, Inc. (IEEE). The original IEEE Standard was submitted to the IEC for
consideration under the agreement, and the resulting IEC/IEEE Dual Logo International Standard has been
published in accordance with the ISO/IEC Directives.
IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating
Committees of the IEEE Standards Association (IEEE-SA) Standards Board. The IEEE develops its standards
through a consensus development process, approved by the American National Standards Institute, which
brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers
are not necessarily members of the Institute and serve without compensation. While the IEEE administers the
process and establishes rules to promote fairness in the consensus development process, the IEEE does not
independently evaluate, test, or verify the accuracy of any of the information contained in its standards.
Use of an IEC/IEEE Dual Logo International Standard is wholly voluntary. The IEC and IEEE disclaim liability for
any personal injury, property or other damage, of any nature whatsoever, whether special, indirect,
consequential, or compensatory, directly or indirectly resulting from the publication, use of, or reliance upon
this, or any other IEC or IEEE Standard document.
The IEC and IEEE do not warrant or represent the accuracy or content of the material contained herein, and
expressly disclaim any express or implied warranty, including any implied warranty of merchantability or fitness
for a specific purpose, or that the use of the material contained herein is free from patent infringement.
IEC/IEEE Dual Logo International Standards documents are supplied “AS IS”.
The existence of an IEC/IEEE Dual Logo International Standard does not imply that there are no other ways to
produce, test, measure, purchase, market, or provide other goods and services related to the scope of the
IEC/IEEE Dual Logo International Standard. Furthermore, the viewpoint expressed at the time a standard is
approved and issued is subject to change brought about through developments in the state of the art and
comments received from users of the standard.
Every IEEE Standard is subjected to review at least every five years for revision or reaffirmation. When a
document is more than five years old and has not been reaffirmed, it is reasonable to conclude that its contents,
although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to
determine that they have the latest edition of any IEEE Standard.
In publishing and making this document available, the IEC and IEEE are not suggesting or rendering
professional or other services for, or on behalf of, any person or entity. Neither the IEC nor IEEE is undertaking
to perform any duty owed by any other person or entity to another. Any person utilizing this, and any other
IEC/IEEE Dual Logo International Standards or IEEE Standards document, should rely upon the advice of a
competent professional in determining the exercise of reasonable care in any given circumstances.
Interpretations – Occasionally questions may arise regarding the meaning of portions of standards as they relate
to specific applications. When the need for interpretations is brought to the attention of IEEE, the Institute will
initiate action to prepare appropriate responses. Since IEEE Standards represent a consensus of concerned
interests, it is important to ensure that any interpretation has also received the concurrence of a balance of
interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are
not able to provide an instant response to interpretation requests except in those cases where the matter has
previously received formal consideration.
Comments for revision of IEC/IEEE Dual Logo International Standards are welcome from any interested party,
regardless of membership affiliation with the IEC or IEEE. Suggestions for changes in documents should be in
the form of a proposed change of text, together with appropriate supporting comments. Comments on standards
and requests for interpretations should be addressed to:
Secretary, IEEE-SA Standards Board, 445 Hoes Lane, P.O. Box 1331, Piscataway, NJ 08855-1331, USA and/or
General Secretary, IEC, 3, rue de Varembé, PO Box 131, 1211 Geneva 20, Switzerland.
Authorization to photocopy portions of any individual standard for internal or personal use is granted by the
Institute of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright
Clearance Center. To arrange for payment of licensing fee, please contact Copyright Clearance Center,
Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy
portions of any individual standard for educational classroom use can also be obtained through the Copyright
Clearance Center.
NOTE – Attention is called to the possibility that implementation of this standard may require use of subject
matter covered by patent rights. By publication of this standard, no position is taken with respect to the
existence or validity of any patent rights in connection therewith. The IEEE shall not be responsible for
identifying patents for which a license may be required by an IEEE standard or for conducting inquiries into the
legal validity or scope of those patents that are brought to its attention.
Published by IEC under licence from IEEE. © 2005 IEEE. All rights reserved.
– 6 – IEC 62528:2007(E)
IEEE 1500-2005(E)
IEEE Standard Testability Method
for Embedded Core-based
Integrated Circuits
Sponsor
Test Technology Technical Council
of the
IEEE Computer Society
Approved 30 June 2005
American National Standards Institute
Approved 20 March 2005
IEEE-SA Standards Board
Abstract: This standard defines a mechanism for the test of core designs within a system on chip
(SoC). This mechanism constitutes a hardware architecture and leverages the core test language
(CTL) to facilitate communication between core designers and core integrators.
Keywords: core test, embedded core test, IP test, test reuse
Published by IEC under licence from IEEE. © 2005 IEEE. All rights reserved.
IEEE 1500-2005(E)
IEEE Introduction
IEEE Std 1500 is a scalable standard architecture for enabling test reuse and integration for embedded cores
and associated circuitry. It foregoes addressing analog circuits and focuses on facilitating efficient test of
digital aspects of systems on chip (SoCs). IEEE Std 1500 has serial and parallel test access mechanisms
(TAMs) and a rich set of instructions suitable for testing cores, SoC interconnect, and circuitry. In addition,
IEEE Std 1500 defines features that enable core isolation and protection. IEEE Std 1500 will reduce test cost
through improved automation, promote good design-for-test (DFT) technique, and improve test quality
through improved access.
Core test language (CTL) is the official mechanism for describing IEEE 1500 wrappers and test data associ-
a
ated with cores. CTL is defined in IEEE P1450.6 ™ and was originally begun as part of the development of
IEEE Std 1500.
IEEE Std 1500 was broadly influenced by the past work of the IEEE Std 1149.1™ Working Group and has
several members from that group. IEEE Std 1149.1 and IEEE Std 1500 have similar goals at different levels
of integration. IEEE Std 1149.1 describes a wrapper architecture and access mechanism designed for the
purpose of testing components of a board whereas IEEE Std 1500 has a similar structure targeted towards
testing cores in an SoC.
IEEE Std 1500 has been a continuous effort for its participants due to the goal of resolving the needs of rec-
onciling and accommodating disparate test strategies and motives. The greatest effort has been put into sup-
porting as many requirements as possible while still producing a cohesive and consistent standard.
Objective of the IEEE 1500 effort
The Embedded Core Test Working Group was approved in 1997 with the charter to develop a standard test
method for integrated circuits (ICs) containing embedded cores, i.e., reusable megacells. That method would
be independent of the underlying functionality of the IC or its individual embedded cores. The method will
create the necessary testability requirements for detection and diagnosis of such ICs, while allowing for ease
of interoperability of cores originated from distinct sources. This method will be usable for all classes of dig-
ital cores including hierarchical ones (subclause 15.1 discusses hierarchical core-wrapper configurations).
In order to satisfy that charter, the Embedded Core Test Working Group was organized into several task
forces:
Core Test Language
Scalable Architecture
Compliance Definition/Information Model
Terminology/Glossary
Edition
Mergeable Cores Test
Benchmarking
Industry & Media Relations
a
Information on references can be found in Clause 2.
Published by IEC under licence from IEEE. © 2005 IEEE. All rights reserved.
– 8 – IEC 62528:2007(E)
IEEE 1500-2005(E)
Achievements
Since its inception, the Embedded Core Test Working Group has produced eight drafts of the preliminary
standard, considering all aspects of core-based test. Due concern has been given to ensuring that a broad
spectrum of users will be satisfied through flexibility. Both serial and parallel TAMs were developed. A
definition for core wrappers was created, and a set of instructions developed. The CTL was begun, and an
information model and compliance definition using that language were developed.
Notice to users
Errata
Errata, if any, for this and all other standards can be accessed at the following URL: http://
standards.ieee.org/reading/ieee/updates/errata/index.html. Users are encouraged to check this URL for
errata periodically.
Interpretations
Current interpretations can be accessed at the following URL: http://standards.ieee.org/reading/ieee/interp/
index.html.
Patents
Attention is called to the possibility that implementation of this standard may require use of subject matter
covered by patent rights. By publication of this standard, no position is taken with respect to the existence or
validity of any patent rights in connection therewith. The IEEE shall not be responsible for identifying
patents or patent applications for which a license may be required to implement an IEEE standard or for
conducting inquiries into the legal validity or scope of those patents that are brought to its attention.
Published by IEC under licence from IEEE. © 2005 IEEE. All rights reserved.
IEEE 1500-2005(E)
STANDARD TESTABILITY METHOD
FOR EMBEDDED CORE-BASED
INTEGRATED CIRCUITS
1. Overview
IEEE Std 1500™ defines a scalable architecture for independent, modular test development and test applica-
tion for embedded design blocks and also enables test of the external logic surrounding these cores. Modular
testing is typically a requirement for embedded nonlogic blocks, such as memories, and for embedded pre-
designed nonmergeable intellectual property (IP) cores. In addition, the IEEE 1500 architecture can also be
used to partition large design blocks into smaller blocks of more manageable size and to facilitate test reuse
for blocks that are reused from one system-on-chip (SoC) design to the next.
The IEEE 1500 architecture comprises hardware requirements, through the definition of a standardized core
wrapper, and uses a test-specific language to communicate information between core providers and core
users. This language is the IEEE P1450.6™ core test language (CTL). Although IEEE Std 1500 limited
itself to test aspects internal to nonmergeable cores, careful consideration was given to the interoperability
of such cores, resulting in plug-and-play (PnP) requirement definitions. SoC-specific issues such as those
related to the design of test access mechanisms (TAMs) are excluded from this standard and assumed to be
addressed by the SoC designer.
IEEE Std 1500 specifically focuses on defining test requirements for unidirectional non-tristate digital ter-
minals, as these represent a minimum and mandatory set of requirements upon which the more complex
bidirectional terminals are based. It is, therefore, implied that support for bidirectional or tristatable termi-
nals is provided only to the extent that the individual unidirectional terminals, i.e., the bidirectional or tristat-
able terminal, are available for IEEE 1500 wrapper insertion. In addition, the hardware architecture defined
in this standard anticipates a synchronous wrapper design methodology.
While IEEE Std 1500 does not discuss chip-level design, the architecture defined in this standard does not
prevent interfacing with IEEE 1149.1™-based standards. An example of this interface is provided in
Annex C for the reader’s benefit.
All rules described in this standard apply to the case where the IEEE 1500 wrapper is enabled (the wrapper
logic actively participates in the test of the core) except rules specific to the Wrapper Disabled state of the
IEEE 1500 wrapper. In Wrapper Disabled state, the IEEE 1500 wrapper is disabled, allowing functional
Information on references can be found in Clause 2.
Published by IEC under licence from IEEE. © 2005 IEEE. All rights reserved.
– 10 – IEC 62528:2007(E)
IEEE 1500-2005(E)
operation of the wrapped core. IEEE P1450.6 constructs were added to this standard, where appropriate, to
further guide the reader. It is anticipated that the reader will refer to these CTL constructs documented in
IEEE P1450.6. Additional discussion that complements the body of this standard are presented in annex
clauses:
— Annex A contains the legend for IEEE 1500 wrapper cells.
— Annex B shows examples of IEEE 1500 wrapper cells.
— Annex C presents similarities between IEEE Std 1500 and IEEE Std 1149.1 and discusses an exam-
ple interface between IEEE Std 1500 and IEEE Std 1149.1.
1.1 Scope
IEEE Std 1500 has developed a standard design-for-testability method for integrated circuits (ICs) contain-
ing embedded nonmergeable cores. This method is independent of the underlying functionality of the IC or
its individual embedded cores. The method creates the necessary requirements for the test of such ICs, while
allowing for ease of interoperability of cores that may have originated from different sources.
1.2 Purpose
The aim of IEEE Std 1500 is to provide a consistent scalable solution to the test reuse challenges specific to
the reuse of nonmergeable cores, while preserving the IP aspects that are often associated with these cores.
This objective is achieved through provision of a core-centric methodology that enables successful integra-
tion of cores into SoCs.
IEEE Std 1500 provides a bridge between core providers and core users and also facilitates the automation
of test data transfer and reuse between these two entities via the use of the IEEE P1450.6 CTL. This automa-
tion relies on information requirements (the information model) placed on the core provider to ensure that
the core can be successfully integrated by the core user. The result is shorter time to market for core provid-
ers and core users.
The data transfer and reuse from the core provider to the core user are based on the premise that the core test
data are left unchanged, while the test protocol is adapted from the IEEE 1500 hardware interface to the
SoC.
2. Normative references
The following referenced documents are indispensable for the application of this document. For dated refer-
ences, only the edition cited applies. For undated references, the latest edition of the referenced document
(including any amendments or corrigenda) applies.
IEEE Std 1149.1, IEEE Standard Test Access Port and Boundary-Scan Architecture.
IEEE P1450.6, Draft Standard for Standard Test Interface Language (STIL) for Digital Test Vector Data—
Core Test Language (CTL), http://grouper.ieee.org/groups/ctl/.
IEEE publications are available from the Institute of Electrical and Electronics Engineers, 445 Hoes Lane, Piscataway, NJ 08854,
USA (http://standards.ieee.org/).
Published by IEC under licence from IEEE. © 2005 IEEE. All rights reserved.
IEEE 1500-2005(E)
3. Definitions, acronyms, and abbreviations
This clause lists some definitions of terms that have been used throughout this standard. In addition, a list of
acronyms and abbreviations is also provided. The criteria for differentiating various terms are based on the
following rules:
a) General terminology in the scope of electrical engineering and/or test technology, which do not
influence the definition of this standard itself.
1) These terms are used in this standard without further explanation. It is assumed that the reader-
ship has sufficient background knowledge to understand these terms.
2) Some of these terms may already be defined in The Authoritative Dictionary of IEEE Stan-
dards Terms. Therefore, someone looking for a particular definition could always consult The
Authoritative Dictionary to verify the meaning of the term.
b) Terms that are specific to this standard
1) These terms are defined in this clause.
2) General definitions are valid throughout this standard.
3) Local definitions are relevant only to a specific clause of this standard.
Effort has been made to achieve consistent usage of all terms (e.g., wrapper, TAM).
3.1 Definitions
3.1.1 access mechanisms: Mechanisms by which signals may be propagated to and from a core, from either
embedded circuitry or from the primary inputs and outputs of the system chip. There are two types of access
mechanisms:
(a) Functional access: The mechanism for moving stimuli to and observing responses from a core or
user-defined logic (UDL) during functional operation or normal mode.
b) Test access: The mechanism for moving stimuli to and observing responses from a core or UDL dur-
ing nonfunctional operation or test mode.
3.1.2 auxiliary clock (AUXCK): A functional clock that may be used in conjunction with wrapper clock
(WRCK) during core test for capturing, shifting, updating, and optionally transferring test data in a wrapper.
3.1.3 bypass: As applied to core wrappers, an abbreviated sequential path connecting a wrapper serial input
(WSI) to a wrapper serial output (WSO).
3.1.4 captureWR: A wrapper terminal used to enable and control a Capture operation in the selected
IEEE 1500 wrapper register (WR).
3.1.5 cell functional input (CFI): For input wrapper cells, the cell’s input, which is connected to a wrapper
functional input (WFI); for output wrapper cells, the cell’s input, which is connected to a core output.
NOTE—See CFI pin in Figure 16.
3.1.6 cell functional output (CFO): For input wrapper cells, the cell’s output, which is connected to a core
input; for output wrapper cells, the cell’s output, which is connected to a wrapper functional output (WFO).
NOTE—See CFO pin in Figure 16.
3.1.7 cell test input (CTI): A wrapper boundary register (WBR) cell’s test data input.
3.1.8 cell test output (CTO): A wrapper boundary register (WBR) cell’s test data output.
Published by IEC under licence from IEEE. © 2005 IEEE. All rights reserved.
– 12 – IEC 62528:2007(E)
IEEE 1500-2005(E)
3.1.9 control: The process of applying test pattern stimuli.
3.1.10 core: Predesigned circuit block that can be tested as an individual unit.
3.1.11 core data register (CDR): Optional data register that belongs to a core being wrapped.
3.1.12 core input: An input terminal of an unwrapped core.
3.1.13 core integrator: An entity that incorporates one or more cores into an system on chip (SoC).
3.1.14 core isolation: A test mode feature preventing core-to-core or core-to-UDL (i.e., user-defined logic)
interaction.
3.1.15 core output: An output terminal of an unwrapped core.
3.1.16 core provider: An entity that designs cores that can be reused in other designs.
3.1.17 core test: A test methodology that is applied to an embedded core.
3.1.18 core test language (CTL): A standard language for core suppliers to provide test data that can be
used to test a core once it is integrated into a system on chip (SoC). The language presents a format to
describe test and support data so that the core can be effectively integrated, reused and tested.
NOTE—See IEEE P1450.6 reference documentation.
3.1.19 dedicated shift path: A shift path comprising storage elements that do not participate in functional
operation.
3.1.20 dedicated wrapper (cell): A wrapper style that does not share hardware with core functionality. This
style allows certain test operations to occur concurrently and transparently during functional operation.
This definition could apply to individual cells.
3.1.21 external safe state: A configuration of safe state in which the outputs of a core are in a state that pre-
vents them from interfering with a block of logic outside the core. See also internal safe state; safe state.
3.1.22 firm core: A predesigned block of functional logic such as a macro, megacell, or memory that has a
process technology-dependent netlist representation and may be amenable to some modification.
3.1.23 hard core: A predesigned block of functional logic such as a macro, megacell, or memory that has a
physical implementation that cannot be modified.
3.1.24 hybrid instruction: A wrapper instruction that has mixed use of wrapper serial port (WSP) and
wrapper parallel port (WPP) terminals.
3.1.25 input cell: A wrapper boundary register (WBR) cell that is provided on a core input.
3.1.26 internal safe state: A configuration of safe state whereby a core is protected from the impact of a test
outside the core. See also external safe state; safe state.
3.1.27 interoperability: See plug-and-play (PnP).
3.1.28 inward facing (IF) mode: The test mode where core inputs are controlled by the wrapper boundary
register (WBR) and core outputs are observed by the WBR.
Published by IEC under licence from IEEE. © 2005 IEEE. All rights reserved.
IEEE 1500-2005(E)
3.1.29 mergeable core: With respect to testability, a core that can be integrated with other cores and user-
defined logic (UDL) into a system on chip (SoC) so that a uniform design-for-test (DFT) methodology can
be applied across the entire system. A typical mergeable core is provided using a register transfer level
(RTL) or gate-level description.
3.1.30 merged core: With respect to testability, a core that is integrated with other cores and user-defined
logic (UDL) into a system on chip (SoC) so that a uniform design-for-test (DFT) methodology could be
applied across the entire system.
3.1.31 nonmergeable core: With respect to testability, a core that cannot be integrated to apply a uniform
design-for-test (DFT) methodology to the entire system on chip (SoC). A typical nonmergeable core comes
with a physical design implementation that does not accommodate modification of the test methodology. A
nonmegeable core may be represented as a block-box design, making standard automatic test pattern gener-
ation (ATPG) impossible on such a core.
3.1.32 nonmerged core: With respect to testability, a core that has not been integrated with other cores and
user-defined logic (UDL) into a system on chip (SoC) so that a uniform design-for-test (DFT) methodology
could be applied across the entire system.
3.1.33 normal mode: The mode in which the wrapper boundary register (WBR) does not interfere with the
functional operation of a wrapped core.
3.1.34 observation: The process of monitoring pattern response.
3.1.35 output cell: A wrapper boundary register (WBR) cell that is provided for a core output.
3.1.36 outward facing (OF) mode: The test mode where wrapper functional outputs (WFOs) are controlled
by the wrapper boundary register (WBR) and wrapper functional inputs (WFIs) are observed by the WBR.
3.1.37 parallel instruction: A wrapper instruction that uses wrapper parallel port (WPP) terminals and also
configures the wrapper bypass register (WBR) between wrapper serial input (WSI) and wrapper serial out-
put (WSO).
3.1.38 pattern set: A collection of test vectors intended for manufacturing test. In the context of core test
language (CTL), a pattern set is a collection of pattern constructs and their associated macros and procedures
brought together with PatternBurst and PatternExecs.
3.1.39 plug-and-play (PnP): A minimum level of interoperability between various core wrappers in a sys-
tem on chip (SoC).
3.1.40 safe data: Data that satisfy safe state configuration requirements. These data are user-defined.
3.1.41 safe state: A property whereby a test of one block of logic is prevented from interfering with or dam-
aging another block of logic. See also external safe state; internal safe state.
3.1.42 selectWIR: The IEEE 1500 wrapper terminal that determines the selection of a wrapper register
(WR). A value of 1 represents selection of the wrapper instruction register (WIR), and a value of 0 repre-
sents selection of a wrapper data register (WDR).
3.1.43 serial instruction: A wrapper instruction that exclusivel
...








Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.
Loading comments...