Earlier quoted context omitted.
I've been thinking of something similar recently - to extend your idea slightly, why couldn't the flashing of the FPGA happen per tick? Thus at every tick your FPGA could become entirely different hardware, tailored to whatever task is required at that tick.
Well, flashing is pretty slow compared to modern computers. You have to load it from flash (no pun) memory and Altera are the only ones (AFAIK) that support only changing subsections. (Which could be great because you can change only a half or quarter of your FPGA with new logic units while the others keep running.) Also, you'd have to know what you'd need... before you need it. Which is kind of impossible. By time y…
Intel Gears Up for FPGA Push
111–112 of 112 posts
Re: Intel Gears Up for FPGA Push
#112Earlier quoted context omitted.
You can always use third-party EDA tools if you have the money rather than the vendor bundled free software. Eg Cadence, Mentor Graphics, etc.
Don't you need the vendor-specific backend for the physical P&R?
Most complaints about vendor software are closer to the front of the flow. Examples...
* Poor language support (applies for both SystemVerilog and VHDL)
* Not enough transparency and access to primitives and IP blocks, resulting in poor ability to automate
* Generally buggy elaboration and synthesis results, sometimes even causing the tool to crash
My opinion is that the FPGA companies spend too much money improving the HLS (c-to-gates) and IP wizard experience, in an attempt to make their devices more accessible to the mythical software engineer who wants to use an FPGA.
They should have spent that time and money supporting language standards, and improving the RTL experience, which is how most engineers use their products.