Design for testing: Difference between revisions

Content deleted Content added
I have added the relevant reference source on the page.
No edit summary
Line 45:
== Debug using DFT features ==
In addition to being useful for manufacturing "go/no go" testing, scan chains can also be used to "debug" chip designs. In this context, the chip is exercised in normal "functional mode" (for example, a computer or mobile-phone chip might execute assembly language instructions). At any time, the chip clock can be stopped, and the chip re-configured into "test mode". At this point the full internal state can be dumped out, or set to any desired values, by use of the scan chains. Another use of scan to aid debug consists of scanning in an initial state to all memory elements and then go back to functional mode to perform system debug. The advantage is to bring the system to a known state without going through many clock cycles. This use of scan chains, along with the clock control circuits are a related sub-discipline of logic design called "Design for Debug" or "Design for Debuggability".
<ref>[https://www.pcloudy.com/functional-testing-vs-non-functional-testing/ "In functional testing the focus should be on the user-friendliness"]{{date=JulyJan 20192020 |bot=InternetArchiveBot |fix-attempted=yes }}
article by Bala, EDN, 701/3009/20192020</ref>
 
== See also ==