Intel® Quartus® Prime Pro Edition User Guide: Design Optimization

ID 683641
Date 12/04/2023
Public
Document Table of Contents

6.3.2.1.3. Considerations for Auto Sized Regions

If you use Auto/Floating Size/State Logic Lock regions, consider the following limitations and effects:
  • Auto/Floating regions cannot be reserved.
  • Verify that your Logic Lock region is not empty. If you do not assign any instance to the region, the Fitter reduces the size to 0 by 0, making the region invalid.
  • The region may or may not be associated with a partition. When you combine partitions with Auto/Floating Size/State Logic Lock regions, you get flexibility to solve your particular fitting challenges. However, every constraint that you add reduces the solutions available, and too many constraints can result in the Fitter not finding a solution. Some cases are:
    • If a partition is preserved at synthesis or not preserved, the Logic Lock region confines the logic to a specific area, allowing the Fitter to optimize the logic within the partition, and optimize the placement within the Logic Lock region.
    • If a partition is preserved at placement, routed, or final; a Logic Lock region is not an effective placement boundary, because the location of the partition's logic is fixed.
    • However, if the Logic Lock region is reserved, the Fitter avoids placing other logic in the area, which can help you reduce resource congestion.
  • Once the outcome of the Logic Lock region meets your specification, you can:
    • Convert the Logic Lock region to Fixed/Locked Size/State.
    • Leave the Logic Lock region with Auto/Floating Size/State attribute and use the region as a “keep together” type of function.
    • If the Logic Lock region is also a partition, you can preserve the place and route through the partition and remove the Logic Lock region entirely.