Posts Tagged ‘BIST’

3D Stacked Die Create Unique Test Issues

Thursday, December 2nd, 2010

By Ann Steffora Mutschler
While 3D die stacking promises a number of benefits including smaller footprint, faster speed, lower power and possibly lower cost, testing those devices isn’t going to be simple.

There are varying degrees of challenges aligned with varying types of defects that occur throughout the process, from wafer fabrication to package assembly to system-level assembly. And at each level, there are phenomena that impact quality and that lead to potential defects, said Ed Malloy, product manager for Encounter Test at Cadence Design Systems.

At the wafer level are all of the challenges normally seen in a non-3D scenario, including design and process related defects—traditionally called “stuck at” and delay-based defects, which are timing or process-related defects. With the “stuck at” or static types of defects at the wafer level, the dynamic defects are typically process-related, where a higher resistance might occur on a trace on the die that slows the signal down.

Both of these challenges become even more complicated by the stacking process. “As you stack these devices, there are thermal impacts that need to be modeled and understood,” Malloy said. “So as we go down the process curve the cell behavior becomes more widely varying depending on your process and your temperature. The temperature fluctuations have a significant impact on the quality of your signal integrity. So if you’re not understanding the thermal characteristics or dynamics that exist between the stacked devices, then this can lead to failure.”

Effective testing of 3D integrated devices starts with having a high-quality ‘known good die’ (KGD) test, explained Greg Aldrich, director of marketing for the Silicon Test Systems group at Mentor Graphics.

“The first step in testing for a 3D package is to be able to test the wafers or the standalone die before any packaging gets started. Typically that will get done at wafer test, so you’re testing multiple wafers that will eventually get packaged together. You have to have a test that does a very high quality and tries to detect everything you can possibly detect before you start packaging the individual die.”

One of the biggest challenges with 3D stacking has to do with the number of pins because there may not be access to all of the pins during wafer probe. Many more pins are used in 3D stacking, but a large number will not get packaged. Instead, they will be attached with a through-silicon via (TSV) or in another way, and there may not be big enough probe pads to probe them during wafer test.

“Today’s probe technology is unable to handle the finer pitch and dimensions of TSV tips. The wafer has to be thinned by about 75% for them to be stacked, but what happens is that the tips of the TSVs can be exposed. So as the thinned wafer is contacted by the wafer probe there is a danger of damaging the wafer,” explained Samta Bansal, product marketing for Encounter digital implementation system, and 3D IC guru, at Cadence Design Systems.

“You may have thousands and thousands of internal pins and you are only bonding out a very small subset. So especially after you get the package together, how do you get access to everything and fully test everything from a very small number of pins?” said Mentor’s Aldrich.

Mentor does all testing through a TAP (test access port) interface, under the IEEE boundary scan specification 1149.1 that has a 5-pin interface for test access. For example, all of its BIST is initiated and results gathered through the TAP interface.

A second piece of the 3D testing involves the interconnect between the package to verify everything that goes through the TSVs, as well as things that can be bonded out and packaged separately, he said. In testing the interconnect there could be two SoCs stacked on the package, for example, and there may be a lot of different types of interfaces between those SoCs. Some may be standard digital, some may be analog signals, and some may be high-speed serial-bus interfaces. Another scenario could be a memory chip, like a DRAM, stacked on top of an SoC. In both cases, the SoCs or the memory must be fully tested once it is sitting in the package.

Aldrich noted that Mentor is leveraging all of its technology in a different methodology. “For example, for testing a memory chip that’s sitting on top of an SoC, we can take our memory BIST and instead of putting it on the same die that the memory exists—which is what we would typically do for embedded memory—we can put it on the SoC and then interface the BIST for that memory through the normal bus interface between the memory and the DRAM. So with the memory BIST logic sitting on the SoC we can then test the DRAM chip itself. It’s a different methodology of using some of the BIST logic that we have.”

For testing the die-to-die interconnect, IEEE 1149.1, the boundary scan standard for single-ended digital signals can be used to test all the signals in between SoCs in a stack, and IEEE 1149.6 that is for AC coupled differential signals.

Managing power during test
As the industry moves down the process nodes, the consumption of power during test mode is impacting signal integrity of the chips, therefore power must be managed during test mode. “Traditionally test mode consumes anywhere between 2X and 5X the power of a normal functional mode. Because of the variations in the lower processes, you can’t afford to have these wider swings of power – they impact not only the signal integrity but the reliability. You can have early defects if you’re not managing power, so they can pass on a tester but fail in the field. By managing power at the wafer level, it mirrors the power consumption during functional mode – that’s an essential part of ensuring that ‘known good die’ are going into the 3D assembly process,” Cadence’s Malloy explained.

Within the 3D package device itself, power consumption must also be managed including memories, which can consume a lot of power, he said. “When they do, it affects temperature, which affects performance, and signal integrity – it’s a spiraling effect. So you have to have the capability to manage your memory tests, your logic tests and all the power. At the same time, you need to be testing areas that would potentially be susceptible to thermal effects: there may be some high risk areas that you would want to test after assembly. An easy one would be to model and test the through silicon vias and interface as well as the communication across chips. Of course you want to check the connectivity but still need to be checking some of the core logic and how it’s behaving once these devices are packaged.”

As part of a 3D stacked die methodology a test sign-off or test vector sign-off should be included in order to know where potential hot spots may be, which power analysis tools can do.

Other companies doing work with 3D ICs include Apache Design Solutions, which in last several years, has been working with a number of leading semiconductor companies including TSMC on 3D ICs. In fact, in June, TSMC included Apache’s 3D IC power and noise tools in its Reference Flow 11.0 and Analog/Mixed-Signal (AMS) Reference Flow 1.0.

