Answers Database
M1.5i/2.1i: How to preserve the pinout of a previous PAR run (pad2ucf)
Record #3534
Product Family: Software
Product Line: Merged Core
Product Part: Timing
Problem Title:
M1.5i/2.1i: How to preserve the pinout of a previous PAR run (pad2ucf)
Problem Description:
Urgency: standard
General Description:
How does one keep the same pinout between PAR runs, if the
original UCF does not contain a LOC for every PAD?
Solution 1:
In M1.5 there is a utility which creates a ucf file with the pin assignments from a previous run.
Select the version/revision that you want to use.
Select 'Design -> Lock Pins'.
This will add the pin assignments to the ucf file specified in the Design Manager. If no file is spe
cified it will create a ucf file.
Solution 2:
You can use the PERL script "pad2ucf", available at:
ftp://ftp.xilinx.com/pub/utilities/M1_workstation/pad2ucf.tar.Z
or
ftp://ftp.xilinx.com/pub/utilities/M1_pc/pad2ucf.zip
This script will take the .pad report produced by PAR and
recreate the equivalent UCF constraints that would have
LOC'd the signals to the desired pads. The UCF may then be
used for subsequent PAR runs.
One note: this script assumes the name of the signal in the
UCF is the name of the IOB reported in the .pad. This
assumption should always be true, provided that a BLKNM
or HBLKNM was not placed on the pad.
End of Record #3534 - Last Modified: 07/13/99 15:59 |
