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
- nQrux® Root of Trust IP
- AXI to UCIe Bridge IP
- UCIe 2.x Controller IP
- SWI3S (SoundWire I3S Interface) Peripheral Controller Core IP
- OpenTitan-based RISC-V Secure Element
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
- A Secure dToF LiDAR SoC with Dual-Domain Fingerprinting and Event-Driven AFE Circuit Achieving Sensor-Level Attack Resilience
- ZTA-Q: an Open-source RISC-V Platform for Accurate Quantized CNN Inference
- Automated Pre-Silicon Verification of High-Speed DDR5 and LPDDR5/6 Memory Controllers: Closed-Loop Timing, Mode Register, and PHY Synchronization in UVM
- U-Sonic: An Open-Source 8-Channel Ultrasound Transmit IP in a 130 nm RISC-V SoC
- S-ALSA: Co-Design of Adiabatic Logic-based Sensing and Balanced Bit-Cells for Secure and Energy-Efficient MRAM