Frequently Asked Questions / EDK

---

The WARP Board does not appear in the list of available boards in the Base System Builder.

There could be a few reasons for the board not appearing in the list.

1. Make sure the you have the latest board description file (*.xbd) from the repository. Refer to the XBD Installation Readme for details on where to save the file.
2. If the board still does not appear when trying to create a project:
   1. Start Base System Builder
   2. On the page to select project file, under "Advanced Options", check "Use Repository Paths" and give the location as:

       C:\EDK\board
      

      Then select "Ok" and the board should appear in the list.

---

How do I install custom peripherals from the repository?

1. To install the custom peripherals create a folder on your computer:

   <xilinx_install_drive>:\EDK_user_repository\MyProcessorIPLib
   

2. Create two folders, pcores amd drivers. Depending on which version of the EDK you installed, these folders may already exist.
3. Copy the folders of the peripheral you wish to install from the repository to your computer. Remember to keep the same directory structure as seen in the repository. Copy the peripheral's files from both the pcores and drivers folders or the Base System Builder will give an error. Some peripherals do not have drivers; in this case the driver is not needed for XPS to recognize the peripheral.

Alternatively, if you have a Subversion client installed, you can create a working copy of our custom peripherals on your PC.

1. Navigate to

   <xilinx_install_drive>:\EDK_user_repository\MyProcessorIPLib
   

2. Using Subversion, checkout these two URLs:

   http://warp.rice.edu/svn/WARP/PlatformSupport/CustomPeripherals/pcores/
   http://warp.rice.edu/svn/WARP/PlatformSupport/CustomPeripherals/drivers/
   

3. This will create pcores and drivers directories (if they don't already exist) containing the latest version of our peripherals.
4. To sync your working copy with the repository, run a Subversion update from these directories.

---

I'm trying to run an Ethernet demo. I get no response when I attempt to ping the board, despite everything else working, generating and downloading properly…

This is most likely due to the clock speed your PLB bus is running at. If you've included the 10/100 Ethernet core in your project and you review the hardware generation log -- you might notice an inconveniently small block of text telling you that the bus must run at a speed greater than 65mHz for 100 Mb Ethernet connections to work. You need to either connect the board to a 10 Mb Ethernet port or regenerate your hardware platform, selecting 100MHz for the bus speed in Base System Builder.

---

I'm attempting to run Xilkernel and/or LWIP. Despite having all of the necessary libraries added into my C-Code, the compiler still gives me errors for undefined functions that are Xilkernel/LWIP-based.

The problem may be more general and not just limited to Xilkernel or LWIP, but rather any libraries you've included in the software platform settings menu. The common problem is that the library paths have not been added to the compiler configuration menu. The fix is as follows:

1. Go to Applications Tab -> Expand Project View -> Right-click on "Compiler Options" and click "Set Compiler Options..."
2. Go to "Paths" Tab and then in the "Libraries to Link against(-l)" box, make sure this field contains a value like:

      xilkernel lwip4
   

You only need to list the libraries your code requires.

---

During Bitstream generation in XPS, the process gets stuck at "Using Options File: xflow.opt" in the output display.

This occurs when the user has insignificent read/write privelages on the computer.

---

I cannot get my personal peripheral repository to appear every time I open Xilinx Platform Studio

Move your peripheral repository to (or make sure it is in):

<xilinx_install_drive>:\EDK_user_repository\<folder of any name containing drivers and pcores>

---

The non-Xilinx-made peripherals in the WARP *.xbd file are not showing up in Base System Builder

It appears that this occurs when the EDK installation directory is not in C:\EDK. This is an issue currently being looked into. A temporary fix for this problem is to move custom made pcores into:

\\<EDK Installation Directory>\hw\XilinxProcessorIPLib\pcores\

and place the corresponding driver files in:

\\<EDK Installation Directory>\sw\XilinxProcessorIPLib\drivers\

---