15.01.2013 Views

U. Glaeser

U. Glaeser

U. Glaeser

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

FIGURE 44.4<br />

FIGURE 44.5<br />

It becomes evident that the isolation approach and the techniques to make a core test-ready depends<br />

on various design constraints such as area, timing, power as well as the test coverage needs for the core,<br />

and the core interconnect faults.<br />

Core Test Integration<br />

Testing SoC devices with multiple blocks (Fig. 44.4), each block embedding different test techniques,<br />

could become a nightmare without an appropriate test manager that can control the testing of various<br />

blocks. Some of these blocks could be user-designed and others predesigned cores. Given the current<br />

lack of any test interface standard in the SoC environment, it becomes very complex to control and observe<br />

each of the blocks. Two key issues must be addressed: sequencing of the test operations [4] among the<br />

various blocks, and optimization of the test interface between the various blocks and the chip I/O. These<br />

depend very much on the test architecture, whether test controllers are added to individual blocks or<br />

shared among many, and whether the blocks have adopted differing design-for-test (DFT) methodologies.<br />

A high-level view of the SoC test architecture is shown in Fig. 44.5, where the embedded test in each of<br />

the cores is integrated through a test bus, which is connected to a 1149.1 TAP controller for external<br />

access. Many devices are using boundary scan with the IEEE 1149.1 TAP controller not only to manage<br />

in-chip test, but also to aid at board and system-level testing. Some of the test issues pertain to the use<br />

of a centralized TAP controller or the use of controller in each block with a common test bus to<br />

communicate between various test controllers. In other words, it is the question of centralized versus<br />

distributed controller architecture. Each of these has implications with respect to the design of test<br />

functionality within each block.<br />

Besides testing each core through their individual access mechanism such as the core isolation wrapper,<br />

the complete testing of the SoC also requires an integrated test which tests the interconnects between<br />

the cores and the user-defined-logic (UDL). The solution requires, first to connect the test facilities<br />

© 2002 by CRC Press LLC<br />

DRAM<br />

User<br />

Logic<br />

Core<br />

An SoC includes multiple cores with memory and user logic.<br />

User-Logic<br />

Core<br />

Wrapper<br />

SRAM Core<br />

Core<br />

on-chip Test Controllers<br />

Core<br />

wrapper<br />

Test Bus<br />

1149.1 TAP<br />

A high-level architecture for SoC test integration.<br />

R<br />

O<br />

M<br />

User<br />

Logic<br />

D/A-A/D<br />

Core<br />

wrapper<br />

on-chip BIST controllers<br />

SoC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!