Changes between Version 10 and Version 11 of FAQ


Ignore:
Timestamp:
Jun 24, 2006, 10:28:39 PM (18 years ago)
Author:
murphpo
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQ

    v10 v11  
    1010   mkdosfs -v -F 16 X:
    1111}}}
    12 
     12----
    1313=== 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... ===
    1414This 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.
    15 
     15----
    1616=== 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. ===
    1717
     
    2323}}}
    2424You only need to list the libraries your code requires.
    25 
     25----
    2626=== I'm not getting any serial port interaction. ===
    2727There are several problems that could cause this:
    2828 1. Incorrect cable type (this is most common): the WARP FPGA board's RS-232 interface is configured exactly like a PC. In order to connect it directly to another PC, you need a null modem cable or adapter (i.e. one which cross the Tx and Rx signals).
    2929 1. A system with a different hardware configuration has been redownloaded to WARP. In rare cases, the program running in the FPGA's PowerPC can lock up if a new system has been downloaded that has a different hardware configuration. The solution to this is to simply power cycle the board; be sure to leave the board off for a few seconds to allow the capacitors to discharge.
    30 
     30----
    3131=== During Bitstream generation in XPS, the process gets stuck at "Using Options File: xflow.opt" in the output display. ===
    3232This occurs when the user has insignificent read/write privelages on the computer.
    33 
     33----
    3434=== I cannot get my personal peripheral repository to appear every time I open Xilinx Platform Studio ===
    3535Move your peripheral repository to (or make sure it is in):