Build or Buy? The Design Rules Remain the Same
The last time I visited the "build or buy" issue, a lot of small commercial engineering outfits were looking to the big companies for in-house support for their various products for the burgeoning wireless market.
With the technology and complexity of self-contained RF systems having advanced much in the past 15 years, I'm sure the major IC companies and module makers still get involved with the little guy but the details are usually sparse due to the nature of today's non-disclosure agreements. On the other hand, build-versus-buy is largely the same issue at university labs and applied-research houses, where performance isn't necessarily measured in commercial terms and where meeting tight timetables and cost budgets aren't always the biggest driving factors.
So what are the general design rules? I reckon they're largely unknown to the current crop of today's young engineers, but they are relatively simple and unchanged, albeit counter-intuitive.
To read the full article, click here
Related Semiconductor IP
- MIL-STD-1553 Controller IP
- UFS 5.x Device IP
- UCIe 3.x Controller IP
- Ethernet 800G PCS IP
- CHI to UCIe Bridge IP
Related Blogs
- The Hidden Threat in Analog IC Migration: Why Electromigration rules can make or break your next tapeout
- Building Smarter, Faster: How Arm Compute Subsystems Accelerate the Future of Chip Design
- The Integrated Design Challenge: Developing Chip, Software, and System in Unison
- Analog Design and Layout Migration automation in the AI era
Latest Blogs
- CDM Dependence on Device Capacitance
- What the Cyber Resilience Act means for the future of chip design
- When Your IP Vendor Has Operated 150,000 Base Stations: Introducing Viettel Semiconductor
- Relationship between architecture and validation in system design
- The Post-Quantum Cryptography Mandate: Building Cryptographically Agile Systems for the Quantum Era