top_map.map

串口通讯源码

Release 14.2 Map P.28xd (nt64)
Xilinx Map Application Log File for Design 'top'

Design Information
------------------
Command Line   : map -intstyle ise -p xc3s500e-fg320-4 -cm area -ir off -pr off
-c 100 -o top_map.ncd top.ngd top.pcf 
Target Device  : xc3s500e
Target Package : fg320
Target Speed   : -4
Mapper Version : spartan3e -- $Revision: 1.55 $
Mapped Date    : Mon Nov 12 21:20:43 2012

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

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

Design Summary:
Number of errors:      0
Number of warnings:    0
Logic Utilization:
  Total Number Slice Registers:         106 out of   9,312    1%
    Number used as Flip Flops:          105
    Number used as Latches:               1
  Number of 4 input LUTs:               140 out of   9,312    1%
Logic Distribution:
  Number of occupied Slices:            102 out of   4,656    2%
    Number of Slices containing only related logic:     102 out of     102 100%
    Number of Slices containing unrelated logic:          0 out of     102   0%
      *See NOTES below for an explanation of the effects of unrelated logic.
  Total Number of 4 input LUTs:         175 out of   9,312    1%
    Number used as logic:               139
    Number used as a route-thru:         35
    Number used as Shift registers:       1

  The Slice Logic Distribution report is not meaningful if the design is
  over-mapped for a non-slice resource or if Placement fails.

  Number of bonded IOBs:                 17 out of     232    7%
  Number of BUFGMUXs:                     2 out of      24    8%

Average Fanout of Non-Clock Nets:                2.82

Peak Memory Usage:  277 MB
Total REAL time to MAP completion:  6 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 "top_map.mrp" for details.