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
- NFC wireless interface supporting ISO14443 A and B with EEPROM on SMIC 180nm
- DDR5 MRDIMM PHY and Controller
- RVA23, Multi-cluster, Hypervisor and Android
- HBM4E PHY and controller
- LZ4/Snappy Data Compressor
Related Blogs
- The Arm Ecosystem: More than Just an Ecosystem, it's Oxygen for SoC Design Teams
- 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
- SOC Design Techniques that Enable Autonomous Vehicles
Latest Blogs
- lowRISC Tackles Post-Quantum Cryptography Challenges through Research Collaborations
- How to Solve the Size, Weight, Power and Cooling Challenge in Radar & Radio Frequency Modulation Classification
- Programmable Hardware Delivers 10,000X Improvement in Verification Speed over Software for Forward Error Correction
- The Integrated Design Challenge: Developing Chip, Software, and System in Unison
- Introducing Mi-V RV32 v4.0 Soft Processor: Enhanced RISC-V Power