System-on-Chip Design for Edge Computing
Edge computing has become one of those terms that means everything and nothing. But strip away the vagueness and you'll find real engineering challenges: how do you build a single chip that runs neural networks, handles sensor fusion, manages connectivity, and does it all within a 5-15W power envelope? I've been involved in SoC architecture for edge devices, and the tradeoffs are different from anything you'd encounter in datacenter design.
The Edge SoC Constraint Triangle
Every edge SoC design starts with three constraints that fight each other: performance, power, and cost. In a datacenter, cost is measured per FLOP and you have kilowatts to burn. At the edge, your BOM target might be $15-50 for the SoC, your power budget is dictated by a battery or a small heatsink, and you still need to run a neural network that was probably designed on a 400W GPU.
The chips that succeed at the edge aren't the ones with the highest peak performance. They're the ones that handle the most common workloads at the lowest typical power, while still being able to burst briefly for demanding tasks.
Key Architectural Building Blocks
A modern edge SoC typically integrates these components:
For a related perspective, see Neuromorphic Chips Guide: Brain-Inspired Computing with Inte.
- CPU cluster: Usually ARM Cortex-A series (big.LITTLE or DynamIQ configuration). Qualcomm's QCS6490 uses a 1+3+4 arrangement — one Cortex-A78 "prime" core at up to 2.7GHz, three A78 "gold" cores, and four A55 "silver" cores for efficiency. The heterogeneous design lets you match core capability to workload demand moment by moment.
- GPU: Typically ARM Mali or Qualcomm Adreno. Not primarily for graphics at the edge, but for general-purpose compute (OpenCL/Vulkan compute shaders) and display output. Ambarella's CV72S skips a traditional GPU entirely for vision-only applications.
- NPU/DSP: This is where the AI inference happens. Qualcomm's Hexagon DSP, MediaTek's APU (AI Processing Unit), or dedicated accelerators from companies like Hailo (Hailo-8L provides 13 TOPS at under 2.5W). The NPU is usually a dataflow architecture optimized for int8/int4 convolution and attention operations.
- ISP (Image Signal Processor): For camera-based applications (surveillance, automotive, drones), dedicated ISP hardware handles debayering, noise reduction, HDR merge, and lens correction at the pixel rate. Doing this on the CPU would burn 10x the power.
- Connectivity: Wi-Fi 6E/7, Bluetooth 5.3, and sometimes cellular (4G/5G) modem integration. NXP's i.MX 95 integrates a dedicated real-time processing domain for TSN (Time-Sensitive Networking) Ethernet.
- Security subsystem: Hardware root of trust, secure boot, crypto accelerators (AES, SHA, RSA/ECC), and often a secure enclave. ARM TrustZone or a dedicated security island like the one in Google's Titan M2.
Memory Architecture for Edge
This is where edge SoCs diverge sharply from datacenter chips. You don't get 192GB of HBM3. Typical configurations:
- Low-end edge (smart cameras, sensors): 512MB-2GB LPDDR4/4X, often package-on-package (PoP) for cost and board area savings.
- Mid-range edge (robotics, automotive): 4-8GB LPDDR5, either PoP or soldered discrete packages. NVIDIA's Jetson Orin NX has 16GB LPDDR5 at 102.4 GB/s.
- High-end edge (autonomous vehicles, edge servers): 16-32GB LPDDR5X. Qualcomm's Cloud AI 100 uses 64GB LPDDR4X across 4 channels for edge inference servers.
On-chip SRAM is critical for edge NPU performance. The dataflow architecture in most edge NPUs relies on large scratchpad memories (1-16MB) to hold activation tensors and weight tiles close to the compute units. Increasing the SRAM budget directly reduces external memory accesses, which dominate power consumption. I'd argue that for a given transistor budget, spending more on SRAM and less on compute cores often gives you better performance per watt for real inference workloads.
Power Management: The Hidden Complexity
A well-designed edge SoC spends most of its time in a low-power state. The power management unit (PMU) in a modern edge SoC is itself a complex subsystem:
This connects to the ideas in Silicon Wafer Supply Chain: From Sand to 300mm Wafers.
- Voltage and frequency scaling per domain: The CPU, GPU, NPU, and ISP typically have independent voltage and clock domains. You can run the NPU at full speed while the CPU idles.
- Power gating: Entire subsystems are physically powered down when not needed. The transistor-level implementation uses header/footer switches (large PMOS/NMOS devices that disconnect a block from VDD/VSS).
- Retention modes: SRAM contents can be preserved at a reduced voltage (typically 0.5-0.6V compared to 0.75-0.9V nominal), allowing fast wake-up without reloading data from external memory.
- Dynamic voltage and frequency scaling (DVFS): The PMU continuously adjusts operating points based on workload demand, thermal sensors, and battery state.
In my experience, the power management firmware is often the most difficult software to get right in an edge SoC. The interactions between thermal throttling, DVFS, power gating, and real-time deadlines create subtle bugs that only appear under specific workload combinations.
Real Products and Their Tradeoffs
Let me walk through a few actual edge SoCs and what makes each tick:
NVIDIA Jetson Orin (2022-present): The gold standard for GPU-centric edge AI. The Orin SoC combines an Ampere GPU (2048 CUDA cores, 64 Tensor cores) with a 12-core ARM Cortex-A78AE CPU and dual NVDLA (Deep Learning Accelerator) engines. The top SKU (AGX Orin 64GB) delivers 275 TOPS INT8 at 60W. It's powerful but power-hungry compared to purpose-built inference chips. Best for applications that need GPU-class flexibility — running arbitrary CUDA workloads, not just neural nets.
We covered a related topic in CPU Microarchitecture Explained: Pipeline Stages, Branch Pre.
Qualcomm QCS8550 (2024): Derived from the Snapdragon 8 Gen 3 mobile platform, adapted for IoT and edge applications. The Hexagon NPU delivers about 48 TOPS at under 12W. Has an excellent camera ISP (Spectra), integrated Wi-Fi 7 and Bluetooth 5.4. The Android/Linux software ecosystem is better than most alternatives. Best for smart camera and vision-AI applications.
Texas Instruments TDA4VH (2023): Designed specifically for automotive ADAS and machine vision. Integrates C7x DSP cores (optimized for deep learning), ARM Cortex-A72 and R5F cores, and dedicated vision and imaging accelerators. It's not the highest TOPS number (about 32 TOPS), but TI's focus on functional safety (ASIL-B/D capable) and long-term availability (15+ year production commitment) matters enormously in automotive. Good luck getting a 15-year supply commitment from Qualcomm.
Ambarella CV72S (2024): A vision-focused SoC that uses Ambarella's CVflow architecture — a vector processor optimized for computer vision operations. Delivers impressive performance-per-watt for surveillance and drone applications. The downside is a smaller software ecosystem compared to NVIDIA or Qualcomm.
Design Methodology for Edge SoCs
If you're architecting an edge SoC, here's what I think the key decisions are, in order of importance:
- Define your workload precisely. "AI at the edge" isn't a workload. "Running YOLOv8-L at 30fps on 4 camera streams with <200ms latency" is a workload. Everything else follows from this.
- Pick your NPU/accelerator architecture based on the model types you need to run. Transformer-based models have very different compute and memory access patterns than CNNs. A chip optimized for convolution may be terrible at attention.
- Size your on-chip SRAM generously. It's the single biggest factor in inference energy efficiency.
- Design the power management architecture early, not as an afterthought. In my experience, thermal and power constraints end up determining the actual sustained performance more than the theoretical peak.
- Consider the software ecosystem carefully. Silicon is only as useful as the software that runs on it. NVIDIA's dominance at the edge is built on CUDA and TensorRT more than on hardware superiority.
Edge SoC design is honestly some of the most interesting work in semiconductors right now because it forces you to optimize everything simultaneously. There's no brute-force option when your power budget is 10 watts.