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
- Over-Voltage Lockout (OVLO) IP
- Verification IP for Universal Chiplet Interconnect Express (UCIe) up to 3.0
- UCIe-S (Gen2) Compatible PHY for Standard Package (x16) in TSMC N3P, North/South Orientation
- DSP-Based 112G SerDes
- XTAL oscillator in TSMC-7nm
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
- Building the engine behind Arm’s silicon shift
- M31 High-Speed and Long-Channel MIPI C/D-PHY Solution on TSMC N3P/N3C
- Understanding security certification and how analog IP can help
- Embedded Security explained: Secure boot for embedded systems
- World's First Standards-Compliant 112G PHY IP for Linear Optics: A Turning Point for AI Interconnects