The first step: Understand the basic hardware knowledge of fpga, such as the meaning and internal structure of fpga, the types of existing fpga chips, and how to distinguish fpga chips.
Step 2: Understand the fpga hardware design language, starting with vhdl, can also start from other,
Step 3: Familiar with vhdl language compilation environment maxblusii or quartusii,
Step 4: Buy the development board (this can be bought at the beginning), it is recommended to buy a general initial on the line,
Tips for getting started:
Conceptual understanding: Engaged in fpga development, not writing code, is circuit design, digital circuit design, but unlike you in protel drawing schematic, do layout, it requires you to use the language to describe your circuit, and then according to your description to generate the corresponding circuit, the way described here reflects your technical level, please understand, Verilog or VHDL is hardwaredescriptionlaugahge.
2. Theoretical Reserve: Get your digital circuit book out and understand registers, state machines, timing equations.
3. Please read the manual of xilinx or altera fpga to understand its interface, firmware composition (pll,blockram,dcm,serdes, etc.), and resource distribution. It is recommended to open a chip layout with xilinx fpgaeidter software. You will find that the essence of fpga is a series of resources stacked, you have to do is how to use such hardware resources to make what you want.
4. Please understand combinatorial logic and temporal logic, and calculate the composition of the two kinds of logical signal delay, that is, the timing division problem.
5. Hands-on ability, write code, write more code, debug more, you encounter more problems, solve more, all the problems are not problems. Be good at summarizing.
6. Popular interface, the principle of technology to understand, such as spi,i2c,usb,ddr1\/2\/3, pcie, popular high-speed interface lvds,lvpecl,sstl and so on.
7.fpga engineers often play the role of this system engineer, please think more from the perspective of the system.
8. Good documentation habits, this is very important!