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
- Configurable CPU tailored precisely to your needs
- Ultra high-performance low-power ADC
- HiFi iQ DSP
- CXL 4 Verification IP
- JESD204E Controller IP
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
- The Memory Imperative for Next-Generation AI Accelerator SoCs
- Leadership in CAN XL strengthens Bosch’s position in vehicle communication
- Validating UPLI Protocol Across Topologies with Cadence UALink VIP
- Cadence Tapes Out 32GT/s UCIe IP Subsystem on Samsung 4nm Technology
- LPDDR6 vs. LPDDR5 and LPDDR5X: What’s the Difference?