Creating Peripherals That do NOT Require PowerPC Control:

There are two methods of implementing non-PowerPC-controlled peripherals in XPS. The first method is to build the pcores-side of the file structure as described in the File Structure section of this guide. The second method is to use Xilinx Platform Studio’s built in “Create or Import Peripheral Wizard.” This wizard can be accessed in XPS from the “Hardware” drop-down -> “Create or Import Peripheral…” The steps are as follows:

  1. This utility gives two options: “Create templates for a new peripheral” or “Import existing peripheral.” For simply wrapping a peripheral in an EDK-compliant manner, one must choose “Import Existing Peripheral.”
  2. The wizard will then prompt for a repository location or the project. Either is fine, but for development purposes, until the peripheral is finished, it can be nice to keep it in the project directory itself.
  3. The wizard will then prompt for a name. The name must be the same as your top-level HDL module. If it is not, the wizard will later complain of not being able to find a top-level module.
  4. You may give the peripheral a version number if you wish.
  5. The wizard will then prompt for what elements make up the peripheral – check all that may apply.
  6. At the next screen, the wizard will ask for the HDL-source file type. It’s important to select the proper type. Otherwise, not all of the files may appear when the user tries to add them later.
  7. At this point the user can choose to use an XST file if the user was developing the peripheral in ISE/Project Navigator, use a *.pao file that the user coded by hand (see above section), or just directly add the files manually and have XPS determine the proper structure. If the user chooses the last option, the user must remember to order the HDL files by placing the top-level file last in the structure.
  8. If the wizard is able to successfully add the HDL files, it will proceed to aid the user in applying the proper BUS interface. The peripheral MUST already have the compliant bus logic/ports instantiated in its HDL. This part of the wizard is not to be used for implementing a bus in your design – if the peripheral uses no bus, simply deselect “Select bus interface(s).”
  9. The wizard will then let the user configure any of the ports as being interrupt compliant
  10. The wizard will then allow the user to define any specific attributes if the ports allow for it
  11. The wizard will then prompt for any netlist files
  12. The wizard will then prompt for any documentation files
  13. The wizard will then proceed to generate and place the proper file structure for the user’s peripheral in EDK-compliant format

PREV: The File Structure for XPS/EDK-based Peripherals
| HOME | NEXT: Creating Peripherals That Require PowerPC Control
Last modified 16 years ago Last modified on Jul 12, 2006, 12:02:18 AM