3 * This file contains special DoxyGen information for the generation of the main page and other special
4 * documentation pages. It is not a project source file.
7 /** \mainpage uIP Powered Webserver Project
9 * \section SSec_Compat Project Compatibility:
11 * The following list indicates what microcontrollers are compatible with this project.
15 * \section SSec_Info USB Information:
17 * The following table gives a rundown of the USB utilization of this project.
21 * <td><b>USB Mode:</b></td>
22 * <td>Dual Mode Host/Device</td>
25 * <td><b>USB Class:</b></td>
26 * <td>Communications Device Class (CDC) \n
27 * Mass Storage Device</td>
30 * <td><b>USB Subclass:</b></td>
31 * <td>Remote NDIS (Microsoft Proprietary CDC Class Networking Standard) \n
32 * Bulk-Only Transport</td>
35 * <td><b>Relevant Standards:</b></td>
36 * <td>Microsoft RNDIS Specification \n
37 * USBIF Mass Storage Standard \n
38 * USB Bulk-Only Transport Standard \n
39 * SCSI Primary Commands Specification \n
40 * SCSI Block Commands Specification</td>
43 * <td><b>Usable Speeds:</b></td>
44 * <td>Full Speed Mode</td>
48 * \section SSec_Description Project Description:
50 * Simple HTTP webserver project. This project combines the LUFA library with the uIP TCP/IP full network stack and FatFS
51 * library to create a RNDIS host capable of serving out HTTP webpages to multiple hosts simultaneously. This project
52 * demonstrates how the libraries can be combined into a robust network enabled application, with the addition of a RNDIS
55 * To use this project, plug the USB AVR into a computer, so that it enumerates as a standard Mass Storage device. Load
56 * HTML files onto the disk, so that they can be served out to clients -- the default file to serve should be called
57 * <i>index.htm</i>. Filenames must be in 8.3 format for them to be retrieved correctly by the webserver, and the total
58 * requested file path must be equal to or less than 50 characters.
60 * When attached to a RNDIS class device, such as a USB (desktop) modem, the system will enumerate the device, set the
61 * appropriate parameters needed for connectivity and begin listening for new HTTP connections on port 80. The device IP,
62 * netmask and default gateway IP must be set to values appropriate for the RNDIS device being used for this project to
63 * work, if the DHCP client is disabled (see \ref SSec_Options).
65 * When properly configured, the webserver can be accessed from any HTTP webrowser by typing in the device's static or
66 * dynamically allocated IP address.
68 * \section SSec_Options Project Options
70 * The following defines can be found in this project, which can control the project behaviour when defined, or changed in value.
74 * <td><b>Define Name:</b></td>
75 * <td><b>Location:</b></td>
76 * <td><b>Description:</b></td>
79 * <td>ENABLE_DHCP=<i>x</i></td>
80 * <td>Makefile CDEFS</td>
81 * <td>When set to 1, this enables the DHCP client for dynamic IP allocation of the network settings from a DHCP server.
82 * To disable DHCP and use the fixed address settings set elsewhere, set this to zero (do not undefine it).</td>
85 * <td>DEVICE_IP_ADDRESS</td>
86 * <td>Lib/uIPManagement.h</td>
87 * <td>IP address that the webserver should use when connected to a RNDIS device (when ENABLE_DHCP is not defined).</td>
90 * <td>DEVICE_NETMASK</td>
91 * <td>Lib/uIPManagement.h</td>
92 * <td>Netmask that the webserver should use when connected to a RNDIS device (when ENABLE_DHCP is not defined).</td>
95 * <td>DEVICE_GATEWAY</td>
96 * <td>Lib/uIPManagement.h</td>
97 * <td>Default routing gateway that the webserver should use when connected to a RNDIS device (when ENABLE_DHCP
98 * is not defined).</td>