Home
Most Innovative Test Technoloy
 
Test Pattern Editorial from ChipScaleReview
Upgrading ATE systems for KGD Testing
Wednesday, 23 February 2011 17:23

Posted with permission from Chip Scale Review Jan 2011

www.chipscalereview.com

Paul Sakamoto  This e-mail address is being protected from spambots. You need JavaScript enabled to view it

 

One of the great “unsung heroes” of Moore’s Law is the ever-shrinking package around the die. After all, it’s hard to have tiny, hand-held digital devices if the silicon is packaged in FPGA packages. Today, that package has been reduced to the point that it is becoming a coating and some bumps on the die. Sometimes, it is a stack of these die that are connected with TSVs (Through Silicon Vias). In all cases, it is now a requirement that full-performance be guaranteed during wafer level test. This need may bring rise to many challenges for some companies. The one that we will address in this article is the need to upgrade the ATE used in the wafer test area.

A common practice over the years has been to partition device testing for SoC (System on Chip) devices so that older, lower-performance ATE is used for wafer test and newer, high-performance equipment is used for post-assembly test. This was largely because wafer tests, particularly speed and analog tests, were executed below specification to allow for the difficulties of creating a high-fidelity probe contact to the die. Slow gains in wafer test performance were made over the years to help eliminate waste at the post-assembly, final test level. Today, many of these older ATE systems are still able to test most of the device parameters, particularly the bulk of the digital pins for wireless applications, but they fall way short in the areas of HSIO (High Speed I/O), RF and lower speed analog. You can buy high performance probe interfaces, but the manufacturers of these older systems typically cease option development for these ATE in favor of newer products, upgrading old wafer test systems with OEM help is seldom an option. On the other hand, many new consumer devices have such a low cost structure that buying a new high-end system to test them is out of the question. A possible solution is to add an after-market upgrade.


Do-it-yourself upgrading of ATE has been happening ever since the first systems were shipped over 40 years ago. The popularity of this activity has not been all that broad, however, due to the lack of sufficient economic pressure. In the past, speed of development and throughput for chip test was the lead factor above test cost. Today the focus is changing somewhat to cost of acquisition of the equipment taking a much bigger role.


To illustrate the difference in approach between then and now, consider the following hypothetical conversation. The Boss says, “Bill, do we have to buy the new Blartfast 2000 ATE system to test the new part? It costs $2 million! Can’t you just modify the old Blartfast 1990?” Bill than responds, “Sure. Just give me $1M, five engineers and about a year. It’ll be fun. The instrument sales guy will like it too.” Of course, the Boss than says, “Never mind. Write up the Blartfast 2k requisition.” Today, the conversation would be more like, “Bill, you have two months and $200k to get the new parts ready to test. If you can’t get it done, your job goes to India.” Faced with this, Bill is now ready to begin home remodeling of his ATE.


So, what are some typical applications for DIY (Do It Yourself) ATE upgrades? SerDes I/O pins are a good target. Many new mobile devices use the MIPI protocol to communicate between cameras and the rest of the phone using just a few wires to send a lot of data. Other SerDes test challenges include HDMI, DP (display port), USB 3.0, PCIe, MDDI, and SATA. What makes these great candidates for the addition of a discrete instrument? They all consume relatively few device pins, have very high-speed requirements (GHz) and are often co-located on devices where the fundamental data rate of the other few hundred pins is <<200MHz. There is usually no viable OEM upgrade available (if there is, you should consider it). The other factor is to look at what the savings amount to, and in most of these cases it’s the difference between a $100k instrument or a $1.5M tester with options.

 

Some will argue that this kind of tester upgrade has poor throughput, but I would suggest that this is “old-school’ thinking and that modern instrumentation is often very competitive in speed of analysis. For many analog tests, it’s actually superior due to its ability to locally process captured test data.

 

For all of you test engineers that are frustrated designers and system integrators, rejoice! Your time has come to be the hero, or at least keep your job, and make your old testers new again with home-brew testing.

 

