Semico's list of 10 reasons why it’s taken so long for SoC design teams to adopt IP. How many apply to your team?
February 4, 2011
For those of us who formerly purchased IP in the form of 40-pin DIPs, the idea of using IP to design SoCs isn’t so foreign. However, for people accustomed to designing everything under the hood of their latest ASIC, the idea has seen surprisingly slow adoption. Semico’s new IP report, “IP Subsystems: The New IP Market Paradigm,” lists 10 reasons for the slow uptake. With author Rich Wawrzyniak’s kind permission, I have decided to list them here.
Related Semiconductor IP
- Process/Voltage/Temperature Sensor with Self-calibration (Supply voltage 1.2V) - TSMC 3nm N3P
- USB 20Gbps Device Controller
- SM4 Cipher Engine
- Ultra-High-Speed Time-Interleaved 7-bit 64GSPS ADC on 3nm
- Fault Tolerant DDR2/DDR3/DDR4 Memory controller
Related Blogs
- The Arm Ecosystem: More than Just an Ecosystem, it's Oxygen for SoC Design Teams
- Smarter SoC Design for Agile Teams and Tight Deadlines
- Some critical considerations for SoC and Silicon Realization teams thinking about using ARM Cortex-A7 or ARM Cortex-A8 processor cores
- Why SoC Design Teams Still Struggle in a Connected World
Latest Blogs
- Shaping the Future of Semiconductor Design Through Collaboration: Synopsys Wins Multiple TSMC OIP Partner of the Year Awards
- Pushing the Boundaries of Memory: What’s New with Weebit and AI
- Root of Trust: A Security Essential for Cyber Defense
- Evolution of AMBA AXI Protocol: An Introduction to the Issue L Update
- An Introduction to AMBA CHI Chip-to-Chip (C2C) Protocol