The drive to reduce power and increase performance demands advanced packaging technologies such as SiP and 3D-IC/TSV. Apache recognized that these technologies pose major power, thermal, and stress challenges due to the coupling of power delivery network between digital and analog dies and their heat transfer properties. As such, Apache’s tools generate CPM and CTM as hand-off compact models representing the die power and thermal behaviors, and are extended to utilize CPM and CTM for multi-die chip-package analysis.

For additional information on this subject there are two blogs of note:

–Samta Bansal’s blog.
–Ed Malloy’s blog.

Rethinking Test

Thursday, February 11th, 2010

By Ann Steffora Mutschler

The responsibility of semiconductor test has long sat solely with the test engineer as the chip designer focused on the functionality of the device. However, particularly in low-power designs, when the device is being tested, much higher power levels are applied than normal functional operation – sometimes causing the device to fail.

This ‘false failure’ can lead to unnecessary yield loss on the production line requiring significant time and effort to diagnose because the extra power applied to the device may indicate incorrectly that the device is bad when it is not.

The goal of the test engineer is to reduce the cost to test a device. Therefore, they want their automatic test pattern generation (ATPG) tools to generate a lot of activity and test a lot of the chip. As a result, a lot of power is being consumed—typically exceeding the functional power budget between 7x to 10x.

This occurs because the chip is designed with a power budget in functional mode. “If you think about the design of a chip, most chips aren’t operating all parts of the chip at the same time and ATPG doesn’t look at functionality — it just looks at the structure and to minimize the cost or minimize the patterns it’s trying to make as much activity happen in the chip in order to get test all simultaneously,” explained Robert Ruiz, senior product marketing manager for test automation products at Synopsys.

In the past, ATPG tools really didn’t need to look at power consumption — the chips were small enough, the power rails were big enough, and there wasn’t a big prevalence of low-power designs. On top of that, there weren’t compression techniques being used, which further exacerbates the problem because the goal of a low-power design is to minimize switching activity, while the goal of compression is to maximize it. This is a very big deal for test engineers, but it is not an issue traditionally highlighted in the design community given designers’ focus on functionality—even though designers may take partial ownership about how to implement some of the design-for-test solutions.

Ruiz indicated that approximately three years ago the impact of power on test became a big area of Synopsys’ R&D effort based on feedback from a number of customers. At that time, he said, there were some customers who reported power issues related to test. They did some redesign, which resolved the issues at hand, but believed it could be a problem in the future. “It has certainly evolved to the point where most customers say they definitely have found a power issue during test,” Ruiz said.

Test is tricky for low-power designs
Greg Aldrich, director of marketing for the Silicon Test Systems group at Mentor Graphics Corp. said one of the problems in test is how to create test patterns that have lower power profiles in terms of what data gets shifted in, which is dramatically complicated by the use of on-chip compression and on-chip test structures. Previously, test was performed by shifting data into scan chains, issuing the clock cycle, shifting the data out, and then comparing it to the golden response data, whereby the scan chains were directly connected to the tester.

However, most designs today utilize either built-in self test (BIST) or on-chip/embedded compression, which is still a deterministic process. But instead of the tester directly shifting data into the scan chain, there is a decompressor that it goes through that sits on chip. The tester shifts data into the decompressor, which is expanded internally, essentially creating the data on-chip, Aldrich explained.

What complicates the process is that since the data is being created on chip a new on-chip piece of logic must also be created, so Mentor invented a new low-power decompressor that allows the designer to control the stuff on chip, he said. “It’s not as simple as just changing what’s on the tester. You actually have to change some of the embedded test logic on chip to be able to control that. I think that is going to be primarily how switching activity is going to be controlled during the test—by controlling how the test patterns are created and then how the test patterns are loaded.”

Similarly, Synopsys rolled out an ATPG approach that doesn’t require any hardware or DFT change (which no customer really wants to do), Ruiz said. The company’s TetraMAX tool was enhanced about three years ago to allow the user to dial in a budget of the switching activity, which serves as a proxy for power consumption. And, if a customer wants to be more aggressive and active in managing power consumption, there are other hardware techniques including Synopsys’ DFTMAX tool as it puts off the scan chain.

Likewise, Mentor’s Aldrich noted that in terms of innovations both on the design side as well as on the test side to help deal with the impact of power on test, “It’s all focused on how to reduce the switching activity during the test. Historically, a lot of that has been done by partitioning the test and that is still the case especially as you move to designs that have multiple voltage domains or multiple power islands. Being able to just sequence the tests for each one of those allows you to test a smaller piece of the design. That has some implications on the test time and cost that it takes to test the device but that’s one approach.”

Mentor has also added more control into its tools as to how much is switching during the test process. For example in its ATPG tools, users can specify constraints to the test pattern generation tool to indicates how much switching is allowed during the test pattern.

“The more aggressive they are in terms of lowering the amount of switching during the test process, the higher it is in terms of test costs. It’s going to take more test patterns, it’s going to take more compute time to create the test patterns but it is a knob they will have control over now. They really have no other choice other than designing the power structures in the design such that they can handle 50% switching activity—that’s the only other alternative,” Aldrich said.

In the end, the objective of test is to create the highest coverage in the smallest number of test patterns. What that means from the perspective of the design, it means you want to try and switch on everything possible in the design on every cycle on the tester—and that’s the opposite goal of low-power design. That said, a complete rethinking of compression algorithms and other test technology is in order.