LogicLock Routing Constraints File Name logic option

A logic option that specifies the name of the file from which to import an entity's back-annotated routing.

This option is useful for hierarchical or bottom-up designs in which the user wishes to preserve the routing results that have been previously generated for a subdesign entity. To use this option, you must create a separate Quartus® Prime Standard Edition project for each subdesign entity. When timing requirements are met, the locations of resources in each subdesign entity can be back annotated with routing information. Importing these back-annotated resource locations and routing constraints into a top-level design preserves the subdesign entity's performance.

If you turn on Back-annotated routing in the Advanced Import Settings dialog box, you must use the LogicLock Routing Constraints File Name logic option to specify the Routing Constraints File (.rcf) Definition from which to import the back-annotated routing.

Important: Important: Specifying the LogicLock Routing Constraints File Name logic option for an entity does not import the entity's back-annotated routing into the top-level design, but only specifies the Routing Constraints File to use when importing. To import the back-annotated routing, you must use the LogicLock Regionswindow.

This option is available for supported device(MAXII, and MAXV) families.

Scripting Information

Keyword:ll_rcf_import_file

Settings:<file name>
Related concepts

About Quartus Prime Standard Edition Scripting
Related reference

Advanced Import Settings Dialog Box

Contact Altera | Legal Notice

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.