Answers Database


2.1i Floorplanner - PROHIBIT constraints are not supported.


Record #5106

Product Family: Software

Product Line: Merged Core

Product Part: Floorplanner

Product Version: 1.5

Problem Title:

2.1i Floorplanner - PROHIBIT constraints are not supported.


Problem Description:
Urgency: Standard

General Description: Prohibit Constraints placed in the ucf file
will be ignored by the Floorplanner. In the Floorplanner, this
allows logic to be placed in prohibited areas. Currently it is
the responsibility of the user to not place logic in prohibited
locations within the Floorplanner.

When the design is implemented using the floorplan files,
the PROHIBIT constraints in the UCF file are ignored. If
the IOB locations are not specified in the floorplan and
the design is re-implemented using the floorplan file, IOBs
could be placed in locations that are listed as prohibited
in the UCF file.

In a future software release, the Floorplanner will support
the placement of PROHIBIT constraints from within the
Floorplanner tool.



Solution 1:

To resolve this issue, the design can be run without the
floorplan file (so that the PROHIBIT constraints are not
ignored). The design can then be brought in to the
Floorplanner and the Floorplan -> Replace All With
Placement option will ensure that the IOBs are
placed in non-prohibited locations. The user can
then remove/adjust logic as desired and save the
floorplan. By using this technique, the IOBs will be
locked to locations that are not prohibited in the
floorplan file.



Solution 2:

Another way to get around this problem is to manually move
the IOB locations that may be in prohibited areas to
non-prohibited areas in the Floorplanner. Saving this
floorplan will preserve the IOB locations.



Solution 3:

Another possible workaround to this issue is to manually
edit the <design>.mfp file. This is the file that is produced
by the Flooplanner when the floorplan is saved. To do this:

1. Floorplan the desired logic and save the floorplan
2. Open the <design>.mfp file in a text editor
3. Add the PROHIBIT constraints to the end of the .mfp
    file with the following syntax (for example to prohibit P10):
        PROHIBIT P10 ;
4. Run the tools as usual through the design flow

NOTE : This method is recommended only if no other
method will resolve the issue. It is not recommended for
the user to manually edit the .mfp file as a part of the
normal design flow.




End of Record #5106 - Last Modified: 12/06/99 08:12

For the latest news, design tips, and patch information on the Xilinx design environment, check out the Technical Tips!