PE1-5.4 Signal Processing Devices & Architectures

What this is and why it exists

Something has to run the signal processing. There are five broad answers, and this topic is one long comparison between them.

Read it as a spectrum rather than a list. At one end is fully flexible and inefficient. At the other is fully efficient and rigid. Everything else sits between.

The vocabulary

• General purpose processor — an ordinary processor, running ordinary software.
• Digital signal processor — a processor shaped around the multiply-accumulate inner loop.
• FPGA — a field programmable gate array. Logic that is configured rather than programmed.
• Many-core processor — a device with a large number of simple cores on one chip.
• ASIC — an application-specific integrated circuit. Fixed hardware for one job.
• Throughput — how much data a device can process per second.
• Non-recurring engineering cost — the one-off cost of designing a device, before any are made.
• Amortisation — spreading that one-off cost across the units produced.
• Hybrid solution — a system putting each function on whichever fabric suits it.

The mental model

Place the five on the spectrum and each one's properties follow.

A general purpose processor is the most flexible thing available. Any algorithm, changed at any time, in a familiar language. It is also the least efficient, because a great deal of its silicon and its energy goes on being general. It is the baseline the others are measured against.

A digital signal processor is a processor bent towards one inner loop: multiply, accumulate, fetch the next sample. It keeps the software model and gains a large factor in efficiency on the work this field actually does. It is the same class of device as in the signal processing subject, seen here in a system role.

An FPGA is not a processor at all. It is a sea of logic elements and connections that you configure into the circuit you want. That gives hardware efficiency with the ability to change it afterwards, which is why this device made the field practical. Its cost is a different design flow, longer development, and higher power than fixed hardware.

A many-core processor offers a large number of simple cores. It trades a familiar programming model for parallelism, which suits work that divides cleanly and punishes work that does not. Specific products in this category come and go, and the category is worth knowing even when a particular product does not survive.

An ASIC is fixed hardware built for one job. It is the most efficient in both power and area, and it cannot be changed at all. It is, in a sense, the thing this whole field exists to avoid, which is exactly why it is here for contrast.

Now the part that decides real designs, and it is not performance. It is volume.

Designing an ASIC costs a great deal before a single unit exists. That one-off cost is divided across everything you make. Over a hundred million handsets it disappears into the noise. Over a few thousand base stations it dominates. So handsets tend towards fixed hardware and base stations towards configurable logic. The reason is arithmetic about quantity, not a judgement about which technology is better.

The second deciding factor is how much the design might still have to change. A standard still being revised argues for something reconfigurable, whatever the volume says.

Hybrid solutions are the honest answer in practice. Put the fixed, high-rate front-end work on hardware, the flexible control on a processor, and the parts in between wherever they fit. The interesting engineering question stops being which device is best and becomes which function belongs where.

What you should now be able to explain or do

Place all five options on the flexibility against efficiency spectrum. Say what a digital signal processor gains over a general purpose one, and at what cost in generality. Explain what an FPGA configures rather than executes. Explain why volume, not performance, usually decides between configurable logic and fixed hardware. Reconstruct the comparison table from each device's properties.

Check yourself