Measuring Quality in Semiconductor IP
By Piyush Sancheti, Atrenta Inc
edadesignline.com (September 29, 2008)
Semiconductor IP reuse can yield a 2x improvement in design productivity for semiconductor companies. However, with these startling productivity gains come integration pain. Why? Semiconductor IP is essentially a black box for the SoC team that comes from various external sources, with varying and often unknown levels of quality and reusability. SoC designers must find a quality metric for semiconductor IP. If not, they may abandon its use.
Most semiconductor IP today is delivered as soft IP - register transfer level (RTL) or configurable generators that produce RTL. IP suppliers do ensure correct functional behavior. Often overlooked in this process is the communication of design intent and implementation feasibility, a task left for the IP consumer to deal with. A poorly designed IP can result in failures at the SoC level with timing, routing congestion, power, clock synchronization, test coverage, etc. Typically these issues will not be uncovered until after a significant engineering effort has been spent on integration of the IP into the SoC and subsequent implementation. The net result is expensive design iterations, project delays and potential silicon failure.
edadesignline.com (September 29, 2008)
Semiconductor IP reuse can yield a 2x improvement in design productivity for semiconductor companies. However, with these startling productivity gains come integration pain. Why? Semiconductor IP is essentially a black box for the SoC team that comes from various external sources, with varying and often unknown levels of quality and reusability. SoC designers must find a quality metric for semiconductor IP. If not, they may abandon its use.
Most semiconductor IP today is delivered as soft IP - register transfer level (RTL) or configurable generators that produce RTL. IP suppliers do ensure correct functional behavior. Often overlooked in this process is the communication of design intent and implementation feasibility, a task left for the IP consumer to deal with. A poorly designed IP can result in failures at the SoC level with timing, routing congestion, power, clock synchronization, test coverage, etc. Typically these issues will not be uncovered until after a significant engineering effort has been spent on integration of the IP into the SoC and subsequent implementation. The net result is expensive design iterations, project delays and potential silicon failure.
To read the full article, click here
Related Semiconductor IP
- ReRAM NVM in DB HiTek 130nm BCD
- UFS 5.0 Host Controller IP
- PDM Receiver/PDM-to-PCM Converter
- Voltage and Temperature Sensor with integrated ADC - GlobalFoundries® 22FDX®
- 8MHz / 40MHz Pierce Oscillator - X-FAB XT018-0.18µm
Related Articles
- Structural netlist efficiently verifies analog IP
- Analog IP verification guidelines
- Leverage always-on voice trigger IP to reach ultra-low power consumption in voice-controlled devices
- New Power Management IP Solution Can Dramatically Increase SoC Energy Efficiency
Latest Articles
- An FPGA-Based SoC Architecture with a RISC-V Controller for Energy-Efficient Temporal-Coding Spiking Neural Networks
- Enabling RISC-V Vector Code Generation in MLIR through Custom xDSL Lowerings
- A Scalable Open-Source QEC System with Sub-Microsecond Decoding-Feedback Latency
- SNAP-V: A RISC-V SoC with Configurable Neuromorphic Acceleration for Small-Scale Spiking Neural Networks
- An FPGA Implementation of Displacement Vector Search for Intra Pattern Copy in JPEG XS