| List of Messages | |
CAUSE: You specified the assignment MAX_RAM_BLOCKS_M4K to the specified value either for this partition or for the whole project. As a result, the Compiler assumes the given number of M4K/M9K RAM blocks exist for the given partition (or the project) and tries to limit M4K/M9K RAM block usage to this number. This overrides the usual method of determining the M4K/M9K RAM block limit from the device information. The assignment MAX_RAM_BLOCKS_M4K can be set as a global project-wide assignment and/or on a particular partition for incremental compilation. It can be set as a project-wide option by clicking Maximum Number of M4K/M9K Memory Blocks in the More Analysis and Synthesis Settings dialog box. It can be set on a partition using the Assignment Editor. The partition-specific assignment overrides the global assignment, if any. If this assignment is set as a project-wide option, each partition that does not have a partition-specific assignment will limit the M4K/M9K RAM block usage to the global value. This means that if there is no project-wide MAX_RAM_BLOCKS_M4K assignment, each partition that doesn't have this assignment will assume that it has all the M4K/M9K RAM blocks in the device available to use. This can result in a no-fit error. As a result, it is recommended that you make partition-specific assignments when incremental compilation is in use.
ACTION: No action is required.
Copyright© 2015 Altera Corporation. All rights reserved. ALTERA, ARRIA, CYCLONE, HARDCOPY, MAX, MEGACORE, NIOS, QUARTUS, STRATIX, and all other brands, unless noted otherwise, and/or trademarks of Altera Corporation in the U.S. and other countries.