host_interface.bld

Xilinx XC4VSX35为核心的 XtremeDSP Development Kit-IV 开发板的例程

Release 10.1.01 ngdbuild K.34 (nt)
Copyright (c) 1995-2008 Xilinx, Inc.  All rights reserved.

Command Line: C:\Xilinx\10.1\ISE\bin\nt\unwrapped\ngdbuild.exe -ise
E:/download_material/virtex4_board/XTremeDSP_developmentIV/Examples/host_interfa
ce_basic/ise/host_interface/host_interface.ise -intstyle ise -dd _ngo -nt
timestamp -i -p xc4vsx35-ff668-10 host_interface.ngc host_interface.ngd

Reading NGO file
"E:/download_material/virtex4_board/XTremeDSP_developmentIV/Examples/host_interf
ace_basic/ise/host_interface/host_interface.ngc" ...
Reading in constraint information from
'E:/host_interface_basic/source/host_interface_xdsp4VSX35FF668.ucf'...
Gathering constraint information from source properties...
Done.

Resolving constraint associations...
Checking Constraint Associations...
Done...
Checking Partitions ...

Checking expanded design ...
ERROR:NgdBuild:604 - logical block 'H1_IFACE/H2_DMA_CTRL/H1_INFIFO/UTHERAM' with
   type 'rm16x32d' could not be resolved. A pin name misspelling can cause this,
   a missing edif or ngc file, or the misspelling of a type name. Symbol
   'rm16x32d' is not supported in target 'virtex4'.
ERROR:NgdBuild:604 - logical block 'H1_IFACE/H2_DMA_CTRL/H2_OUTFIFO/UTHERAM'
   with type 'rm16x32d' could not be resolved. A pin name misspelling can cause
   this, a missing edif or ngc file, or the misspelling of a type name. Symbol
   'rm16x32d' is not supported in target 'virtex4'.
ERROR:NgdBuild:604 - logical block 'H2_FIFO/BRAM' with type 'rm32x512_v4tgt'
   could not be resolved. A pin name misspelling can cause this, a missing edif
   or ngc file, or the misspelling of a type name. Symbol 'rm32x512_v4tgt' is
   not supported in target 'virtex4'.

Partition Implementation Status
-------------------------------

  No Partitions were found in this design.

-------------------------------

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

Total memory usage is 94300 kilobytes


One or more errors were found during NGDBUILD.  No NGD file will be written.

Writing NGDBUILD log file "host_interface.bld"...