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
- SpaceWire Node IP core
- nQrux Secure Boot
- 4K/8K Multiformat IP supporting AV2 decoder
- Ultra Ethernet MAC & PCS 100G/200G/400G/800G
- Ethernet PCS 100G/200G/400G/800G/1.6T
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
- A Repeatable Framework for Hardware Security Assurance
- Inside the SiFive Performance™ P570 Gen 3: High Performance Efficiency for Next-Generation Consumer and Commercial Applications
- What the steam engine can teach us about modern chip design
- Automotive silicon in the era of AI, functional safety, and cybersecurity
- JPEG XS Officially Joins GenICam, The Machine Vision Standard Managed By EMVA