Changes between Version 8 and Version 9 of FAQ

Timestamp:

Jun 19, 2006, 4:52:49 PM (18 years ago)

Author:

murphpo

Comment:

--

FAQ

@@ -11 +11 @@
 }}}
 
-=== 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 bus is running at. If you've included the 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 ethernet transfers to work.
+=== 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. ===
@@ -18 +18 @@
 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..."
- 1. Go to "Paths" Tab and then in the "Libraries to Link against(-l)" box, make sure that you add in:
+ 1. Go to "Paths" Tab and then in the "Libraries to Link against(-l)" box, make sure this field contains a value like:
 {{{
    xilkernel lwip4
 }}} 
-or that this phrase already exists. It's really just the names for each of these special libraries to be included separated by spaces.
+You only need to list the libraries your code requires.
 
 === I'm not getting any serial port interaction. ===
 There are several problems that could cause this:
- 1. The wire shorting the pins over the serial port on the WARP main board has become loose/disconnected
- 1. Incorrect cable type (this is most common): Standard serial cables DO NOT work with the WARP serial interface. A little DB9 (Null Modem) type serial cable is required. The quick fix for this is to open a standard serial cable and flip and resolder the rx/tx pin mapping -- pins 2 & 3. In a normal serial cable, pin 2 maps to pin 2 and the same for pin 3. These must be remapped so 2 maps to 3 and 3 maps to 2.
- 1. A system with a different hardware configuration has been redownloaded to WARP. In rare cases, the FPGA can lock up if a new system has been downloaded that has a different hardware configuration. The solution to this is to simply turn on and off the system power, allowing ample time for the capacitors on the board to drain.
-
+ 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).
+ 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.