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.
Related Semiconductor IP
- RISC-V CPU IP
- AES GCM IP Core
- High Speed Ethernet Quad 10G to 100G PCS
- High Speed Ethernet Gen-2 Quad 100G PCS IP
- High Speed Ethernet 4/2/1-Lane 100G PCS
Related Blogs
- Execute Your Hardware Verification Campaign in the Cloud - a Verification Engineer's Perspective
- Software is from Mars, hardware is from Pluto
- Differentiation Through Hardware is Not Going Away
- Opinion: Why IDEs for hardware design fail
Latest Blogs
- Why Choose Hard IP for Embedded FPGA in Aerospace and Defense Applications
- Migrating the CPU IP Development from MIPS to RISC-V Instruction Set Architecture
- Quintauris: Accelerating RISC-V Innovation for next-gen Hardware
- Say Goodbye to Limits and Hello to Freedom of Scalability in the MIPS P8700
- Why is Hard IP a Better Solution for Embedded FPGA (eFPGA) Technology?