使用Synplify进行综合时,ISE实施阶段存在问题

时间:2018-12-09 20:15:35

标签: vhdl verilog system-verilog hdl synopsys-vcs

我的项目包含ISE项目中XPS部分的MicroBlaze,几条AXI4 Lite / Full总线。在ISE中实现一些AXI4从站。 该项目是完全综合的,并且可以与XST一起使用,但是在使用Synplify Pro进行综合时会发生以下错误:

   ERROR:NgdBuild:989 - Failed to process BMM information edkBmmFile.bmm
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/AXI3_BUS_RAMonly_RO' with
   type 'MBSystemEnvironment_axi3_bus_ramonly_ro_wrapper' could not be resolved.
   A pin name misspelling can cause this, a missing edif or ngc file, case
   mismatch between the block name and the edif or ngc file name, or the
   misspelling of a type name. Symbol
   'MBSystemEnvironment_axi3_bus_ramonly_ro_wrapper' is not supported in target
   'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/AXI3B_MASTER_RAMonly_RO'
   with type 'MBSystemEnvironment_axi3b_master_ramonly_ro_wrapper' could not be
   resolved. A pin name misspelling can cause this, a missing edif or ngc file,
   case mismatch between the block name and the edif or ngc file name, or the
   misspelling of a type name. Symbol
   'MBSystemEnvironment_axi3b_master_ramonly_ro_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/AXI1BL_SLAVE_RW' with type
   'MBSystemEnvironment_axi1bl_slave_rw_wrapper' could not be resolved. A pin
   name misspelling can cause this, a missing edif or ngc file, case mismatch
   between the block name and the edif or ngc file name, or the misspelling of a
   type name. Symbol 'MBSystemEnvironment_axi1bl_slave_rw_wrapper' is not
   supported in target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/AXI2B_MASTER_RAMonly_RW'
   with type 'MBSystemEnvironment_axi2b_master_ramonly_rw_wrapper' could not be
   resolved. A pin name misspelling can cause this, a missing edif or ngc file,
   case mismatch between the block name and the edif or ngc file name, or the
   misspelling of a type name. Symbol
   'MBSystemEnvironment_axi2b_master_ramonly_rw_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/AXI2_BUS_RAMonly_RW' with
   type 'MBSystemEnvironment_axi2_bus_ramonly_rw_wrapper' could not be resolved.
   A pin name misspelling can cause this, a missing edif or ngc file, case
   mismatch between the block name and the edif or ngc file name, or the
   misspelling of a type name. Symbol
   'MBSystemEnvironment_axi2_bus_ramonly_rw_wrapper' is not supported in target
   'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/Generic_GPIO' with type
   'MBSystemEnvironment_generic_gpio_wrapper' could not be resolved. A pin name
   misspelling can cause this, a missing edif or ngc file, case mismatch between
   the block name and the edif or ngc file name, or the misspelling of a type
   name. Symbol 'MBSystemEnvironment_generic_gpio_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/Generic_SPI' with type
   'MBSystemEnvironment_generic_spi_wrapper' could not be resolved. A pin name
   misspelling can cause this, a missing edif or ngc file, case mismatch between
   the block name and the edif or ngc file name, or the misspelling of a type
   name. Symbol 'MBSystemEnvironment_generic_spi_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/MCB_DDR3' with type
   'MBSystemEnvironment_mcb_ddr3_wrapper' could not be resolved. A pin name
   misspelling can cause this, a missing edif or ngc file, case mismatch between
   the block name and the edif or ngc file name, or the misspelling of a type
   name. Symbol 'MBSystemEnvironment_mcb_ddr3_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/RS232' with type
   'MBSystemEnvironment_rs232_wrapper' could not be resolved. A pin name
   misspelling can cause this, a missing edif or ngc file, case mismatch between
   the block name and the edif or ngc file name, or the misspelling of a type
   name. Symbol 'MBSystemEnvironment_rs232_wrapper' is not supported in target
   'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/AXI0_BUS_MB_RAMonly_RW' with
   type 'MBSystemEnvironment_axi0_bus_mb_ramonly_rw_wrapper' could not be
   resolved. A pin name misspelling can cause this, a missing edif or ngc file,
   case mismatch between the block name and the edif or ngc file name, or the
   misspelling of a type name. Symbol
   'MBSystemEnvironment_axi0_bus_mb_ramonly_rw_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/AXI1_BUS_Lite_RW' with type
   'MBSystemEnvironment_axi1_bus_lite_rw_wrapper' could not be resolved. A pin
   name misspelling can cause this, a missing edif or ngc file, case mismatch
   between the block name and the edif or ngc file name, or the misspelling of a
   type name. Symbol 'MBSystemEnvironment_axi1_bus_lite_rw_wrapper' is not
   supported in target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/axi_timer_0' with type
   'MBSystemEnvironment_axi_timer_0_wrapper' could not be resolved. A pin name
   misspelling can cause this, a missing edif or ngc file, case mismatch between
   the block name and the edif or ngc file name, or the misspelling of a type
   name. Symbol 'MBSystemEnvironment_axi_timer_0_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/clock_generator_0' with type
   'MBSystemEnvironment_clock_generator_0_wrapper' could not be resolved. A pin
   name misspelling can cause this, a missing edif or ngc file, case mismatch
   between the block name and the edif or ngc file name, or the misspelling of a
   type name. Symbol 'MBSystemEnvironment_clock_generator_0_wrapper' is not
   supported in target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/debug_module' with type
   'MBSystemEnvironment_debug_module_wrapper' could not be resolved. A pin name
   misspelling can cause this, a missing edif or ngc file, case mismatch between
   the block name and the edif or ngc file name, or the misspelling of a type
   name. Symbol 'MBSystemEnvironment_debug_module_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/microblaze_0' with type
   'MBSystemEnvironment_microblaze_0_wrapper' could not be resolved. A pin name
   misspelling can cause this, a missing edif or ngc file, case mismatch between
   the block name and the edif or ngc file name, or the misspelling of a type
   name. Symbol 'MBSystemEnvironment_microblaze_0_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/microblaze_0_bram_block'
   with type 'MBSystemEnvironment_microblaze_0_bram_block_wrapper' could not be
   resolved. A pin name misspelling can cause this, a missing edif or ngc file,
   case mismatch between the block name and the edif or ngc file name, or the
   misspelling of a type name. Symbol
   'MBSystemEnvironment_microblaze_0_bram_block_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/microblaze_0_d_bram_ctrl'
   with type 'MBSystemEnvironment_microblaze_0_d_bram_ctrl_wrapper' could not be
   resolved. A pin name misspelling can cause this, a missing edif or ngc file,
   case mismatch between the block name and the edif or ngc file name, or the
   misspelling of a type name. Symbol
   'MBSystemEnvironment_microblaze_0_d_bram_ctrl_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/microblaze_0_dlmb' with type
   'MBSystemEnvironment_microblaze_0_dlmb_wrapper' could not be resolved. A pin
   name misspelling can cause this, a missing edif or ngc file, case mismatch
   between the block name and the edif or ngc file name, or the misspelling of a
   type name. Symbol 'MBSystemEnvironment_microblaze_0_dlmb_wrapper' is not
   supported in target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/microblaze_0_i_bram_ctrl'
   with type 'MBSystemEnvironment_microblaze_0_i_bram_ctrl_wrapper' could not be
   resolved. A pin name misspelling can cause this, a missing edif or ngc file,
   case mismatch between the block name and the edif or ngc file name, or the
   misspelling of a type name. Symbol
   'MBSystemEnvironment_microblaze_0_i_bram_ctrl_wrapper' is not supported in
   target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/microblaze_0_ilmb' with type
   'MBSystemEnvironment_microblaze_0_ilmb_wrapper' could not be resolved. A pin
   name misspelling can cause this, a missing edif or ngc file, case mismatch
   between the block name and the edif or ngc file name, or the misspelling of a
   type name. Symbol 'MBSystemEnvironment_microblaze_0_ilmb_wrapper' is not
   supported in target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/microblaze_0_intc' with type
   'MBSystemEnvironment_microblaze_0_intc_wrapper' could not be resolved. A pin
   name misspelling can cause this, a missing edif or ngc file, case mismatch
   between the block name and the edif or ngc file name, or the misspelling of a
   type name. Symbol 'MBSystemEnvironment_microblaze_0_intc_wrapper' is not
   supported in target 'spartan6'.
