Xilinx LogiCORE MicroBlaze Product Manual page 58

Step
Tcl Command:
Error message:
Possible causes:
Corrective actions: • With PlanAhead, select each instance and use Generate IP in the context menu,
Step:
Tool:
Error message:
Possible causes:
Corrective action:
Step:
Tool:
Error message:
Possible causes:
Corrective action:
Step:
Tool:
Error message:
MicroBlaze Micro Controller System v1.3
PG048 December 18, 2012
Create Merged BMM, Update Tool to Use BMM
microblaze_mcs_setup
ERROR: Could not find a BMM file for instances. Please regenerate the MicroBlaze
MCS instances.
• With PlanAhead, the BMM file has not been generated after customizing a
MicroBlaze MCS instance, or after adding an existing IP.
• The BMM file has inadvertently been deleted.
or synthesize the project, and then invoke the command again.
• With Project Navigator, double-click on each MicroBlaze MCS instance to
regenerate it, and then invoke the command again.
Implement Project
Ngdbuild
NgdBuild:989 - Failed to process BMM information
• The parameter "Instance Hierarchical Design Name" set in the MicroBlaze MCS
configuration dialog does not match the actual instantiation name or place in the
instantiation hierarchy. Note that this is case sensitive in the tools.
• The parameter "Memory Size" set in the MicroBlaze MCS configuration dialog has
changed, but the corresponding BMM file has not been updated.
• Change "Instance Hierarchical Design Name" to the correct value in the
MicroBlaze MCS configuration dialog. This is the actual name used in the
instantiation, prefixed with all hierarchical levels below the top instance,
separated with /.
• Regenerate the BMM file according to the previous item.
Implement Project
Ngdbuild
NgdBuild:634 - Cannot open input BMM file
The Ngdbuild -bm option does not indicate the correct BMM file.
Change the Ngdbuild option, either manually, or by invoking
microblaze_mcs_setup in the Tcl Console.
Implement Project
Ngdbuild
NgdBuild:76 - File "path/component-name.ngc" cannot be merged into block
"instance-name" (TYPE="component-name") because one or more pins on the block,
including pin "pin-name", were not found in the file. Please make sure that all pins
on the instantiated component match pins in the lower-level design block
(irrespective of case). If there are bussed pins on this block, make sure that the
upper-level and lower-level netlists use the same bus-naming convention.
www.xilinx.com
Appendix B: Debugging
57