Which IP for FD-SOI Ecosystem?
We know that the best technology or product, even if it exhibits best in class and unmatched features, is almost of no use if lacking an ecosystem. If you think about a processor core, you will expect to find compatible communication bus and memories (inside the SoC) and operating system, compiler, debugger, etc. When dealing with a disruptive ASIC technology like FD-SOI, you will expect to have multiple sources for raw SOI wafers, at least double sourcing capability for processing these wafers and, last but not least, a solid IP ecosystem. If you can’t decree the creation of this IP ecosystem, you (the foundry or ASIC vendor) can certainly invest resource to internally develop the foundation IP (standard cell library or memory compiler). Your involvement in supporting or initiating the development of complexes IP by the best in class IP vendors will make the difference too.
To read the full article, click here
Related Semiconductor IP
- nQrux® Root of Trust IP
- AXI to UCIe Bridge IP
- UCIe 2.x Controller IP
- SWI3S (SoundWire I3S Interface) Peripheral Controller Core IP
- OpenTitan-based RISC-V Secure Element
Related Blogs
- FinFET vs FDSOI - Which is the Right One for Your Design?
- From "What-If" to "What-Is": Cadence IP Validation for Silicon Platform Success
- Efficient IP Packaging for Today’s SoC Integration
- The Next-Generation UCIe IP Subsystem for Advanced Package Designs
Latest Blogs
- From Bug Hunting to Engineering Methodology: Lessons from AI-Driven Development
- Manufacturing Intelligence: Turning EDA Data into Trusted Action
- Execute-in-Place: Getting More from Embedded NVM
- Rethinking RTL flows with AI-driven hybrid formal verification
- Arm and NVIDIA: Building the trusted compute foundation for the agentic AI era