The demo presented on this page uses:
FreeRTOS has made some modifications to the uIP stack since this demo was created. See the Embedded Ethernet Examples List page for more information.
The FreeRTOS ARM Cortex-M3 port includes a full interrupt nesting model. Interrupt priorities must be set in accordance with the instructions on the Customisation page for correct operation.
IMPORTANT! Notes on using the ST ARM Cortex-M3 Web Server DemoPlease read all the following points before using this RTOS port.
My application does not run, what could be wrong?
Source Code OrganisationThe CrossWorks workspace for the STM32F107 demo is located in the FreeRTOS/Demo/CORTEX_STM32F107_GCC_Rowley directory.
The FreeRTOS zip file download contains the files for all the ports and demo application projects. It therefore contains many more files than used by this demo. See the Source Code Organization section for a description of the downloaded files and information on creating a new project.
The Demo Application
web server configurationEnsure that jumper JP4 is set so that JP4 pins 1 and 2 are shorted - this routes the output of the external 25MHz crystal to the PHY. Jumpers JP3, JP11, JP12 and JP13 need to be shorting pins 2 and 3, which should be the default setting.
Connect the STM3210C evaluation board to a computer running a web browser either directly using a point to point (crossover) cable, or via an Ethernet switch using a standard Ethernet cable.
The IP address used by the demo is set by the constants configIP_ADDR0 to configIP_ADDR3 within the file FreeRTOS/Demo/CORTEX_STM32F107_GCC_Rowley/FreeRTOSConfig.h. The MAC address and net mask are configured within the same header file.
The IP addresses used by the web browser computer and the STM32 development board must be compatible. This can be ensured by making the first three octets of both IP addresses identical. For example, if the web browser computer uses IP address 192.168.100.1, then the development board can be given any address in the range 192.168.100.2 to 192.168.100.254 (barring any addresses already present on the network).
Building and executing the demo application
The ST peripheral libraryPlease note that the peripheral library utilised by the demo application is neither re-entrant nor event driven.
During its initialisation, the demo application accesses IO port configuration from within more than one task. This raises the possibility of problems related to re-entrancy (or lack of it). No attempt is made to guard against this. If this proves problematic then place the initialisation library calls inside critical sections.
The LCD driver uses a polled SPI interface. Currently the LCD gatekeeper task is configured to execute at a medium priority - resulting in lower priority tasks not getting any processing time while the SPI interface is being polled. The task can be configured to execute at the lowest priority, but this results in visibly slower LCD updates. A much more efficient solution would be to re-implement the driver to make use of the DMA and be event driven.
FunctionalityThe demo application creates 30 tasks prior to starting the RTOS scheduler. These tasks consist predominantly of the standard demo application tasks (see the demo application section for details of the individual tasks). Their only purpose is to test the RTOS kernel port and provide a demonstration of how to use the various API functions.
The following tasks and tests are created in addition to the standard demo tasks:
When executing correctly the demo application will behave as follows:
Served Web PagesThe top of each served page includes a menu containing a link to every other page.
The served RTOS stats page showing status information on each task in the system.
The served run time stats page showing the processor utilisation of each task.
The served IO page
The IO page provides a simple interface that permits data to be sent to LED 4 and LCD on the development board.
The check box permits the state of LED 4 to be set and queried. The text box can be used to write a message to the LCD, but does not query the text currently being display. Changes are sent to the target hardware by clicking the "Update IO" button.
The TCP Stats and Connections pages display run time networking information.
RTOS port specific configurationConfiguration items specific to these demos are contained in FreeRTOS/Demo/CORTEX_STM32F107_GCC_Rowley/FreeRTOSConfig.h. The constants defined in this file can be edited to suit your application. In particular -
The lowest priority on a ARM Cortex-M3 core is in fact 255 - however different ARM Cortex-M3 vendors implement a different number of priority bits and supply library functions that expect priorities to be specified in different ways. Use the supplied examples as a reference.
Each port #defines 'BaseType_t' to equal the most efficient data type for that processor. This port defines BaseType_t to be of type long.
Note that vPortEndScheduler() has not been implemented.
Interrupt service routinesIn the demo application the vector table remains in flash.
Unlike most ports, interrupt service routines that cause a context switch have no special requirements and can be written as per the compiler documentation. The macro portEND_SWITCHING_ISR() can be used to request a context switch from within an ISR. An example interrupt service routine called vMAC_ISR() is provided in FreeRTOS/Demo/CORTEX_STM32F107_GCC_Rowley/webserver/emac.c. This should be used as a reference example.
Note that portEND_SWITCHING_ISR() will leave interrupts enabled.
Switching between the pre-emptive and co-operative RTOS kernelsSet the definition configUSE_PREEMPTION within FreeRTOS/Demo/CORTEX_STM32F107_GCC_Rowley/FreeRTOSConfig.h to 1 to use pre-emption or 0 to use co-operative.
Compiler optionsAs with all the ports, it is essential that the correct compiler options are used. The best way to ensure this is to base your application on the provided demo application files.
Memory allocationSource/Portable/MemMang/heap_2.c is included in the ARM Cortex-M3 demo application project to provide the memory allocation required by the RTOS kernel. Please refer to the Memory Management section of the API documentation for full information.
Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.