kgd

 
TSVs Bring New Test Trade-offs
Tuesday, 14 September 2010 00:07

Posted with permission from Chip Scale Review Sep 2010

www.chipscalereview.com

One of my favorite old TV series is "The Hitch Hiker’s Guide to the Galaxy" from the BBC. The story starts out when an average guy named Arthur Dent wakes up to find out that his home is about to be demolished to make way for a motorway. He is then informed by his friend Ford Prefect – who is actually an alien travel book researcher – that the Earth is about to be vaporized as part of a “Hyper-Space bypass” for extra terrestrial, faster than light-speed travelers. Many of you must now be wondering how this can possibly relate to test. Well, I think it reminds me of some of the trade-offs we face in the design and test of 3D (three dimensional) stacked packages with TSVs (through silicon vias). To make TSVs some silicon territory is being literally vaporized to make way for direct pathways between circuits on different die. A TSV might be ten or more microns in diameter, so the resulting area is large enough for a lot of digital mission-mode gates to occupy. This valuable space is sacrificed to save package and board space as well as to increase chip-to-chip signal performance; to create an effective “Hyper-space bypass” of sorts.

 

Today, the benefits of the TSV similarly overcome many of the evils that the process brings, including loss of silicon real-estate, because of the product benefits that come with them. However, when TSVs need to be placed for test access, the reception is not always so great because the test access path, often related to JTAG based scan architectures, does not have a lot to do with the mission mode of the devices in the stack. That is, the manufacturer doesn’t get to charge anybody for the silicon used for test access port space. It is viewed as “cost” or “expense” rather than “value added.” The result is that it makes sense to reduce the number of TSVs for test access and use the savings to reduce the area of the resulting chip design or to use the space for money-making circuits. The test access standard chosen for stacked die access will determine how much area is used for TSV connections, the physical layer of the TAP (Test Access Port), the type of ATE equipment needed, the ability to test in parallel, and the speed of test among other factors. Because the subject is evolving, complex and there are competing ideas, there is no agreed upon standard as of yet.

 

To help me through the fog of “if, what and maybe” for 3D testing, I called upon my old friend Al Crouch who is part of several groups who are wrestling with this topic. As always, Al overloaded my shrinking cranial capacity with masses of great information. We don’t have the space to cover it all in detail here, but what it comes down to is a couple of big architectural choices. The first choice is, given a fixed amount of test data and instructions, do you run more test access pins at moderate speed as 1149.1 JTAG tends to do today, or can we find a way to run fewer pins faster? Depending on the choice made, it’s possible to have as few as 2 pins, which connect through the stack as TSVs, or there could be more than 7 at the other extreme. Additionally, some of the architectures that use more pins require chip enable connections to select or de-select the die or function in the stack. This results in not only more area lost to TSVs, but the possibility of non-uniform test access footprint in the die stack since the enable signal might not be routed to all the die. As such, the higher pin count solutions tend to add pins to the TSV test access bus as the stack of die gets more layers. The two pin scheme can potentially stay limited to two pins in the stack because it will use packets to send test information to and from the appropriate circuit. Depending on who you talk with, packets in the test bus are either a simplification or a complication with respect to the test access circuitry. From an area standpoint, it’s quite likely the SERDES (serializer-deserializer) circuits in the two wire scheme will take up a lot less space than the TSVs of the full 1149.1 ports.

 

Other advantages of the two wire, packet transmission approach come at wafer sort. In some cases, the 3D device components at wafer sort may have almost no mission-mode functionality at all and scan based testing ala 1149.1 may be the only real test method for these KGDs (known good die) before assembly. That is, depending on how functionality is partitioned among the die in the stack, structural test is likely to be the only tool for creating the KGD test. Having only two pins per access port would allow more die to be tested in parallel, it reduced the probe card pins per die, and has other benefits. In fact, with some standardization of the test access and power supply pins, it may be possible to use one probe card for all the die in a stack. The more pins you use, the less likely this is. Also, remember that any pin to be probed needs to have a bonding pad as well as a TSV. This is another serious area hit.

 

