(As always, direct to RTFM as necessary, but please cite.)

Assuming the question "why use FPGA instead of MCU?" has already been 
answered (algorithm exists on MCU but is too slow, wish to leverage 
existing IP cores such as those from opencores.org, desire to join an IP 
core development effort, etc.), getting one's feet wet with FPGA 
development still seems quite a bit more non-trivial than with MCU 
development.  However, the two have enough superficial similarity that 
one might guess there are some parallels.

- Can I assume that the components of an FPGA setup are no more than 
synthesis software (VHDL or Verilog), a sort of hardware programmer (or 
analogue thereof--what would it be called?), and a 
breakout/demonstration board with an in-circuit programming header?

- Any recommendations on which of the above would be the cheapest with 
which to start out?  For a given product, assuming nothing except the 
equipment already necessary to work with PICs and other simple 
circuitry, what would be a minimal BOM for getting anything coherent out 
of the FPGA?

- Is there a significant presence of FOSS and/or Linux-compatible 
synthesis and burning software?

I keep trying to find answers for the practical side of FPGA but all I 
can seem to locate is information on the theory...some legit answers 
would be great. :-)

Thanks
dro
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist