__projnav.log

用于FPGA向DSP传送数据的接口

Applying constraints in "fd_constraints.ucf" to the design...

Checking timing specifications ...
Checking expanded design ...

NGDBUILD Design Results Summary:
  Number of errors:     0
  Number of warnings:   0

Writing NGD file "fpgatodsp.ngd" ...

Writing NGDBUILD log file "fpgatodsp.bld"...

NGDBUILD done.




Started process "Map".

Using target part "4vsx35ff668-12".
Mapping design into LUTs...
Running directed packing...
Running delay-based LUT packing...
Running related packing...

Design Summary:
Number of errors:      0
Number of warnings:   21
Logic Utilization:
  Number of Slice Flip Flops:          12 out of  30,720    1%
  Number of 4 input LUTs:              28 out of  30,720    1%
Logic Distribution:
  Number of occupied Slices:                           22 out of  15,360    1%
    Number of Slices containing only related logic:      22 out of      22  100%
    Number of Slices containing unrelated logic:          0 out of      22    0%
      *See NOTES below for an explanation of the effects of unrelated logic
Total Number 4 input LUTs:             34 out of  30,720    1%
  Number used as logic:                 28
  Number used as a route-thru:           6
  Number of bonded IOBs:               57 out of     448   12%
  Number of BUFG/BUFGCTRLs:             2 out of      32    6%
    Number used as BUFGs:                2
    Number used as BUFGCTRLs:            0

Total equivalent gate count for design:  564
Additional JTAG gate count for IOBs:  2,736
Peak Memory Usage:  202 MB

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 "fpgatodsp_map.mrp" for details.




Started process "Place & Route".




Constraints file: fpgatodsp.pcf.
Loading device for application Rf_Device from file '4vsx35.nph' in environment
D:/xilinx.
   "fpgatodsp" is an NCD, version 3.1, device xc4vsx35, package ff668, speed -12
This design is using the default stepping level (major silicon revision) for
this device (1). Unless your design is targeted at devices of this stepping
level, it is recommended that you explicitly specify the stepping level of the
parts you will be using. This will allow the tools to take advantage of any
available performance and functional enhancements for this device. The latest
stepping level for this device is '2'. Additional information on "stepping
level" is available at support.xilinx.com.

Initializing temperature to 85.000 Celsius. (default - Range: 0.000 to 85.000
Celsius)
Initializing voltage to 1.200 Volts. (default - Range: 1.140 to 1.260 Volts)


Device speed data version:  "PREVIEW 1.57 2005-08-24".


Device Utilization Summary:

   Number of BUFGs                     2 out of 32      6%
   Number of ILOGICs                   2 out of 448     1%
   Number of External IOBs            57 out of 448    12%
      Number of LOCed IOBs            57 out of 57    100%

   Number of OLOGICs                  28 out of 448     6%
   Number of Slices                   22 out of 15360   1%
      Number of SLICEMs                0 out of 7680    0%



Overall effort level (-ol):   Standard (set by user)
Placer effort level (-pl):    Standard (set by user)
Placer cost table entry (-t): 1
Router effort level (-rl):    Standard (set by user)

WARNING:Par:276 - The signal addr<14>_IBUF has no load
WARNING:Par:276 - The signal addr<15>_IBUF has no load
WARNING:Par:276 - The signal addr<16>_IBUF has no load
WARNING:Par:276 - The signal addr<17>_IBUF has no load
WARNING:Par:276 - The signal addr<18>_IBUF has no load
WARNING:Par:276 - The signal addr<19>_IBUF has no load
WARNING:Par:276 - The signal addr<1>_IBUF has no load
WARNING:Par:276 - The signal addr<2>_IBUF has no load
WARNING:Par:276 - The signal addr<3>_IBUF has no load
WARNING:Par:276 - The signal addr<5>_IBUF has no load
WARNING:Par:276 - The signal addr<6>_IBUF has no load
WARNING:Par:276 - The signal addr<7>_IBUF has no load
WARNING:Par:276 - The signal addr<9>_IBUF has no load
WARNING:Par:276 - The signal addr<10>_IBUF has no load
WARNING:Par:276 - The signal addr<11>_IBUF has no load
WARNING:Par:276 - The signal addr<12>_IBUF has no load
WARNING:Par:276 - The signal addr<13>_IBUF has no load

Starting Placer

Phase 1.1
Phase 1.1 (Checksum:9898cb) REAL time: 4 secs 

Phase 2.31
Phase 2.31 (Checksum:1312cfe) REAL time: 4 secs 

Phase 3.2
......
WARNING:Place:644 - A clock IOB  clock component is not placed at an optimal
   clock IOB site  The clock IOB component <nrd> is placed at site IOB_X0Y131.
   The clock IO site can use the fast path between the IO and the Clock
   buffer/GCLK if the IOB is placed in the master Clock IOB Site. This is
   normally an ERROR but the environment variable
   XIL_PLACE_ALLOW_LOCAL_BUFG_ROUTING is set allowing your design to continue.