ERROR:NgdBuild:604 - logical block
   'MBSystemEnvironment_top_i/MBSystemEnvironment_i/proc_sys_reset_0' with type
   'MBSystemEnvironment_proc_sys_reset_0_wrapper' could not be resolved. A pin
   name misspelling can cause this, a missing edif or ngc file, case mismatch
   between the block name and the edif or ngc file name, or the misspelling of a
   type name. Symbol 'MBSystemEnvironment_proc_sys_reset_0_wrapper' is not
   supported in target 'spartan6'.
INTERNAL_ERROR::45 - Memory allocation leak of 112 bytes at 0x07280E18 for a 'AddressMappingType' record.
INTERNAL_ERROR::45 - Memory allocation leak of 43 bytes at 0x072A2210 for a StrNew.
INTERNAL_ERROR::45 - Memory allocation leak of 88 bytes at 0x073220A8 for a 'AddressMapType' record.
INTERNAL_ERROR::45 - Memory allocation leak of 40 bytes at 0x072528F8 for a 'symbol_context' record.
INTERNAL_ERROR::45 - Memory allocation leak of 36 bytes at 0x072A2600 for a StrDup.
INTERNAL_ERROR::45 - Memory allocation leak of 16 bytes at 0x072A3940 for a 'DataFileNameListType' record.
INTERNAL_ERROR::45 - Memory allocation leak of 24 bytes at 0x072A3AE8 for a 'AddressSpaceLinkType' record.
INTERNAL_ERROR::45 - Memory allocation leak of 96 bytes at 0x07321F00 for 'void *' data.

