Doing some work with HDL in a university research setting is different than shipping a working product with the associated constraints.
3,708 karma · joined September 28, 2008
Doing some work with HDL in a university research setting is different than shipping a working product with the associated constraints.
Optimization is important in hardware due to cost, speed, and power implications of hardware design. These tradeoffs are there for software design as well, but to a much less extent.
Debugging HDL involves looking at timing waveforms in a simulator.
A lot of the trouble with FPGA development in my opinion isn't the HDL, but the toolchains themselves. I haven't met anyone that likes FPGA toolchains. Things like PLL instantiation problems are likely to do with the tool and not the language.
A lot of people (I'm not saying this is you) coming from a software background tend to approach FPGAs as if it were a software problem. They seem very similar, after all. You write some code into a window, hit a button, and bam, you have some functionality. To some extent, I think it leads them to tend to shove a square peg in a round hole. Just like there are programming paradigms governing software design, there paradigms governing FPGA design as well. Trying to force certain abstractions can lead to headache.
Abstractions are very important in any design process, be it analog hardware, digital hardware, software, bridge design, etc. Software tends to favor abstractions because they are powerful, but also very cheap. One can afford to waste some CPU cycles if it reduces development time and the occurrence of bugs. In FPGA and ASIC design, abstractions are just as important but one can't afford to waste clock speed or chip area to get it. FPGAs are expensive and ASICs even more so. The design paradigms of HDL exist for that reason, as frustrating as they may be.
In a sense, I've just grown accustomed to Verilog's warts. I was appalled at the FPGA development process when I first started but at this point I just take it for granted. I think thing will get better but it will take time. Even so, I think that it is best to stick with Verilog/VHDL for the time being. Just like if one wanted to web development, one would have to learn javascript, which is also considered terrible.
I would think that the toolchains would be the biggest complaint.
If one wanted to do web development, javascript knowledge is important. It is the same with FPGAs and HDL.
I think your InstaPart feature looks cool. Lots of big companies have CAD teams that just make component libraries for designers. It is nice to get a bit of that on the small side of the industry finally.
That being said, limiting it to 5/month is very constraining. Can you accrue InstaParts? I think most designers typically need more than that per project, but not necessarily each month.
The problem with open toolchains from the manufacturer's point of view is that they have nothing to gain and everything to lose. They don't want to sell chips one at a time to hobbyists. They want to sell them millions at the time to GM and other companies. In their mind, open toolchains buy them nothing but leave them open to competitors stealing their designs. I'm not saying this view is accurate, it is just how chip vendors think.