Answers Database
2.1i COREGEN: "ERROR: ... Can not find initial Contents file to read: <module_name>.mif" when READ MIF is selected
Record #8316
Product Family: Software
Product Line: LogiCore
Product Part: Coregen IP Modules
Problem Title:
2.1i COREGEN: "ERROR: ... Can not find initial Contents file to read: <module_name>.mif"
when READ MIF is selected
Problem Description:
Urgency: hot
General Description:
The Virtex Block and Distributed Memory cores may not find an MIF file in the project
directory when the READ MIF option is selected. When this is the case, the following
error message may be seen:
"ERROR: Customization parameter rule checks failed. Terminating core
elaboration: Can not find initial Contents file to read: <module_name>.mif
ERROR: SimGenerator: Failure to set Sim customization parameters for core
Single_Port_Block_Memory."
Solution 1:
There is a bug in the Block Memory cores in which the core customizer
writes out the MIF filie to wherever the CORE Generator application was started up
instead of in the project directory.
The customization GUI also looks for the MIF file in this location when you select
the Read MIF option. Unfortunately there is no way to specify the location of
the MIF to the customization GUI explicitly.
On PCs:
-------------
Normally the start directory is defined as $XILINX/coregen/tmp when the CORE
Generator is invoked in standalone mode (directly through the Windows Start
Menu). This is where the CORE Generator tries to find the MIF file when "READ
MIF" is selected.
Ther workaround is to copy the MIF file into your $XILINX/coregen/tmp directory,
and regenerate the core. You must then re-implement the design and generate
a new timing simulation netlist using the new core.
If you invoke the CORE Generator from the Foundation tools, the MIF may be
read in from the Fndtn\Active\Projects directory in some cases.
On UNIX Workstations:
-------------------------------------
CORE Generator expects to find the MIF file in the directory from which you invoked
the CORE Generator application if you run it standalone.
This problem will be fixed in the C_IP4 IP Modules update.
End of Record #8316 - Last Modified: 12/17/99 19:32 |