在此之前,我不必煮这种三明治: ISE14.7 合成15.09

项目的主要部分取决于XPS。因此,在综合结束时,响应是什么都不做:

@I::"D:\WinFiles\Documents\XilinxProjects\ExMyProcessor1\MBSystemEnvironment\hdl\MBSystemEnvironment.v"
    @I::"D:\WinFiles\Documents\XilinxProjects\ExMyProcessor1\MBSystemEnvironment\MBSystemEnvironment_top.v"
    @I::"D:\WinFiles\Documents\XilinxProjects\ExMyProcessor1\ExMyProcessorTOP_m.v"
    @I:"D:\WinFiles\Documents\XilinxProjects\ExMyProcessor1\ExMyProcessorTOP_m.v":"D:\WinFiles\Documents\XilinxProjects\ExMyProcessor1\ExMACROS.v"
    @I:"D:\WinFiles\Documents\XilinxProjects\ExMyProcessor1\ExMyProcessorTOP_m.v":"D:\WinFiles\Documents\XilinxProjects\ExMyProcessor1\LCD_CONTROLLER_m.v"
    Verilog syntax check successful!
    Selecting top level module ExMyProcessorTOP_m
    @N: CG364 :"D:\WinFiles\Documents\XilinxProjects\ExMyProcessor1\MBSystemEnvironment\hdl\MBSystemEnvironment.v":3650:7:3650:50|Synthesizing module MBSystemEnvironment_proc_sys_reset_0_wrapper
    @W: CG146 :"D:\WinFiles\Documents\XilinxProjects\ExMyProcessor1\MBSystemEnvironment\hdl\MBSystemEnvironment.v":3650:7:3650:50|Creating black box for empty module MBSystemEnvironment_proc_sys_reset_0_wrapper
    @N: CG364 :"D:\WinFiles\Documents\XilinxProjects\ExMyProcessor1\MBSystemEnvironment\hdl\MBSystemEnvironment.v":3699:7:3699:51|Synthesizing module MBSystemEnvironment_microblaze_0_intc_wrappe
    @W: CG146 :"D:\WinFiles\Documents\XilinxProjects\ExMyProcessor1\MBSystemEnvironment\hdl\MBSystemEnvironment.v":3699:7:3699:51|Creating black box for empty module MBSystemEnvironment_microblaze_0_intc_wrapper
    ...
    @W: MT246 :"d:\winfiles\documents\xilinxprojects\exmyprocessor1\mbsystemenvironment\hdl\mbsystemenvironment.v":1757:4:1757:15|Blackbox MBSystemEnvironment_debug_module_wrapper is missing a user supplied timing model. This may have a negative effect on timing analysis and optimizations (Quality of Results) 
    @W: MT246 :"d:\winfiles\documents\xilinxprojects\exmyprocessor1\mbsystemenvironment\hdl\mbsystemenvironment.v":1112:4:1112:15|Blackbox MBSystemEnvironment_microblaze_0_wrapper is missing a user supplied timing model. This may have a negative effect on timing analysis and optimizations (Quality of Results) 
    @W: MT246 :"d:\winfiles\documents\xilinxprojects\exmyprocessor1\mbsystemenvironment\hdl\mbsystemenvironment.v":1093:4:1093:26|Blackbox MBSystemEnvironment_microblaze_0_bram_block_wrapper is missing a user supplied timing model. This may have a negative effect on timing analysis and optimizations (Quality of Results) 
    @W: MT246 :"d:\winfiles\documents\xilinxprojects\exmyprocessor1\mbsystemenvironment\hdl\mbsystemenvironment.v":973:4:973:27|Blackbox MBSystemEnvironment_microblaze_0_d_bram_ctrl_wrapper is missing a user supplied timing model. This may have a negative effect on timing analysis and optimizations (Quality of Results) 
    @W: MT246 :"d:\winfiles\documents\xilinxprojects\exmyprocessor1\mbsystemenvironment\hdl\mbsystemenvironment.v":943:4:943:20|Blackbox MBSystemEnvironment_microblaze_0_dlmb_wrapper is missing a user supplied timing model. This may have a negative effect on timing analysis and optimizations (Quality of Results) 
    @W: MT246 :"d:\winfiles\documents\xilinxprojects\exmyprocessor1\mbsystemenvironment\hdl\mbsystemenvironment.v":823:4:823:27|Blackbox MBSystemEnvironment_microblaze_0_i_bram_ctrl_wrapper is missing a user supplied timing model. This may have a negative effect on timing analysis and optimizations (Quality of Results) 
    @W: MT246 :"d:\winfiles\documents\xilinxprojects\exmyprocessor1\mbsystemenvironment\hdl\mbsystemenvironment.v":793:4:793:20|Blackbox MBSystemEnvironment_microblaze_0_ilmb_wrapper is missing a user supplied timing model. This may have a negative effect on timing analysis and optimizations (Quality of Results) 
    @W: MT246 :"d:\winfiles\documents\xilinxprojects\exmyprocessor1\mbsystemenvironment\hdl\mbsystemenvironment.v":761:4:761:20|Blackbox MBSystemEnvironment_microblaze_0_intc_wrapper is missing a user supplied timing model. This may have a negative effect on timing analysis and optimizations (Quality of Results) 
    @W: MT246 :"d:\winfiles\documents\xilinxprojects\exmyprocessor1\mbsystemenvironment\hdl\mbsystemenvironment.v":734:4:734:19|Blackbox MBSystemEnvironment_proc_sys_reset_0_wrapper is missing a user supplied timing model. This may have a negative effect on timing analysis and optimizations (Quality of Results) 
    ...
    MBSystemEnvironment_microblaze_0_intc_wrapper  1 use
    MBSystemEnvironment_microblaze_0_wrapper  1 use
    MBSystemEnvironment_proc_sys_reset_0_wrapper  1 use
    MBSystemEnvironment_rs232_wrapper  1 use
    VCC             4 uses
    I/O ports: 76
    I/O primitives: 74
    IBUF           2 uses
    IOBUF          17 uses
    OBUF           55 uses
    I/O Register bits:                  0
    Register bits not including I/Os:   0 (0%)
    Total load per clock:
    @S |Mapping Summary:
    Total  LUTs: 0 (0%)
     Number of unique control sets:              0
    Region Summary:
    Other LUTs: 0 Other Registers: 0
    Mapper successful!

也许我不应该使用PN(ISE)外壳,而是使用Synplify外壳本身?

0 个答案:

没有答案