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
- nQrux® Root of Trust IP
- AXI to UCIe Bridge IP
- UCIe 2.x Controller IP
- SWI3S (SoundWire I3S Interface) Peripheral Controller Core IP
- OpenTitan-based RISC-V Secure Element
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
- The FCC Is Modernizing UWB Rules. Why It Matters for the Next Wave of Innovation
Latest Blogs
- From Bug Hunting to Engineering Methodology: Lessons from AI-Driven Development
- Manufacturing Intelligence: Turning EDA Data into Trusted Action
- Execute-in-Place: Getting More from Embedded NVM
- Rethinking RTL flows with AI-driven hybrid formal verification
- Arm and NVIDIA: Building the trusted compute foundation for the agentic AI era