Changes between Version 7 and Version 8 of FAQ

Timestamp:

Jun 16, 2006, 1:56:19 AM (18 years ago)

Author:

snovich

Comment:

--

FAQ

@@ -17 +17 @@
 
 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 that you add in
-"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.
+ 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:
+{{{
+   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.
 
 === 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
-2. 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.
-3. 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. 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.