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
Related Blogs
- How Network-on-Chip Architectures Are Powering the Future of Microcontroller Design
- Design specification: The cornerstone of an ASIC collaboration
- Securing RISC-V Third-Party IP: Enabling Comprehensive CWE-Based Assurance Across the Design Supply Chain
- The Silent Guardian of AI Compute - PUFrt Unifies Hardware Security and Memory Repair to Build the Trust Foundation for AI Factories
Latest Blogs
- Designing for What Comes Next in AI
- Secure boot on Efinix Titanium Ti60: Getting started with KiviBoot-Tiny
- How Long Does It Take to Port a New AI Model? Minutes Now, and Falling
- PCI Express Security and TEE Integration, Part 1 - Establishing Trust
- World Models at the Edge, in Real Time: V-JEPA 2.1 on the Quadric GPNPU