See Also

A fixed-size LogicLock^™ region can have a locked or floating location, but an auto-size LogicLock region must have a floating location. The Quartus^® II software determines an optimal location for floating regions during compilation. If you are satisfied with the locations chosen, you can back-annotate them for use on subsequent compilations.

When you create a LogicLock region by drawing it in the Floorplan Editor, it is locked in its current location. You can change its location to a floating location by right-clicking its top bar and choosing Toggle Locked State (right button pop-up menu). The Floorplan Editor displays locked regions with a solid line and floating regions with a dashed line.

When you create a LogicLock region by using the LogicLock Regions window, it has a floating location. You can use the Location tab to change the region's origin or to lock its location. Although the Quartus II software determines the actual location of a floating region during compilation, the Current Assignments floorplan and Timing Closure floorplan display the region at the location specified by its current origin, which is listed on the Location tab under Origin Settings.

The Quartus II software interprets the location of a child LogicLock region as relative to its parent region's origin. When you lock the location of a child region, the child region's location is locked only relative to its parent region's origin, not relative to the target device. When you move a parent region, the Quartus II software automatically updates the locations of all of its descendant regions to maintain their positions relative to the parent region.

The Fitter requires that you assign floating locations to any child LogicLock regions that have an auto-size parent LogicLock region.

The Fitter permits locked LogicLock regions to overlap with other LogicLock regions. However, the Fitter cannot place a floating LogicLock region in a location that causes it to overlap with other floating LogicLock regions except its ancestor and descendant regions.

For Stratix^™ and Stratix^™ GX devices, if a LogicLock region partially overlaps with an M4K block, M-RAM block, or DSP block, the Quartus II software considers the LogicLock region to contain the whole M4K block, M-RAM block, or DSP block, and the Fitter may place nodes assigned to the LogicLock region anywhere on the overlapping M4K block, M-RAM block, or DSP block.

For Cyclone^™ devices, if a LogicLock region partially overlaps with an M4K block, the Quartus II software considers the LogicLock region to contain the whole M4K block and the Fitter may place nodes assigned to the LogicLock region anywhere on the overlapping M4K block.

LogicLock regions with floating locations are not supported for Mercury^™ devices.

Back to Top