FONT SIZE : AAA
After completion, this model was run through a standard synthesis software tool, targeted at a smallish size FPGA with the following results:
Number of ports : 66
Number of nets : 1704
Number of instances : 1639
Number of references to this view : 0
Total accumulated area :
Number of BUFGP : 1
Number of Dffs or Latches : 164
Number of Function Generators : 1181
Number of IBUF : 33
Number of MUX CARRYs : 31
Number of MUXF5 : 221
Number of MUXF6 : 2
Number of OBUF : 32
Number of accumulated instances : 1701
Number of global buffers used: 1
***********************************************
Device Utilization for 2VP2fg256
***********************************************
Resource Used Avail Utilization
-----------------------------------------------
IOs 65 140 46.43%
Global Buffers 1 16 6.25%
Function Generators 1181 2816 41.94%
CLB Slices 591 1408 41.97%
Dffs or Latches 164 3236 5.07%
Block RAMs 0 12 0.00%
Block Multipliers 0 12 0.00%
-----------------------------------------------
Clock : Frequency
------------------------------------
clk : 30.0 MHz
finished : 30.0 MHz
What is clear from this report is the fact that a significant amount of resources was required to implement this multiplier on a small device. In this case, the optimization was for area and not speed, but in spite of that, the design usage was nearly 50% of the whole FPGA. Clearly, arithmetic functions are not always easy on an FPGA, certainly not in area terms, with the worst culprit being multipliers. However, we are going to investigate alternative techniques and this is really just for a comparison of resources.
As a result, care must be taken in managing designs, taking advantage of pipelining and using the available resources as effectively as possible. The downside is that the design becomes more involved, with a controller generally required, but ultimately with the possibility of higher performance than an equivalent DSP function. It is also the case that many modern FPGAs now contain dedicated DSP functions (such as multiplication) which can be targeted directly in synthesis, which means that the area issue will not occur.
Manufacturer:Xilinx
Product Categories: Portes logiques
Lifecycle:Obsolete -
RoHS:
Manufacturer:Xilinx
Product Categories: Semiconducteurs & Actifs
Lifecycle:Obsolete -
RoHS: No RoHS
Manufacturer:Xilinx
Product Categories: FPGAs (Field Programmable Gate Array)
Lifecycle:Obsolete -
RoHS:
Manufacturer:Xilinx
Product Categories:
Lifecycle:Obsolete -
RoHS: -
Manufacturer:Xilinx
Product Categories:
Lifecycle:Obsolete -
RoHS: No RoHS
Support