FPGA Express

After we get the correct fimctionalily of our top-level ( mac tesf ) module, we must convert diese top-level design files and all generated cores to the programming file for the FPGA The first step is called design synthesis. In ECE554, we use FPGA Express as our synthesis tool. 

Start=>Programs=>Xilinx Foundation Series 3.1i=>Accessories=>FPGA Express... 

Note that the synthesis directory is created by FPGA Express to hold its project file synthesis.exp as well as our synthesized hardware (netlist file . edf ). 

Now all the design (source) files have been entered and analyzed by the FPGA Express. The check mark will appear to indicate that each file is correct according to the FPGA Express. If not, the cross mark will appear instead. The next step is to synthesize the top most ( mitring ) module. 

Fpga export netlist.jp g Minimize the FPGA Express window. 

Synopsys FPGA Express automatically generated file // This file will be overwritten by each chip export // Author kittitor // Program FPGA Express // Version 3.5.0.5831... 

This mitring, v was also generated ly FPGA Express along with die mitring, edf . 

FPGA Express=>Help=>VHDL Reference Manual... 

Add a new source file non syn.v to the current project synthesis. FPGA Express will automatically performs syntax checking. 

Delete initial Q = I bl and update the source file again. It should pass the S3mtax checking by FPGA Express. 

In addition, passing the FPGA Express syntax checker does always NOT mean that the HDL code can be synthesized correctly since problems can arise later in the synthesis process. Also, synthesis may work, but not produce useful results. For example, you have to search the output schematic carefully to see whether latches are inferred by your incomplete if or case statements. 

---