/**
@page LwIP_HTTP_Server_Raw LwIP HTTP Server Raw Application
@verbatim
******************************************************************************
* @file LwIP/LwIP_HTTP_Server_Raw/readme.txt
* @author MCD Application Team
* @brief Description of the LwIP http server Raw API.
******************************************************************************
* @attention
*
* Copyright (c) 2016 STMicroelectronics.
* All rights reserved.
*
* This software is licensed under terms that can be found in the LICENSE file
* in the root directory of this software component.
* If no LICENSE file comes with this software, it is provided AS-IS.
*
******************************************************************************
@endverbatim
@par Application Description
This application guides STM32Cube HAL API users to run a http server application
based on Raw API of LwIP TCP/IP stack
The communication is done with a web browser application in a remote PC.
this HTTP server contains three html pages:
+ the first page (home page) is static, it gives information about STM32F7
and LwIP stack.
+ the second page (LED control) allows to control the four LEDs located in
the STM32F769I_EVAL board
+ the third page (ADC conversion) is dynamically refreshed (every 1 s),
it shows the ADC3 channel 8 analog input converted value
If the LCD is used (#define USE_LCD in main.h), log messages will be displayed
to inform user about ethernet cable status and the IP address value, else this
will be ensured by LEDs:
+ LED1: ethernet cable is connected.
+ LED2: ethernet cable is not connected.
If a DHCP server is available, a dynamic IP address can be allocated by enabling
the DHCP process (#define LWIP_DHCP in lwipopts.h).
If a DHCP server is not available, after timeout connection, the device only gets a static
IP address(the switch from static to dynamic IP address is not available in this application).
Note: In this application the Ethernet Link ISR need the System tick interrupt
to configure the Ethernet MAC, so the Ethernet Link interrupt priority must be
set lower (numerically greater) than the Systick interrupt priority to ensure
that the System tick increments while executing the Ethernet Link ISR.
Note: By default, the Ethernet Half duplex mode is not supported in the
STM32F769I_EVAL board, for more information refer to the HAL_ETH_MspInit()
function in the ethernetif.c file
Note : ETH_MDIO signal is connected to PA2 which is shared with other signals like SAI2_SCKB.
By default on STM32F769I_EVAL board, PA2 is connected to SAI2_SCKB, so to connect PA2 to ETH_MDIO :
- jumper JP3 must be on the position 2-3
Note : ETH_MDC is connected to PC1 which is shared with other signals like SAI1_SDA.
By default on STM32F769I_EVAL board, PC1 is connected to SAI1_SDA, so to connect PC1 to ETH_MDC :
- jumper JP6 must be on the position 2-3
@note Care must be taken when using HAL_Delay(), this function provides accurate delay (in milliseconds)
based on variable incremented in SysTick ISR. This implies that if HAL_Delay() is called from
a peripheral ISR process, then the SysTick interrupt must have higher priority (numerically lower)
than the peripheral interrupt. Otherwise the caller ISR process will be blocked.
To change the SysTick interrupt priority you have to use HAL_NVIC_SetPriority() function.
@note The application needs to ensure that the SysTick time base is always set to 1 millisecond
to have correct HAL operation.
@note The STM32F7xx devices can reach a maximum clock frequency of 216MHz but as this application uses SDRAM,
the system clock is limited to 200MHz. Indeed proper functioning of the SDRAM is only guaranteed
at a maximum system clock frequency of 200MHz.
For more details about this application, refer to UM1713 "STM32Cube interfacing with LwIP and applications"
@par Keywords
Connectivity, LwIP, Ethernet, HTTP Server, Raw API, TCP/IP, DHCP
@Note<74>If the user code size exceeds the DTCM-RAM size or starts from internal cacheable memories (SRAM1 and SRAM2),that is shared between several processors,
<20><><A0><A0><A0>then it is highly recommended to enable the CPU cache and maintain its coherence at application level.
<0A><><A0><A0><A0><A0>The address and the size of cacheable buffers (shared between CPU and other masters) must be properly updated to be aligned to cache line size (32 bytes).
@Note It is recommended to enable the cache and maintain its coherence, but depending on the use case
<0A><><A0><A0><A0> It is also possible to configure the MPU as "Write through", to guarantee the write access coherence.
<0A><><A0><A0><A0><A0>In that case, the MPU must be configured as Cacheable/Bufferable/Not Shareable.
<0A><><A0><A0><A0><A0>Even though the user must manage the cache coherence for read accesses.
<0A><><A0><A0><A0><A0>Please refer to the AN4838 <20>Managing memory protection unit (MPU) in STM32 MCUs<55>
<0A><><A0><A0><A0><A0>Please refer to the AN4839 <20>Level 1 cache on STM32F7 Series<65>
@par Directory contents
- LwIP/LwIP_HTTP_Server_Raw/Inc/app_ethernet.h header of app_ethernet.c file
- LwIP/LwIP_HTTP_Server_Raw/Inc/ethernetif.h header for ethernetif.c file
- LwIP/LwIP_HTTP_Server_Raw/Inc/lcd_log_conf.h LCD Log configuration file
- LwIP/LwIP_HTTP_Server_Raw/Inc/stm32f7xx_hal_conf.h HAL configuration file
- LwIP/LwIP_HTTP_Server_Raw/Inc/stm32f7xx_it.h STM32 interrupt handlers header file
- LwIP/LwIP_HTTP_Server_Raw/Inc/main.h Main program header file
- LwIP/LwIP_HTTP_Server_Raw/Inc/lwipopts.h LwIP stack configuration options
- LwIP/LwIP_HTTP_Server_Raw/Src/app_ethernet.c Ethernet specific module
- LwIP/LwIP_HTTP_Server_Raw/Src/stm32f7xx_it.c STM32 interrupt handlers
- LwIP/LwIP_HTTP_Server_Raw/Src/main.c Main program
- LwIP/LwIP_HTTP_Server_Raw/Src/system_stm32f7xx.c STM32F7xx system clock configuration file
- LwIP/LwIP_HTTP_Server_Raw/Src/ethernetif.c Interfacing LwIP to ETH driver
- LwIP/LwIP_HTTP_Server_Raw/Src/httpd_cgi_ssi.c Webserver SSI and CGI handlers
- LwIP/LwIP_HTTP_Server_Raw/Src/fsdata_custom.c ROM filesystem data (html pages)
@par Hardware and Software environment
- This application runs on STM32F767xx/STM32F769xx/STM32F777xx/STM32F779xx devices.
- This application has been tested with the following environments:
- STM32F769I_EVAL board
- Http clients: Firefox Mozilla (v24) or Microsoft Internet Explorer (v8 and later)
- DHCP server: PC utility TFTPD32 (http://tftpd32.jounin.net/) is used as a DHCP server
- STM32F769I_EVAL Set-up
- Connect the eval board to remote PC (through a crossover ethernet cable)
or to your local network (through a straight ethernet cable)
- jumper JP3 must be on the position 2-3 (ETH signal)
- jumper JP4 must be on the position 2-3 (MII_MDIO signal)
- jumper JP6 must be on the position 2-3 (ETH signal)
- jumper JP8 must be on the position 1-2 (MII_MDC signal)
- jumper JP12 must be on the position 1-2 (ETH signal)
- Remote PC Set-up
- Configure a static IP address for your remote PC
for example 192.168.0.11
@par How to use it ?
In order to make the program work, you must do the following :
- Open your preferred toolchain
- Rebuild all files and load your image into target memory
- Run the application
767d083e20