EDA and Systems Design Converge...Or Do They?
For decades systems designers and IC designers have taken different paths. The former have relied primarily on block-level schematics for hardware definition. Except for teams facile in FPGAs, they have treated the chips in their designs as frozen blocks. For verification they have trusted prototypes over any form of simulation.
In contrast, IC designers long ago moved to language-based hardware description—first to describe the flow of data through registers in a synchronous digital design, and later to describe the function and interconnection of blocks at behavioral level. These designers, constrained by the multi-million-dollar costs of building a prototype IC to see how it works, rely on software simulation and formal analysis as verification tools, selectively using FPGA-based prototypes to complement these approaches.
To read the full article, click here
Related Semiconductor IP
- Flexible Pixel Processor Video IP
- 1.6T/3.2T Multi-Channel MACsec Engine with TDM Interface (MACsec-IP-364)
- 100G MAC and PCS core
- xSPI + eMMC Combo PHY IP
- NavIC LDPC Decoder
Related Blogs
- ICCAD Keynote: Design of Secure Systems - Where are the EDA Tools?
- Can the Semiconductor Industry Overcome Thermal Design Challenges in Multi-Die Systems?
- AI will be increasingly important in EDA, reducing design costs and supporting engineers
- Cycuity Partners with SiFive and BAE Systems to Strengthen Microelectronics Design Supply Chain Security
Latest Blogs
- Morgan State University (MSU) Leveraging Intel 16 and the Cadence Tool Flow for Academic Chip Tapeout
- Securing the Future of Terabit Ethernet: Introducing the Rambus Multi-Channel Engine MACsec-IP-364 (+363)
- Why Weebit’s IP Licensing Model Matters
- Arasan’s xSPI/eMMC5.1 PHY: Unified Dual-Mode Physical Layer IP
- Evolution of CXL PBR Switch in the CXL Fabric