Specifications

Embedded System Tools Guide (EDK 6.2i) www.xilinx.com 79
UG111 (v1.4) January 30, 2004 1-800-255-7778
Creating New Peripherals
R
EDK repository is the more versatile storage mechanism because many XPS projects can
access one EDK repository. This tool takes care of creating the right directory structures
and interface files.
In this panel, you indicate whether you want a XPS project or EDK repository, and what
the physical location of the XPS project or EDK repository is. A XPS project is a directory
with a .xmp file. A EDK repository is a directory.
The actual core directory gets created in one of the following based on whether you choose
EDK repository or XPS project:
<EDK-Repository-Dir>/MyProcessorIPLib/pcores
or
<Directory-containing-XPS-Project-File>/pcores
Identifying Module and Version
In this panel you do the following:
x Indicate the name of your top module Typically this is the name of the top module in
the design hierarchy that makes up the peripheral.
x Optionally indicate the version identifier for your module The version identifier for
the core has three components: a major revision number, a minor revision number and
a hardware/software compatibility identifier.
The EDK requires that the top module and (possibly) other sub-modules for your core be
compiled into a logical library named after the top module and the version number. The
rules are best described through the following examples:
It is very important that all the elements of this peripheral are compiled into the indicated
logical library or into some other logical library already available in the XPS project or in
any of the currently accessible EDK repositories. This tool will actually process only the
files that are compiled into the logical library indicated by the above examples. Other files
are assumed to be available in the XPS project, or in any of the currently accessible
repositories. Naturally, this means that the library and use lines in your VHDL need to use
this logical library name.
Additionally, the chosen library name cannot be
work.
The subsequent sections of this document deals with details of peripheral creation or
peripheral import using this tool.
Table 4-1: Naming conventions for peripherals using version identifiers
Peripheral Name spi46
Major version 9
Minor Version 12
Software/hardware compatibility identifier g
Logical library name spi46_v9_12_g
Table 4-2: Naming conventions for peripherals not using version identifiers
Peripheral Name spi46
Logical library name spi46