Viewpoint: An Evolution in Design for Test
Sandeep Bhatia, Senior R&D Director, Oasys Design Systems
EETimes (2/16/2012 12:43 PM EST)
Designers relate to Design for Test (DFT) in much the way that small children relate to scary programs on TV: if they cover their eyes with their hands, perhaps it will go away. But every designer also knows that the design that they are so lovingly bringing into existence won’t see the light of day without addressing the test problem. After all, every single chip needs to be tested.
These days, there is a growing realization that DFT is evolving and, in particular, is not something that can be left to the end of the design cycle when some resident test expert lays his or her hands on the design and pronounces it good. We have all heard far too many stories of the last-minute chaos, and the inevitable schedule slips, that come from leaving test as an after thought. DFT in a modern design requires a systematic approach to planning early on.
To read the full article, click here
Related Semiconductor IP
- NPU IP Core for Mobile
- MSP7-32 MACsec IP core for FPGA or ASIC
- UHF RFID tag IP with 3.6kBit EEPROM and -18dBm sensitivity
- NPU IP Core for Edge
- Specialized Video Processing NPU IP
Related White Papers
- Design and Implementation of Test Infrastructure for Higher Parallel Wafer Level Testing of System-on-Chip
- Moving DFT to RTL overcomes test vector issues
- The evolution of embedded devices: Addressing complex design challenges
- Serial Peripheral Interface. SPI, these three letters denote everything you asked for
Latest White Papers
- Ramping Up Open-Source RISC-V Cores: Assessing the Energy Efficiency of Superscalar, Out-of-Order Execution
- Transition Fixes in 3nm Multi-Voltage SoC Design
- CXL Topology-Aware and Expander-Driven Prefetching: Unlocking SSD Performance
- Breaking the Memory Bandwidth Boundary. GDDR7 IP Design Challenges & Solutions
- Automating NoC Design to Tackle Rising SoC Complexity