Why Is It Always "Someone Else's Problem"?
Anyone who's worked in chip industry will have listened to the hardware guys blaming a software problem, only to cross the room and find that the software guys are convinced that "the problem's in the hardware."
We’re always hearing that innovation is a team sport. Nowhere is this more the case than in today’s semiconductor industry. Different teams and skill sets are required to architect the system, generate the RTL, perform place and route, implement the physical design, verify and debug both the logical and physical design and generate the software that runs on a typical core-based SoC.
You might think that in this environment, people would be used to taking collective responsibility for taping out a chip on time and to budget…
To read the full article, click here
Related Semiconductor IP
- Flexible Pixel Processor Video IP
- Complex Digital Up Converter
- Bluetooth Low Energy 6.0 Digital IP
- Verification IP for Ultra Ethernet (UEC)
- MIPI SWI3S Manager Core IP
Related Blogs
- What is cloud-based security lifecycle management for connected objects and why is it important?
- What is AI Anomaly Detection and Why it needs Explainable AI (XAI)?
- Breaking the Silence: What Is SoundWire‑I3S and Why It Matters
- GloFo's 12nm FD-SOI: why it makes headlines in China
Latest Blogs
- CNNs and Transformers: Decoding the Titans of AI
- How is RISC-V’s open and customizable design changing embedded systems?
- Imagination GPUs now support Vulkan 1.4 and Android 16
- From "What-If" to "What-Is": Cadence IP Validation for Silicon Platform Success
- Accelerating RTL Design with Agentic AI: A Multi-Agent LLM-Driven Approach