Skip to main content

Lund University Publications

LUND UNIVERSITY LIBRARIES

No Fault Found: The Root Cause

Larsson, Erik LU orcid ; Eklow, Bill ; Davidsson, Scott ; Aitken, Rob ; Jutman, Artur and Lotz, Christophe (2015) IEEE VLSI Test Symposium
Abstract
No Trouble Found (NTF) has been discussed for several years [1]. An NTF occurs when a device fails at the board/system level and that failure cannot be confirm by the component supplier. There are several explanations for why NTFs occur, including: device complexity; inability to create system level hardware/software transactions which uncover hard to find defects; different environments during testing (power, thermal, noise). More recently a new concept, No Fault Found (NFF), has emerged. A NFF represents a defect which cannot be detected by any known means so far. The premise is that at some point the defect will be exposed - most likely at a customer site when the device is in a system. Given that we looking for a defect that we know... (More)
No Trouble Found (NTF) has been discussed for several years [1]. An NTF occurs when a device fails at the board/system level and that failure cannot be confirm by the component supplier. There are several explanations for why NTFs occur, including: device complexity; inability to create system level hardware/software transactions which uncover hard to find defects; different environments during testing (power, thermal, noise). More recently a new concept, No Fault Found (NFF), has emerged. A NFF represents a defect which cannot be detected by any known means so far. The premise is that at some point the defect will be exposed - most likely at a customer site when the device is in a system. Given that we looking for a defect that we know nothing about and are theoretically undetectable it will be interesting to see what the panel has to say about the nature of these defects and how we intend to find them. (Less)
Please use this url to cite or link to this publication:
author
; ; ; ; and
organization
publishing date
type
Chapter in Book/Report/Conference proceeding
publication status
published
subject
host publication
IEEE 33rd VLSI Test Symposium (VTS), 2015
pages
1 pages
publisher
IEEE - Institute of Electrical and Electronics Engineers Inc.
conference name
IEEE VLSI Test Symposium
conference location
Napa, United States
conference dates
2015-04-27
external identifiers
  • scopus:84940399363
ISBN
9781479975983
DOI
10.1109/VTS.2015.7116284
language
English
LU publication?
yes
id
3646ffb9-2fe1-4f73-8bce-a5cc26a5ea08 (old id 5205504)
date added to LUP
2016-04-04 11:04:44
date last changed
2025-04-04 14:10:55
@inproceedings{3646ffb9-2fe1-4f73-8bce-a5cc26a5ea08,
  abstract     = {{No Trouble Found (NTF) has been discussed for several years [1]. An NTF occurs when a device fails at the board/system level and that failure cannot be confirm by the component supplier. There are several explanations for why NTFs occur, including: device complexity; inability to create system level hardware/software transactions which uncover hard to find defects; different environments during testing (power, thermal, noise). More recently a new concept, No Fault Found (NFF), has emerged. A NFF represents a defect which cannot be detected by any known means so far. The premise is that at some point the defect will be exposed - most likely at a customer site when the device is in a system. Given that we looking for a defect that we know nothing about and are theoretically undetectable it will be interesting to see what the panel has to say about the nature of these defects and how we intend to find them.}},
  author       = {{Larsson, Erik and Eklow, Bill and Davidsson, Scott and Aitken, Rob and Jutman, Artur and Lotz, Christophe}},
  booktitle    = {{IEEE 33rd VLSI Test Symposium (VTS), 2015}},
  isbn         = {{9781479975983}},
  language     = {{eng}},
  publisher    = {{IEEE - Institute of Electrical and Electronics Engineers Inc.}},
  title        = {{No Fault Found: The Root Cause}},
  url          = {{https://lup.lub.lu.se/search/files/5689415/5205517.pdf}},
  doi          = {{10.1109/VTS.2015.7116284}},
  year         = {{2015}},
}