How to solve the "Too Much Semiconductor IP" problem? More IP!
June 20, 2013
When discussing system-on-chip (SoC) design with my semiconductor design and software development peers, the conversation eventually gets around to the problem of, “There’s just too much IP!” The feelings I hear border on exasperation at the problem of integrating IP on today’s large SoCs. Engineers who were once paid to write lines of Verilog or C code from scratch are now spending much of their time tying together commercial hardware IP and the associated software. Their jobs have changed, and they’ve had to acquire new skills and new tools to be successful.
Related Semiconductor IP
- NoC System IP
- Cloud-active NOC configuration tool for generating and simulating Coherent and Non-Coherent NoCs
- Tessent NoC Monitor
- Network-on-Chip (NoC) Interconnect IP
- Coherent Network-on-chip (NoC) IP
Related Blogs
- Do Foundries Have Too Much Power?
- How SerDes Became Key IP for Semiconductor Systems
- The semiconductor IP business: the Imagination overview
- World IP Day: A Time to Reflect on the Value of Semiconductor IP
Latest Blogs
- Why Choose Hard IP for Embedded FPGA in Aerospace and Defense Applications
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- Quintauris: Accelerating RISC-V Innovation for next-gen Hardware
- Say Goodbye to Limits and Hello to Freedom of Scalability in the MIPS P8700
- Why is Hard IP a Better Solution for Embedded FPGA (eFPGA) Technology?