Answers Database
Design Manager M1: What are the recommended set of files to be archived in order to restore an M1 design?
Record #4285
Product Family: Software
Product Line: M1 Graphical/General
Product Part: Design Manager
Product Version: 1.5is2
Problem Title:
Design Manager M1: What are the recommended set of files to be archived in order to restore
an M1 design?
Problem Description:
Urgency : Standard
General Description:
In the event that a M1 project must be archived, what are the minimum
recommended set of files to be included in the archive so as to be able
to restore the project in the future ?
Solution 1:
Besides the design source file (SCHEMATIC or HDL), below is a listing of files
that we recommend to include (if applicable) when preparing a design archive:
1. Source netlist (*.edn,*.edf, *.xnf, *.xtf, *.sxnf, *.pld, *.*...) and/or
schematic/HDL. These files be automatically copied into the
implementation version/revision directories. To do so, please
reference (Xilinx Solution 6704).
2. LogiBLOX output netlists (*.ngo, *.ngc [M1.5], *.mem for memory elements)
These files will be needed if a change is made to the input design, which
would then require the Translate stage to be rerun.
3. A user constraint file (<design>.UCF). If changes need to be made to
the *.pcf file, then this should also be included.
4. A user script file (optional) or program.his. The latter has all the
options used when running the individual programs (NGDBUILD, MAP, PAR,
TRCE, etc..)
5. Placed and routed *.ncd file. This represents the ouput of PAR (NOT to be
mistaken with the map.ncd file, produced after MAP). Running Bitgen on the
<placed and routed>.ncd file will allow you to regenerate your bitstream
(*.bit)
The following files are ONLY produced when running the tools from the Design Manager GUI:
6. The bitgen.ut stores the options run during Bitgen. Furthermore, the fe.log
file is often a good source of infomation in regards to options run during a
given implementation.
In general, when a project is implemented via the Design Manager GUI, it is
best to archive all the source netlists (steps #1,2,and 3 above), and simply
everything under the xproj/ directory, which is your design's default working
directory when using the DM GUI. Doing this allows you to include the
<design>.xpj file, which stores the project information required to open
the DM project within the GUI itself (File->Open Project).
For information on how to restore a project after it has moved locations,
please see (Xilinx Solution 2942).
End of Record #4285 - Last Modified: 06/07/99 17:36 |
