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
- NFC wireless interface supporting ISO14443 A and B with EEPROM on SMIC 180nm
- DDR5 MRDIMM PHY and Controller
- RVA23, Multi-cluster, Hypervisor and Android
- HBM4E PHY and controller
- LZ4/Snappy Data Compressor
Related Blogs
- ICCAD Keynote: Design of Secure Systems - Where are the EDA Tools?
- Design IP Growth Is Fueling 94% of EDA Expansion
- 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
Latest Blogs
- lowRISC Tackles Post-Quantum Cryptography Challenges through Research Collaborations
- How to Solve the Size, Weight, Power and Cooling Challenge in Radar & Radio Frequency Modulation Classification
- Programmable Hardware Delivers 10,000X Improvement in Verification Speed over Software for Forward Error Correction
- The Integrated Design Challenge: Developing Chip, Software, and System in Unison
- Introducing Mi-V RV32 v4.0 Soft Processor: Enhanced RISC-V Power