/* | |
FreeRTOS V7.5.3 - Copyright (C) 2013 Real Time Engineers Ltd. | |
All rights reserved | |
VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION. | |
*************************************************************************** | |
* * | |
* FreeRTOS provides completely free yet professionally developed, * | |
* robust, strictly quality controlled, supported, and cross * | |
* platform software that has become a de facto standard. * | |
* * | |
* Help yourself get started quickly and support the FreeRTOS * | |
* project by purchasing a FreeRTOS tutorial book, reference * | |
* manual, or both from: http://www.FreeRTOS.org/Documentation * | |
* * | |
* Thank you! * | |
* * | |
*************************************************************************** | |
This file is part of the FreeRTOS distribution. | |
FreeRTOS is free software; you can redistribute it and/or modify it under | |
the terms of the GNU General Public License (version 2) as published by the | |
Free Software Foundation >>!AND MODIFIED BY!<< the FreeRTOS exception. | |
>>! NOTE: The modification to the GPL is included to allow you to distribute | |
>>! a combined work that includes FreeRTOS without being obliged to provide | |
>>! the source code for proprietary components outside of the FreeRTOS | |
>>! kernel. | |
FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY | |
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS | |
FOR A PARTICULAR PURPOSE. Full license text is available from the following | |
link: http://www.freertos.org/a00114.html | |
1 tab == 4 spaces! | |
*************************************************************************** | |
* * | |
* Having a problem? Start by reading the FAQ "My application does * | |
* not run, what could be wrong?" * | |
* * | |
* http://www.FreeRTOS.org/FAQHelp.html * | |
* * | |
*************************************************************************** | |
http://www.FreeRTOS.org - Documentation, books, training, latest versions, | |
license and Real Time Engineers Ltd. contact details. | |
http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products, | |
including FreeRTOS+Trace - an indispensable productivity tool, a DOS | |
compatible FAT file system, and our tiny thread aware UDP/IP stack. | |
http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High | |
Integrity Systems to sell under the OpenRTOS brand. Low cost OpenRTOS | |
licenses offer ticketed support, indemnification and middleware. | |
http://www.SafeRTOS.com - High Integrity Systems also provide a safety | |
engineered and independently SIL3 certified version for use in safety and | |
mission critical applications that require provable dependability. | |
1 tab == 4 spaces! | |
*/ | |
/****************************************************************************** | |
* NOTE 1: This project provides two demo applications. A simple blinky style | |
* project, and a more comprehensive test and demo application. The | |
* configCREATE_SIMPLE_BLINKY_DEMO_ONLY setting in FreeRTOSConifg.h is used to | |
* select between the two. See the notes on using | |
* configCREATE_SIMPLE_BLINKY_DEMO_ONLY in main.c. This file implements the | |
* comprehensive test and demo version. | |
* | |
* NOTE 2: This file only contains the source code that is specific to the | |
* full demo. Generic functions, such FreeRTOS hook functions, and functions | |
* required to configure the hardware, are defined in main.c. | |
****************************************************************************** | |
* | |
* main_full() creates all the demo application tasks and a software timer, then | |
* starts the scheduler. The web documentation provides more details of the | |
* standard demo application tasks, which provide no particular functionality, | |
* but do provide a good example of how to use the FreeRTOS API. | |
* | |
* In addition to the standard demo tasks, the following tasks and tests are | |
* defined and/or created within this file: | |
* | |
* "Check" timer - The check software timer period is initially set to three | |
* seconds. The callback function associated with the check software timer | |
* checks that all the standard demo tasks are not only still executing, but | |
* are executing without reporting any errors. If the check software timer | |
* discovers that a task has either stalled, or reported an error, then it | |
* changes its own execution period from the initial three seconds, to just | |
* 200ms. The check software timer callback function also toggles the green | |
* LED each time it is called. This provides a visual indication of the system | |
* status: If the green LED toggles every three seconds, then no issues have | |
* been discovered. If the green LED toggles every 200ms, then an issue has | |
* been discovered with at least one task. | |
* | |
* FreeRTOS+CLI command console. The command console is access through UART0 | |
* using 115200 baud and the Microsemi MSS UART drivers. Type "help" to see a | |
* list of registered commands, which include some basic file system commands | |
* (see FreeRTOS+FAT SL comments below). The FreeRTOS+CLI license is different | |
* to the FreeRTOS license, see http://www.FreeRTOS.org/cli for license and | |
* usage details. | |
* | |
* FreeRTOS+FAT SL. FreeRTOS+FAT SL is demonstrated using a RAM disk. [At the | |
* time of writing] The functionality of the file system demo is identical to | |
* the functionality of the FreeRTOS Win32 simulator file system demo with the | |
* command console being accessed via the UART (as described above) instead of | |
* a network terminal. The FreeRTOS+FAT SL license is different to the FreeRTOS | |
* license, see http://www.FreeRTOS.org/fat_sl for license and usage details, | |
* and a description of the file system demo functionality. | |
* | |
* See the documentation page for this demo on the FreeRTOS.org web site for | |
* full information, including hardware setup requirements. | |
*/ | |
/* Standard includes. */ | |
#include <stdio.h> | |
/* Kernel includes. */ | |
#include "FreeRTOS.h" | |
#include "task.h" | |
#include "timers.h" | |
#include "queue.h" | |
/* Standard demo application includes. */ | |
#include "integer.h" | |
#include "PollQ.h" | |
#include "semtest.h" | |
#include "dynamic.h" | |
#include "BlockQ.h" | |
#include "blocktim.h" | |
#include "countsem.h" | |
#include "GenQTest.h" | |
#include "recmutex.h" | |
#include "death.h" | |
#include "flash_timer.h" | |
#include "partest.h" | |
#include "UARTCommandConsole.h" | |
/* Priorities for the demo application tasks. */ | |
#define mainQUEUE_POLL_PRIORITY ( tskIDLE_PRIORITY + 2UL ) | |
#define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1UL ) | |
#define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2UL ) | |
#define mainCREATOR_TASK_PRIORITY ( tskIDLE_PRIORITY + 3UL ) | |
#define mainFLOP_TASK_PRIORITY ( tskIDLE_PRIORITY ) | |
/* A block time of zero simply means "don't block". */ | |
#define mainDONT_BLOCK ( 0UL ) | |
/* The period after which the check timer will expire, in ms, provided no errors | |
have been reported by any of the standard demo tasks. ms are converted to the | |
equivalent in ticks using the portTICK_RATE_MS constant. */ | |
#define mainCHECK_TIMER_PERIOD_MS ( 3000UL / portTICK_RATE_MS ) | |
/* The period at which the check timer will expire, in ms, if an error has been | |
reported in one of the standard demo tasks. ms are converted to the equivalent | |
in ticks using the portTICK_RATE_MS constant. */ | |
#define mainERROR_CHECK_TIMER_PERIOD_MS ( 200UL / portTICK_RATE_MS ) | |
/* The standard demo flash timers can be used to flash any number of LEDs. In | |
this case, because only three LEDs are available, and one is in use by the | |
check timer, only two are used by the flash timers. */ | |
#define mainNUMBER_OF_FLASH_TIMERS_LEDS ( 1 ) | |
/* The LED toggled by the check timer. The first two LEDs are toggle by the | |
standard demo flash timers. */ | |
#define mainCHECK_LED ( 1 ) | |
/* The size of the stack and the priority used by the UART command console | |
task. */ | |
#define mainUART_COMMAND_CONSOLE_STACK_SIZE ( configMINIMAL_STACK_SIZE * 2 ) | |
#define mainUART_COMMAND_CONSOLE_TASK_PRIORITY ( tskIDLE_PRIORITY ) | |
/*-----------------------------------------------------------*/ | |
/* | |
* The check timer callback function, as described at the top of this file. | |
*/ | |
static void prvCheckTimerCallback( xTimerHandle xTimer ); | |
/* | |
* Register commands that can be used with FreeRTOS+CLI. The commands are | |
* defined in CLI-Commands.c and File-Related-CLI-Command.c respectively. | |
*/ | |
extern void vRegisterSampleCLICommands( void ); | |
extern void vRegisterFileSystemCLICommands( void ); | |
/* Prepare to run the full demo: Configure the IO, register the CLI | |
* commands, and depending on configuration, generate a set of sample files on | |
* a RAM disk. | |
*/ | |
static void prvPrepareForFullDemo( void ); | |
/* | |
* Creates and verifies different files on the volume, demonstrating the use of | |
* various different API functions. | |
*/ | |
extern void vCreateAndVerifySampleFiles( void ); | |
/*-----------------------------------------------------------*/ | |
void main_full( void ) | |
{ | |
xTimerHandle xCheckTimer = NULL; | |
/* Prepare to run the full demo: Configure the IO, register the CLI | |
commands, and depending on configuration, generate a set of sample files on | |
a RAM disk. */ | |
prvPrepareForFullDemo(); | |
/* Start all the other standard demo/test tasks. The have not particular | |
functionality, but do demonstrate how to use the FreeRTOS API and test the | |
kernel port. */ | |
vStartIntegerMathTasks( tskIDLE_PRIORITY ); | |
vStartDynamicPriorityTasks(); | |
vStartBlockingQueueTasks( mainBLOCK_Q_PRIORITY ); | |
vCreateBlockTimeTasks(); | |
vStartCountingSemaphoreTasks(); | |
vStartGenericQueueTasks( tskIDLE_PRIORITY ); | |
vStartRecursiveMutexTasks(); | |
vStartPolledQueueTasks( mainQUEUE_POLL_PRIORITY ); | |
vStartSemaphoreTasks( mainSEM_TEST_PRIORITY ); | |
vStartLEDFlashTimers( mainNUMBER_OF_FLASH_TIMERS_LEDS ); | |
/* Start the tasks that implements the command console on the UART, as | |
described above. */ | |
vUARTCommandConsoleStart( mainUART_COMMAND_CONSOLE_STACK_SIZE, mainUART_COMMAND_CONSOLE_TASK_PRIORITY ); | |
/* Create the software timer that performs the 'check' functionality, | |
as described at the top of this file. */ | |
xCheckTimer = xTimerCreate( ( const signed char * ) "CheckTimer",/* A text name, purely to help debugging. */ | |
( mainCHECK_TIMER_PERIOD_MS ), /* The timer period, in this case 3000ms (3s). */ | |
pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */ | |
( void * ) 0, /* The ID is not used, so can be set to anything. */ | |
prvCheckTimerCallback /* The callback function that inspects the status of all the other tasks. */ | |
); | |
if( xCheckTimer != NULL ) | |
{ | |
xTimerStart( xCheckTimer, mainDONT_BLOCK ); | |
} | |
/* The set of tasks created by the following function call have to be | |
created last as they keep account of the number of tasks they expect to see | |
running. */ | |
vCreateSuicidalTasks( mainCREATOR_TASK_PRIORITY ); | |
/* Start the scheduler. */ | |
vTaskStartScheduler(); | |
/* If all is well, the scheduler will now be running, and the following line | |
will never be reached. If the following line does execute, then there was | |
insufficient FreeRTOS heap memory available for the idle and/or timer tasks | |
to be created. See the memory management section on the FreeRTOS web site | |
for more details. */ | |
for( ;; ); | |
} | |
/*-----------------------------------------------------------*/ | |
static void prvCheckTimerCallback( xTimerHandle xTimer ) | |
{ | |
static long lChangedTimerPeriodAlready = pdFALSE; | |
unsigned long ulErrorFound = pdFALSE; | |
/* Check all the demo tasks (other than the flash tasks) to ensure | |
they are all still running, and that none have detected an error. */ | |
if( xAreIntegerMathsTaskStillRunning() != pdTRUE ) | |
{ | |
ulErrorFound = pdTRUE; | |
} | |
if( xAreDynamicPriorityTasksStillRunning() != pdTRUE ) | |
{ | |
ulErrorFound = pdTRUE; | |
} | |
if( xAreBlockingQueuesStillRunning() != pdTRUE ) | |
{ | |
ulErrorFound = pdTRUE; | |
} | |
if ( xAreBlockTimeTestTasksStillRunning() != pdTRUE ) | |
{ | |
ulErrorFound = pdTRUE; | |
} | |
if ( xAreGenericQueueTasksStillRunning() != pdTRUE ) | |
{ | |
ulErrorFound = pdTRUE; | |
} | |
if ( xAreRecursiveMutexTasksStillRunning() != pdTRUE ) | |
{ | |
ulErrorFound = pdTRUE; | |
} | |
if( xIsCreateTaskStillRunning() != pdTRUE ) | |
{ | |
ulErrorFound = pdTRUE; | |
} | |
if( xArePollingQueuesStillRunning() != pdTRUE ) | |
{ | |
ulErrorFound = pdTRUE; | |
} | |
if( xAreSemaphoreTasksStillRunning() != pdTRUE ) | |
{ | |
ulErrorFound = pdTRUE; | |
} | |
/* Toggle the check LED to give an indication of the system status. If | |
the LED toggles every mainCHECK_TIMER_PERIOD_MS milliseconds then | |
everything is ok. A faster toggle indicates an error. */ | |
vParTestToggleLED( mainCHECK_LED ); | |
/* Have any errors been latch in ulErrorFound? If so, shorten the | |
period of the check timer to mainERROR_CHECK_TIMER_PERIOD_MS milliseconds. | |
This will result in an increase in the rate at which mainCHECK_LED | |
toggles. */ | |
if( ulErrorFound != pdFALSE ) | |
{ | |
if( lChangedTimerPeriodAlready == pdFALSE ) | |
{ | |
lChangedTimerPeriodAlready = pdTRUE; | |
/* This call to xTimerChangePeriod() uses a zero block time. | |
Functions called from inside of a timer callback function must | |
*never* attempt to block. */ | |
xTimerChangePeriod( xTimer, ( mainERROR_CHECK_TIMER_PERIOD_MS ), mainDONT_BLOCK ); | |
} | |
} | |
} | |
/*-----------------------------------------------------------*/ | |
static void prvPrepareForFullDemo( void ) | |
{ | |
/* If the file system is only going to be accessed from one task then | |
F_FS_THREAD_AWARE can be set to 0 and the set of example files are created | |
before the RTOS scheduler is started. If the file system is going to be | |
access from more than one task then F_FS_THREAD_AWARE must be set to 1 and | |
the set of sample files are created from the idle task hook function | |
vApplicationIdleHook() - which is defined in this file. */ | |
#if F_FS_THREAD_AWARE == 0 | |
{ | |
/* Initialise the drive and file system, then create a few example | |
files. The output from this function just goes to the stdout window, | |
allowing the output to be viewed when the UDP command console is not | |
connected. */ | |
vCreateAndVerifySampleFiles(); | |
} | |
#endif | |
/* Register both the standard and file system related CLI commands. */ | |
vRegisterSampleCLICommands(); | |
vRegisterFileSystemCLICommands(); | |
} |