Projects/Webserver/Webserver.txt

   1 /** \file
   2  *
   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.
   5  */
   6
   7 /** \mainpage uIP Powered Webserver Project
   8  *
   9  *  \section SSec_Compat Project Compatibility:
  10  *
  11  *  The following list indicates what microcontrollers are compatible with this project.
  12  *
  13  *  - Series 7 USB AVRs
  14  *
  15  *  \section SSec_Info USB Information:
  16  *
  17  *  The following table gives a rundown of the USB utilization of this project.
  18  *
  19  *  <table>
  20  *   <tr>
  21  *    <td><b>USB Mode:</b></td>
  22  *    <td>Dual Mode Host/Device</td>
  23  *   </tr>
  24  *   <tr>
  25  *    <td><b>USB Class:</b></td>
  26  *    <td>Communications Device Class (CDC) \n
  27  *        Mass Storage Device</td>
  28  *   </tr>
  29  *   <tr>
  30  *    <td><b>USB Subclass:</b></td>
  31  *    <td>Remote NDIS (Microsoft Proprietary CDC Class Networking Standard) \n
  32  *        Bulk-Only Transport</td>
  33  *   </tr>
  34  *   <tr>
  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>
  41  *   </tr>
  42  *   <tr>
  43  *    <td><b>Usable Speeds:</b></td>
  44  *    <td>Full Speed Mode</td>
  45  *   </tr>
  46  *  </table>
  47  *
  48  *  \section SSec_Description Project Description:
  49  *
  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
  53  *  network device.
  54  *
  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 the maximum URI length (\see \ref SSec_Options).
  59  *
  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 and TELNET
  62  *  connections on port 23. The device IP, netmask and default gateway IP must be set to values appropriate for the RNDIS
  63  *  device being used for this project to work if the DHCP client is disabled (see \ref SSec_Options) - otherwise, the device
  64  *  will query the network's DHCP server for these parameters automatically.
  65  *
  66  *  When properly configured, the webserver can be accessed from any HTTP webrowser by typing in the device's statically or
  67  *  dynamically allocated IP address. The TELNET client can be accessed via any network socket app by connecting to the device
  68  *  on port 23 on the device's statically or dynamically allocated IP address.
  69  *
  70  *  \section SSec_Options Project Options
  71  *
  72  *  The following defines can be found in this project, which can control the project behaviour when defined, or changed in value.
  73  *
  74  *  <table>
  75  *   <tr>
  76  *    <td><b>Define Name:</b></td>
  77  *    <td><b>Location:</b></td>
  78  *    <td><b>Description:</b></td>
  79  *   </tr>
  80  *   <tr>
  81  *    <td>ENABLE_TELNET_SERVER</td>
  82  *    <td>Makefile CDEFS</td>
  83  *    <td>When defined, this enables the TELNET server in addition to the HTTP webserver, which listens for incomming connections
  84  *        and processes user commands.</td>
  85  *   </tr>
  86  *   <tr>
  87  *    <td>ENABLE_DHCP_CLIENT</td>
  88  *    <td>Makefile CDEFS</td>
  89  *    <td>When defined, this enables the DHCP client for dynamic IP allocation of the network settings from a DHCP server.</td>
  90  *   </tr>
  91  *   <tr>
  92  *    <td>DEVICE_IP_ADDRESS</td>
  93  *    <td>Lib/uIPManagement.h</td>
  94  *    <td>IP address that the webserver should use when connected to a RNDIS device (when ENABLE_DHCP_CLIENT is not defined).</td>
  95  *   </tr>
  96  *   <tr>
  97  *    <td>DEVICE_NETMASK</td>
  98  *    <td>Lib/uIPManagement.h</td>
  99  *    <td>Netmask that the webserver should use when connected to a RNDIS device (when ENABLE_DHCP_CLIENT is not defined).</td>
 100  *   </tr>
 101  *   <tr>
 102  *    <td>DEVICE_GATEWAY</td>
 103  *    <td>Lib/uIPManagement.h</td>
 104  *    <td>Default routing gateway that the webserver should use when connected to a RNDIS device (when ENABLE_DHCP_CLIENT
 105  *        is not defined).</td>
 106  *   </tr>
 107  *   <tr>
 108  *    <td>MAX_URI_LENGTH</td>
 109  *    <td>Makefile CDEFS</td>
 110  *    <td>Maximum length of a URI for the Webserver. This is the maximum file path, including subdirectories and seperators.</td>
 111  *   </tr>
 112  *  </table>
 113  */