In-house layout goes the way of home-grown EDA
I think the practical end to in-house layout may be in sight. I say this for several reasons; complexity, learning curve, peak-load labor requirements and alternative use of manpower.
Let’s take a look at each issue and see what one might conclude. I think I have it right, but who knows, maybe I’m the only one that sees the murky end to internal layout teams at most organizations.
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
- A Fast and Seamless Way to Burst to the Cloud for Peak EDA Workloads
- Unleashing the Power of Wi-Fi 7. Multi-Link Operation Configurations Demystified
- Evolution of AMBA AXI Protocol: An Introduction to the Issue L Update
- Pushing the Boundaries of Memory: What’s New with Weebit and AI
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