| CAUSE: | You directed the Quartus II software to save synthesis results to a Verilog Quartus Mapping File (.vqm)), but your design contains initialized RAM or ROM and you selected a device from the APEX II or Mercury device families. Because the Fitter packed multiple logical RAMs or ROMs into a single Embedded System Block (ESB), your design's original Memory Initialization Files (.mif or .hex) for RAM or ROM are not usable with the VQM File generated by Incremental Synthesis. The Compiler wrote the specified MIF to the directory listed in the top-level message that precedes this message for use with the generated VQM File. |
| ACTION: | When you create a new project using the VQM File generated by Incremental Synthesis, you must place the new MIFs in the same directory as the VQM File. These MIFs replace all MIF or HEX memory initialization files for all RAM or ROM instantiated in the VQM File. However, they do not replace MIFs or HEX Files for content-addressable memory (CAM), so you must use your original MIF or HEX File for any CAM in the design. |
See also:
Saving Synthesis Results for an Entity to a Verilog Quartus Mapping File
Specifying the Device Family & Device for Compilation
|
- PLDWorld - |
|
|
| Created by chm2web html help conversion utility. |