Software-Driven Hardware Verification
There is a transition going on in the system and semiconductor worlds. Some system companies are starting to do their own semiconductor design. In fact, it is notable that all the leading smartphone vendors design their own application processors, for example. At the same time, semiconductor companies have to create a large part of the software stack for each SoC since the software and silicon are intimately related. Both these trends mean that software and SoCs need to be designed in parallel. This is not the only change going on. There is more parallelism in everything from the inter-relation of thermal and power, packaging and EMIR analysis, system architecture and test strategy, and more. This highly concurrent design process is what we at Cadence call System Design Enablement or SDE.
To read the full article, click here
Related Semiconductor IP
- 1.8V/3.3V I/O library with ODIO and 5V HPD in TSMC 16nm
- 1.8V/3.3V I/O Library with ODIO and 5V HPD in TSMC 12nm
- 1.8V to 5V GPIO, 1.8V to 5V Analog in TSMC 180nm BCD
- 1.8V/3.3V GPIO Library with HDMI, Aanlog & LVDS Cells in TSMC 22nm
- Specialed 20V Analog I/O in TSMC 55nm
Related Blogs
- Execute Your Hardware Verification Campaign in the Cloud - a Verification Engineer's Perspective
- Hardware-Assisted Verification: The Real Story Behind Capacity
- Software is from Mars, hardware is from Pluto
- Differentiation Through Hardware is Not Going Away
Latest Blogs
- Cadence Unveils the Industry’s First eUSB2V2 IP Solutions
- Half of the Compute Shipped to Top Hyperscalers in 2025 will be Arm-based
- Industry's First Verification IP for Display Port Automotive Extensions (DP AE)
- IMG DXT GPU: A Game-Changer for Gaming Smartphones
- Rivos and Canonical partner to deliver scalable RISC-V solutions in Data Centers and enable an enterprise-grade Ubuntu experience across Rivos platforms