Best design practices for DFT
Gunjot Kaur , Sidhant Goel & Mayank Parasrampuria (Freescale)
EDN (October 14, 2015)
SoC sub-components (IPs) generally come from various sources – internal and external – and with that it has become necessary that designers ensure the RTL is testable. If the RTL has testability issues, test coverage goals can’t be met and the RTL needs to be modified, which means several iterations of synthesis, verification, and Automatic Test Pattern Generation (ATPG).
Here we will discuss the basic design practices to ensure proper testability.
To read the full article, click here
Related Semiconductor IP
- DDR5 MRDIMM PHY and Controller
- RVA23, Multi-cluster, Hypervisor and Android
- HBM4E PHY and controller
- 64 bit RISC-V Multicore Processor with 2048-bit VLEN and AMM
- NPU IP Core for Mobile
Related White Papers
- SoC designers describe their 'best practices'
- Best Practices for a Reusable Verification Environment
- MBIST verification: Best practices & challenges
- Serial Peripheral Interface. SPI, these three letters denote everything you asked for
Latest White Papers
- QiMeng: Fully Automated Hardware and Software Design for Processor Chip
- RISC-V source class riscv_asm_program_gen, the brain behind assembly instruction generator
- Concealable physical unclonable functions using vertical NAND flash memory
- 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