Co-design - Myth or Reality?
Brian Bailey
EETimes (7/26/2011 10:30 AM EDT)
I think it was probably 17 years ago when I started to attend co-design conferences. At that time they were very academic in nature and they concentrated mostly on the most optimal way to automatically partition a design written in C, Java, or some other language into hardware and software.
The interfaces were always the sticky area and most of the algorithms just assumed that communications was free both in terms of performance and resources. Some of the later ones did take this into account, but not in very flexible ways. We even started to see commercial tools in the area, not just from startups, but from Cadence – with the Felix, VCC – whatever name you preferred to call it by.
But all of this research and the tools went by the wayside. I think the primary reason was they all assumed a single thread, a single function, a single processor, a single bus – and the list could go on. Now designing and partitioning between hardware and software for such a system is not really that difficult and so the tools didn’t provide enough value to warrant their adoption.
To read the full article, click here
Related Semiconductor IP
- LPDDR6/5X/5 PHY V2 - Intel 18A-P
- ML-KEM Key Encapsulation & ML-DSA Digital Signature Engine
- MIPI SoundWire I3S Peripheral IP
- ML-DSA Digital Signature Engine
- P1619 / 802.1ae (MACSec) GCM/XTS/CBC-AES Core
Related Blogs
- Subsystem IP, myth or reality?
- Dis-ARMing the data center - Separating myth from reality
- From guesswork to guidance: Mastering processor co-design with Codasip Exploration Framework
- The Hidden Threat in Analog IC Migration: Why Electromigration rules can make or break your next tapeout
Latest Blogs
- PCIe Low-Power Validation Challenges and Potential Solutions (PIPE/L1 Substates)
- Rethinking Edge AI Interconnects: Why Multi-Protocol Is the New Standard
- Tidying Up: FIPS-Compliant Secure Zeroization for OTP
- Accelerating Your Development: Simplify SoC I/O with a Single Multi-Protocol SerDes IP
- Why What Where DIFI and the new version 1.3