Divide & Conquer: Dispersed global design teams need NoC fabric IP
October 3, 2013
It’s no surprise that most corporate system-on-chip (SoC) design teams are dispersed throughout the world, with different functional teams often located in different countries and continents. For example, we have many customers whose SoC architecture is defined in the United States, but subsystems such as graphics and signal processing are designed elsewhere. Companies choose this "divide and conquer" approach in the hopes of reducing design costs without affecting time to market.
But are there hidden perils to the divide and conquer SoC design approach? And what can be done to avoid these problems?
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
- Why Modern SoC need cache-coherent NoC?
- The Arm Ecosystem: More than Just an Ecosystem, it's Oxygen for SoC Design Teams
- Design IP Sales Grew 16.7% in 2020, Best Growth Rate Ever!
- Design IP Sales Grew 19.4% in 2021, confirm 2016-2021 CAGR of 9.8%
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?