I was able to speak with another friend who is in charge of the design of extremely large, high-performance chips at a large systems company. His chips will not have a high stack due to power, but will still use TSV for performance. Since these chips already have a couple of thousand pins and associated TSVs, the addition of a few extra TSV connections does not create an issue. However, the scalabilty of addressability native to packet signaling solutions still work out well in his case. Each of his chips might have many cores and a well designed packet architecture will help standardize the test access on each die and yet provide the flexibility to have sufficient test coverage.

 

In the accompanying illustration, you can see the difference in complexity between the two approaches. I am sure that a compromise will be reached by the time 3D becomes a larger percentage of shipments.

 

So, now you know some of the trade-offs of TSVs for test access, hyper-space bypasses and silicon motorways. Just remember, stay tuned for more developments here and as "The Hitch Hiker’s Guide to the Galaxy" said on its cover, “Don’t Panic.”

TSV

------------------------------------------------------------------------------------------

 

title

Posted with permission from Chip Scale Review Aug/Sep 2009

www.chipscalereview.com
Paul Sakamoto This e-mail address is being protected from spambots. You need JavaScript enabled to view it

The vast majority of today's test is accomplished in the digital
domain.  That is, numbers are generated and then converted into
analog signals that are applied to a device under test (DUT).  
DUT outputs are monitored for their analog output signals, which
are then turned into numbers that can be evaluated.  Note the
idea that all of the signals are analog and not digital.  Even
if a DUT is sending nominally binary data back and forth, today's
high performance components have I/O pins that always highlight
their analog behavior.  If your background in test came from the
computer science or IT arena, this is a really disturbing development.  
You perhaps thought you could retire or find another career before
learning analog.  Analog was the domain of those folks down the
hall that test the RF (radio frequency) devices.

 ed4-image

When we look at our mission in test, it is really about evaluating
data and making decisions based on the data.  To help make that notion
a reality, one would want to keep the need to understand analog signals
and signaling protocols to a minimum.  Ideally, the ATE (large,
expensive putty-colored box that does the testing) would be able
to convert information (high-level data) into the proper protocol
and signal and back again, all in real-time.  This is more complex
than simple "A/D" or "D/A" conversion because those old methods
leave the protocol and data generation and interpretation to the
test engineer.

This ideal ATE feature would keep the engineer's focus at a higher
level of abstraction (CE folks like that).  It enables the engineer
to program and think in terms of "send the ASCII character set into
the USB pin" instead of worrying about all the weird multi-level
dance that USB needs to get this done.  (Sorry for the weak example,
but you know I just write and manage people nowadays.)

Fortunately, solutions to the analog test issues are available.
Modern ATE options include instruments that have enough local
intelligence that they can execute high-level test commands
with MIPI, LVDS, DDRn, etc.  What this requires is that the instrument
be mounted close to the DUT in the ATE test head for signal fidelity
and that it must also have quite a bit of local intelligence.  The
local intelligence is often in the form of a micro-controller and
real time hardware based on high-performance FPGA fabric.  The FPGA
fabric is used so that new signal standards and protocols can be
implemented without the need to develop an entirely new set of
hardware for each new protocol or signal standard.

This puts the burden for the repetitive task of interfacing to a USB
3.0 pin on the domain experts at the instrument maker level versus
requiring every test engineer to re-invent this particular wheel.  
It is all made practical by the new FPGA technology, embeddable IP
cores, and other tools that allow the new breed of instruments to be
made capable of signal-to-information conversion while still having
great performance and the form factor to fit in an ATE test head.

Although this new architecture of signal-to-information conversion is
still new, the first few companies have fielded the first products,
and I expect the list to grow.  Just as I don't think much about
the signal conversions that happen between my thoughts and this
article, the test engineer should be freed to think about overall
test coverage rather than the minutiae of analog signal interface
in massively digital devices.

------------------------------------------------------------------------------------------

 
« StartPrev12NextEnd »

Page 1 of 2