How to prevent FPGA-based projects from going astray
Adam Taylor, E2V
embedded.com (February 22, 2017)
During the course of my career, I have been involved with developing a number of FPGA designs for some really interesting projects. Sadly, I have also been involved in rescuing several FPGA designs that have gone badly astray. As I worked on these problem designs, it became apparent that -- although the target applications and the members of the development teams were different -- the designs shared some common points that doomed them to failure before the first engineer even sat down to write the first line of HDL code.
With this in mind, I thought I would run through five common issues that I've observed as part of rescuing these projects. These issues are as follows:
![]() |
E-mail This Article | ![]() |
![]() |
Printer-Friendly Page |
Related Articles
- How to Reduce FPGA Logic Cell Usage by >x5 for Floating-Point FFTs
- How to improve FPGA-based ASIC prototyping with SystemVerilog
- How to simplify power design development and evaluation for FPGA-based systems
- How to test the interconnections between FPGAs on a high-density FPGA-based board
- How to design FPGA-based advanced PCI Express endpoint solutions
New Articles
- Understanding MACsec and Its Integration
- Discover new Tessent UltraSight-V from Siemens EDA, and accelerate your RISC-V development.
- The Critical Factors of a High-performance Audio Codec - What Chip Designers Need to Know
- Density Management in Analog Layout Design: Addressing Issues and Ensuring Consistency
- Nexus: A Lightweight and Scalable Multi-Agent Framework for Complex Tasks Automation