1. Learn verilog. Its much easier and is the standard language in the US. VHDL is strongly typed like Ada (VHDL is Ada with hardware constructs added.) If you're in Europe, then learn VHDL because its more of the hardware language standard over there.
Having coded in both (military stuff use to use Ada and VHDL), I would say that strongly typed to the level that VHDL is is an overrated feature for hardware design. When VHDL and Verilog first came out, VHDL had a bunch of features that they supported that Verilog did not, so it became a standard for some. But with the release of verilog AMS and systemverilog, they're both pretty much have the same capability. ANd now the only reason people choose one language over the other is because of their existing code base or because some third party IP uses one or the other. 2. You can get the PICOZED version of the zedboard for $178 which uses the smaller xilinx ZYNQ chip. XIlinx makes their synthesis software tool available for free for their smaller chips, including the Zedboard and picozed. The tool supports verilog. ANd it may even support VHDL if you must inflict that language on youself. On Sat, May 6, 2017 3:08 pm, Prez Cannady wrote: > > 1. To learn VHDL. > 2. To prototype hardware impls if you don't have test rigs of your own. > > > Sent from my iPhone > > >> On May 6, 2017, at 12:08 AM, Greg London <[email protected]> wrote: >> >> >> >> Why would you curse someone with the pain and suffering of VHDL? >> >> >> Does Amazon's service come with High Level Synthesis tools? >> You could write your algorithm in c and then run it as software >> and run it in an fpga and do a side by side comparison to see which is >> faster. >> >> >> >> >> >> _______________________________________________ >> Hardwarehacking mailing list >> [email protected] >> http://lists.blu.org/mailman/listinfo/hardwarehacking >> > -- _______________________________________________ Hardwarehacking mailing list [email protected] http://lists.blu.org/mailman/listinfo/hardwarehacking