WARNING:Place:644 - A clock IOB  clock component is not placed at an optimal
   clock IOB site  The clock IOB component <CLK> is placed at site IOB_X1Y58.
   The clock IO site can use the fast path between the IO and the Clock
   buffer/GCLK if the IOB is placed in the master Clock IOB Site. This is
   normally an ERROR but the environment variable
   XIL_PLACE_ALLOW_LOCAL_BUFG_ROUTING is set allowing your design to continue.


Phase 3.2 (Checksum:98a237) REAL time: 5 secs 

Phase 4.30
Phase 4.30 (Checksum:26259fc) REAL time: 5 secs 

Phase 5.3
Phase 5.3 (Checksum:2faf07b) REAL time: 5 secs 

Phase 6.5
Phase 6.5 (Checksum:39386fa) REAL time: 5 secs 

Phase 7.8
.
Phase 7.8 (Checksum:9bf9fa) REAL time: 5 secs 

Phase 8.5
Phase 8.5 (Checksum:4c4b3f8) REAL time: 5 secs 

Phase 9.18
Phase 9.18 (Checksum:55d4a77) REAL time: 5 secs 

Phase 10.27
Phase 10.27 (Checksum:5f5e0f6) REAL time: 5 secs 

Phase 11.5
Phase 11.5 (Checksum:68e7775) REAL time: 5 secs 

Writing design to file fpgatodsp.ncd


Total REAL time to Placer completion: 5 secs 
Total CPU time to Placer completion: 5 secs 

Starting Router

Phase 1: 269 unrouted;       REAL time: 6 secs 

Phase 2: 197 unrouted;       REAL time: 7 secs 

Phase 3: 36 unrouted;       REAL time: 7 secs 

Phase 4: 0 unrouted;       REAL time: 7 secs 

Total REAL time to Router completion: 7 secs 
Total CPU time to Router completion: 7 secs 

Generating "PAR" statistics.

**************************
Generating Clock Report
**************************

+---------------------+--------------+------+------+------------+-------------+
|        Clock Net    |   Resource   |Locked|Fanout|Net Skew(ns)|Max Delay(ns)|
+---------------------+--------------+------+------+------------+-------------+
|           nrd_BUFGP |BUFGCTRL_X0Y16| No   |   30 |  0.321     |  2.361      |
+---------------------+--------------+------+------+------------+-------------+
|           CLK_BUFGP | BUFGCTRL_X0Y1| No   |    7 |  0.008     |  1.999      |
+---------------------+--------------+------+------+------------+-------------+

Generating Pad Report.

All signals are completely routed.

Total REAL time to PAR completion: 9 secs 
Total CPU time to PAR completion: 9 secs 

Peak Memory Usage:  176 MB

Placement: Completed - No errors found.
Routing: Completed - No errors found.

Number of error messages: 0
Number of warning messages: 19
Number of info messages: 1

Writing design to file fpgatodsp.ncd



PAR done!

Started process "Generate Post-Place & Route Static Timing".

Loading device for application Rf_Device from file '4vsx35.nph' in environment
D:/xilinx.
   "fpgatodsp" is an NCD, version 3.1, device xc4vsx35, package ff668, speed -12
This design is using the default stepping level (major silicon revision) for
this device (1). Unless your design is targeted at devices of this stepping
level, it is recommended that you explicitly specify the stepping level of the
parts you will be using. This will allow the tools to take advantage of any
available performance and functional enhancements for this device. The latest
stepping level for this device is '2'. Additional information on "stepping
level" is available at support.xilinx.com.

Analysis completed Tue Aug 14 22:44:45 2007
--------------------------------------------------------------------------------

Generating Report ...

Number of warnings: 0
Total time: 5 secs 







Started process "Generate Programming File".

WARNING:PhysDesignRules:367 - The signal <addr<14>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<15>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<16>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<17>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<18>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<19>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<1>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<2>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<3>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<5>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<6>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<7>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<9>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<10>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<11>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<12>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.
WARNING:PhysDesignRules:367 - The signal <addr<13>_IBUF> is incomplete. The
   signal does not drive any load pins in the design.


Project Navigator Auto-Make Log File
-------------------------------------










Started process "Synthesize".


=========================================================================
*                          HDL Compilation                              *
=========================================================================
Compiling verilog file "fpgatodsp.v"
ERROR:HDLCompilers:26 - "fpgatodsp.v" line 78 unexpected token: 'end'
ERROR:HDLCompilers:26 - "fpgatodsp.v" line 81 expecting ';', found 'EOF'
ERROR:HDLCompilers:26 - "fpgatodsp.v" line 81 expecting 'end', found 'EOF'
ERROR:HDLCompilers:26 - "fpgatodsp.v" line 81 unexpected token: 'EOF'
ERROR:HDLCompilers:26 - "fpgatodsp.v" line 81 expecting 'end', found 'EOF'
Module <fpgatodsp> compiled
ERROR:HDLCompilers:26 - "fpgatodsp.v" line 81 expecting 'endmodule', found 'EOF'
Analysis of file <"fpgatodsp.prj"> failed.
--> 

Total memory usage is 77196 kilobytes

Number of errors   :    6 (   0 filtered)
Number of warnings :    0 (   0 filtered)