3 ms·
FPGA's are cool and all, but the window of applications where FPGA's are the best tool for the job is getting narrower and narrower. For compute heavy applicat
by londons_explore 8y ago
FPGA's are cool and all, but the window of applications where FPGA's are the best tool for the job is getting narrower and narrower.
For compute heavy applications, GPU's usually offer more performance per watt and performance per $, especially if your application requires lots of add/subtract/multiply/floating point operations.
For large scale designs, low end ASIC's are surprisingly cheap (Starting from $10k), and by far beat an FPGA on perf per watt, and per $ with enough volume.
"I have a big state machine I need to run" is usually misleading. Usually your state machine isn't big enough to require an FPGA, and just converting it to a bunch of switch statements on a microcontroller will do the job just fine.
Microcontrollers usually get close to FPGA's on the "super accurate timing" front too - there are lots that can bit bang things into the hundreds of Mhz range with fancy serialization hardware.
- twtw 8y agoI agree completely, but I would like to point out that FPGAs are fantastic educational tools. Being able to get your hardware design into actual hardware for < $100 is amazing, even though the performance isn't the greatest.
- pseudosudoer 8y agoWhat you're missing is the fundamental reason industry uses FPGA's, flexibility and parallelism. An ASIC will always outpeform an FPGA in some specialized front, but the development time and cost associated with an ASIC is signifantly longer and more expensive respectively. An FPGA can be plopped into your design, and use cases can be added without refabbing the entire PCB. Good luck doing that with an ASIC... A microcontroller is more flexible than a FPGA, but it lacks the ability to parallelize (as many) tasks as an FPGA. Hardware interrupts on a uC are definitely not free and can impact performance from the overhead associated with processing the interrupt, where an FPGA can process any interrupt for "free" without impacting the performance of any parallel module. Real time apps can be implemented on uC's and DSP's, but may not be able to meet them depending on the time constraints on your system. FPGA's and GPU's were never meant to compete. GPU's will destroy an FPGA on any parallel data processing task, but that data needs to first be populated onto the GPU. A GPU's bottleneck is (usually) never it's processing speed, but it's data population (RAM) bandwidth. A GPU will never have direct access to hardware, where as an FPGA does. The overall speed of a GPU exceeds that of an FPGA for specialized parallel processing, but the latency of a GPU is larger. The point is that FPGA's are specialized, and so are other co-processors/hardware. They should be used only when it makes sense to use them, and more ad-hoc or flexible solutions are not viable.
- st26 8y agoA good example of their application is low end oscilloscopes. The heart of the machine is an FPGA running the sampling, DSP, and all the channels. It's very parallel, does a good amount of compute, and also provides lots of arbitrary IO. It's too expensive to spin an ASIC for such a low volume product. A serial processor is orders of magnitude too slow. Not familiar enough with DSP to know why not DSP, possibly too specialized.