FPGA, Microcontroller or ASIC: When Programmable Logic Makes Sense
A microcontroller runs instructions one after another. An FPGA is a fabric of logic blocks, memories and arithmetic units that can be wired into whatever circuit the design describes, all running at once. An ASIC fixes that circuit permanently in silicon. Each suits a different combination of performance, volume and flexibility, and choosing the wrong one is expensive in either direction. This article sets out where each fits.
At a glance
- Parallel
- FPGA logic processes many data streams at the same time, each with fixed timing.
- LUT
- Look-up table: the basic programmable logic element in most FPGA fabrics.
- Reconfig
- An FPGA can be reprogrammed in the field to change the hardware itself.
- NRE
- Non-recurring engineering cost, the large up-front expense that makes an ASIC a volume decision.
The problem
Teams reach for an FPGA when a microcontroller seems too slow, and sometimes the real fix was a faster processor, a DMA controller or a dedicated peripheral. The FPGA brings its own costs: a higher unit price than most microcontrollers, several power rails, configuration memory and specialist design skills.
The opposite mistake is forcing a processor to do work that is naturally parallel, such as high-rate sensor interfaces or deterministic signal processing, and ending up with firmware that struggles to meet timing under load.
Choose an FPGA for what must happen in parallel with fixed timing. For everything else, software is usually cheaper.
Where programmable logic wins
FPGAs suit high-speed, parallel or timing-critical work: interfacing many ADC channels, processing video or radio samples in a pipeline, implementing custom interfaces, and producing outputs with nanosecond-level determinism. They also let hardware be updated after shipping, which matters while standards or algorithms are still changing.
Many products combine both. An FPGA handles the data path while a processor runs the control software, either as separate chips or in a system-on-chip device that puts processor cores and FPGA fabric in one package, such as the AMD Zynq family.
What good looks like
Write down the throughput, latency and determinism the product needs, and check whether a microcontroller with suitable peripherals or DMA can meet them.
If not, estimate the FPGA resources needed: logic, memory blocks, DSP blocks, I/O count and transceivers, with margin.
Weigh unit cost, power and development effort against expected volume; consider an ASIC only when volume and stable requirements justify the up-front cost.
| Microcontroller | FPGA | ASIC | |
|---|---|---|---|
| Execution | Sequential instructions | Parallel hardware | Parallel hardware, fixed |
| Unit cost | Low | Medium to high | Lowest at high volume |
| Up-front cost | Low | Moderate | Very high |
| Change after release | Firmware update | Bitstream update | New silicon |
| Design skills | Embedded software | HDL and timing analysis | Chip design and verification |
A decision path
- Software can do it: Microcontroller or processor
- Parallel or deterministic: Consider an FPGA
- Control plus data path: Processor and FPGA, or an SoC FPGA
- Very high, stable volume: Evaluate an ASIC
What it changes
Right Performance
Parallel work runs in hardware, sequential work in software.
Lower Total Cost
FPGA cost and effort are spent only where they buy something.
Field Flexibility
Reprogrammable logic can follow changing standards.
Clear Partitioning
Each function sits on the device best suited to it.
Where to go next
FPGA power-up needs care: several rails, often with sequencing requirements, and a configuration memory that loads the design at start-up.
Development tools and IP licensing are part of the cost. Check which toolchain features and IP cores your design needs.
Problems this prevents
- An FPGA used where a faster processor would do
- Firmware missing timing on parallel tasks
- Underestimated FPGA power and configuration needs
- An ASIC committed before requirements were stable
Discuss your project
Email support@aavico.com or use Get in Touch when the website finishes loading.