Embedded memory fail analysis for production yield enhancement

Advanced Semiconductor Manufacturing Conference(2011)

Cited 5|Views13
No score
Abstract
The traditional approach for memory fail bitmap analysis is to identify the topological signatures and perform a Failure Analysis investigation on the most frequent signatures, based on the (x, y) coordinates of the fails. This approach is inappropriate when a large portion of the fails are single bits, because too many investigations are required to statistically identify the major repetitive failure mechanisms. This becomes a problem for fast product development and production yield ramp. This paper presents a methodology to classify single fail bits by their unique fault signature, based on the sequence of failing march element read operations from multiple data backgrounds, in a standard Memory BIST flow. These classifications allow investigations to focus on the most important failure mechanisms with greatest yield impact. The methodology is demonstrated in an industrial environment, with identification of critical yield detractors. Starting from a yield problem associated to MBIST failures at high operating temperature, the fault signatures were used to identify a static noise margin parametric problem and a dislocation fault physical problem.
More
Translated text
Key words
built-in self test,embedded systems,failure analysis,integrated circuit yield,integrated memory circuits,logic testing,product development,critical yield detractors,dislocation fault physical problem,embedded memory fail bitmap analysis,failing march element read operations,fault signature,memory built-in self test,production yield enhancement,repetitive failure mechanisms,standard memory bist flow,static noise margin parametric problem,topological fault signature,bitmap,mbist,march algorithm,yield,object recognition,dislocations,algorithm design and analysis,transistors,algorithm design
AI Read Science
Must-Reading Tree
Example
Generate MRT to find the research sequence of this paper
Chat Paper
Summary is being generated by the instructions you defined