Manualshelf

Specifications

ManualsBrandsVector ManualsAir CompressorVEC256
151152153154155156157158159160
160 www.xilinx.com Embedded System Tools Guide (EDK 6.2i)
1-800-255-7778 UG111 (v1.4) January 30, 2004
Chapter 9: Format Revision Tool
R
Revup from EDK 3.2 to EDK 6.1
The Format Revision Tool (revup32to61) updates an existing EDK 3.1 or 3.2 project to a
format for EDK 6.1. Note that if you open an old project with XPS, then it will
automatically revup the project to the new format. A project revup will also automatically
cause revup of all the hardware repository data files (MPD, BBD, and PAO) referred to by
that project and that of the local myip and pcores directories. RevUp can optionally update
just the hardware repository data files . The upgrade is a format update and not an IP
upgrade. Note that there is no update required for software repository (MDD, MLD) files.
In EDK 6.1, the PSF version is 2.1.0. Previous supported versions include 2.0.0 for MPD,
BBD, and PAO files and version 2.1.0 for MDD, and MLD files.
EDK tools are always running with the latest formats. Only RevUp needs to maintain
compatibility with older versions.
Tool Usage
Run revup32to61 as follows from the command line:
revup32to61 <system>.xmp
revup32to61 -rd <repository_dir>
The following are the options supported:
-h (Help)
The -h option displays the usage menu and quits.
-rd (repository directory)
The -rd option allows you to specify the repository directory which needs revup. The
repository directory is the parent directory of the pcores or myip directory. If this
option is specified, then you can not revup an old EDK project (XMP) at the same time.
Limitations
The limitations of the revup32to61 are:
x If you have any IP in myip directory, even though revup will update the format of
data files, you must manually move those IP to pcores directory. EDK 6.1 tools do not
search for IPs in myip directory.
x If you have a EDK 3.1 project, the software repository revup does not happen
automatically. If you your own MDD files, you must manually update them to 2.1.0
format. A manual update of MDD files was required even when reving up from EDK
3.1 to EDK 3.2.