freque_map.map

本实例是学习fpga的入门程序 希望大家喜欢

Release 9.1i Map J.30
Xilinx Map Application Log File for Design 'freque'

Design Information
------------------
Command Line   : D:\Xilinx9.1\bin\nt\map.exe -ise
E:/fpgaproject/frequence/frequence.ise -intstyle ise -p xc3s400-pq208-4 -cm area
-pr b -k 4 -c 100 -o freque_map.ncd freque.ngd freque.pcf 
Target Device  : xc3s400
Target Package : pq208
Target Speed   : -4
Mapper Version : spartan3 -- $Revision: 1.36 $
Mapped Date    : Tue May 05 19:51:03 2009

Mapping design into LUTs...
Running directed packing...
Running delay-based LUT packing...
Running related packing...

Design Summary
--------------

Design Summary:
Number of errors:      0
Number of warnings:    1
Logic Utilization:
  Total Number Slice Registers:        96 out of   7,168    1%
    Number used as Flip Flops:                    76
    Number used as Latches:                       20
  Number of 4 input LUTs:              77 out of   7,168    1%
Logic Distribution:
  Number of occupied Slices:                           75 out of   3,584    2%
    Number of Slices containing only related logic:      75 out of      75  100%
    Number of Slices containing unrelated logic:          0 out of      75    0%
      *See NOTES below for an explanation of the effects of unrelated logic
Total Number of 4 input LUTs:            100 out of   7,168    1%
  Number used as logic:                 77
  Number used as a route-thru:          23
  Number of bonded IOBs:                5 out of     141    3%
    IOB Flip Flops:                     2
  Number of GCLKs:                     3 out of       8   37%
  Number of DCMs:                      1 out of       4   25%

Total equivalent gate count for design:  8,522
Additional JTAG gate count for IOBs:  240
Peak Memory Usage:  156 MB
Total REAL time to MAP completion:  3 secs 
Total CPU time to MAP completion:   3 secs 

NOTES:

   Related logic is defined as being logic that shares connectivity - e.g. two
   LUTs are "related" if they share common inputs.  When assembling slices,
   Map gives priority to combine logic that is related.  Doing so results in
   the best timing performance.

   Unrelated logic shares no connectivity.  Map will only begin packing
   unrelated logic into a slice once 99% of the slices are occupied through
   related logic packing.

   Note that once logic distribution reaches the 99% level through related
   logic packing, this does not mean the device is completely utilized.
   Unrelated logic packing will then begin, continuing until all usable LUTs
   and FFs are occupied.  Depending on your timing budget, increased levels of
   unrelated logic packing may adversely affect the overall timing performance
   of your design.

Mapping completed.
See MAP report file "freque_map.mrp" for details.