Specifications

46 www.xilinx.com Embedded System Tools Guide (EDK 6.2i)
1-800-255-7778 UG111 (v1.4) January 30, 2004
Chapter 2: Xilinx Platform Studio (XPS)
R
Device and Repository
The target device for the project can be changed here. There are four different items:
Architecture, Device Size, Package, and Speed Grade.
Users can specify the Search Path directories here. However, if this option is changed,
users must close the project immediately. If this option is changed here, the changes will be
effective only if the project is closed and loaded again.This option corresponds to the -lp
option of various batch tools. See Chapter 7, “Library Generator” and Chapter 5, “Platform
Generator” for more information.
Users can also specify thier own Makefile to be used in XPS.Before EDK 6.2, XPS used to
generate only 1 makefile, namely <projname>.make. In 6.2, the XPS makefile has been split
into two parts
x The main makefile: <projname>.make
x The include makefile: <projname>_incl.make.
The <projname>_incl.make file contains all options and settings defined in form of
macros. The main makefile <projname>.make contains all the targets and commands for
the complete flow. The main makefile includes the <projname>_incl.make using the
following make directive:-
include system_incl.make
This makes all the macros defined in <projname>_incl.make visible in <projname>.make.
XPS always writes out both the makefiles. However, users can choose not to use the
<projname>.make file for thier flow. Instead, they can specify thier own makefile. Note
that user makefile specified must be different from the two makefiles generated by XPS.
Users are expected to include the <projname>_incl.make in thier own makefile too. This
way, any changes they make to any options and settings in XPS will be reflected in thier
own makefile too. Typically, a user would generate the <projname>.make file once and
then copy it and modify it for thier own purposes.
Note that if you will need to update your makefile whenever you make a significant
change in your design. Some of the changes which affect makefile structure are:-
x Adding, deleting, or renaming a processor
x Adding, deleting, or renaming a software application
x If you change the choice of implementation tool between ISE (ProjNav) and
XPS(Xflow).
x The ACE file generation command might be changed if you change the number of
processors in your design or if you add/delete opb_mdm ip for microblaze designs.
x The XILINX_EDK_DIR macro defined in system_incl.make file changes across Unix
(Solaris/Linux) and Windows platforms.
Hierarchy and Flow
This tab allows user to specify the design hierarchy, whether the processor design being
done in XPS is the top level module or if it is just a sub-module in the entire hierarchy. If
this design is a sub-module, the Top Instance edit box allows you to specify the instance
name used to instantiate this module in the top-level design. This corresponds to the -
iobuf and -ti options of PlatGen tool.
From EDK 6.1 onwards, XPS only supports modular (hierarchical) design mode. The Flat
mode is not supported.User can also choose whether to run the Xilinx Synthesis Tool
(XST).