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
- AXI to UCIe FDI Interface IP
- 45SPCLO UCIe-Class 1-32Gbps Low Power Receiver IP (NRZ)
- 45SPCLO UCIe-Class 1-32Gbps Low Power Transmitter IP (NRZ)
- Peripheral Sensor Interface (PSI5) Host Controller
- Link Acceleration Unit
Related Blogs
- Execute Your Hardware Verification Campaign in the Cloud - a Verification Engineer's Perspective
- Programmable Hardware Delivers 10,000X Improvement in Verification Speed over Software for Forward Error Correction
- Importance Of Hardware Security Verification In Pre-Silicon Design
- IDS-Verify™: From Specification to Sign-Off – Automated CSR, Hardware Software Interface and CPU-Peripheral Interface Verification
Latest Blogs
- What the Cyber Resilience Act means for the future of chip design
- When Your IP Vendor Has Operated 150,000 Base Stations: Introducing Viettel Semiconductor
- Relationship between architecture and validation in system design
- The Post-Quantum Cryptography Mandate: Building Cryptographically Agile Systems for the Quantum Era
- Demystify Address Translation Services (ATS) in PCIe 6.0