Automotive Software Development Used to End with SOP
Back in about 2001, when I was last working for Cadence, Cadence started bringing in a lot of executives from Intel. We had merged custom IC and digital IC engineering and I was running the merged marketing groups. We had a lot of customer commitments for mixed-signal design environments, and figured the only way to deliver on them was to break the silos and make a single team, at least for a year or two. The two groups historically barely talked to each other. The biggest issue was that the two environments had different databases, and we had a third database, openAccess, that existed but was not really used in either system. We needed to get that foundation sorted out before anything good would happen, otherwise we were building a house on sand.
To read the full article, click here
Related Semiconductor IP
- MIPI SoundWire I3S Peripheral IP
- MIPI SoundWire I3S Manager IP
- eDP 2.0 Verification IP
- Gen#2 of 64-bit RISC-V core with out-of-order pipeline based complex
- LLM AI IP Core
Related Blogs
- Synopsys Expands Collaboration with Arm to Accelerate the Automotive Industry’s Transformation to Software-Defined Vehicles
- Virtual Platforms from Arm and Partners Available Now to Accelerate and Transform Automotive Development
- Synopsys Collaborates with Arm to Drive Automotive Design Excellence
- The Shift-Left Approach to Software Development
Latest Blogs
- ML-KEM explained: Quantum-safe Key Exchange for secure embedded Hardware
- Rivos Collaborates to Complete Secure Provisioning of Integrated OpenTitan Root of Trust During SoC Production
- From GPUs to Memory Pools: Why AI Needs Compute Express Link (CXL)
- Verification of UALink (UAL) and Ultra Ethernet (UEC) Protocols for Scalable HPC/AI Networks using Synopsys VIP
- Enhancing PCIe6.0 Performance: Flit Sequence Numbers and Selective NAK Explained