/*\r
- FreeRTOS V7.1.1 - Copyright (C) 2012 Real Time Engineers Ltd.\r
- \r
-\r
- ***************************************************************************\r
- * *\r
- * FreeRTOS tutorial books are available in pdf and paperback. *\r
- * Complete, revised, and edited pdf reference manuals are also *\r
- * available. *\r
- * *\r
- * Purchasing FreeRTOS documentation will not only help you, by *\r
- * ensuring you get running as quickly as possible and with an *\r
- * in-depth knowledge of how to use FreeRTOS, it will also help *\r
- * the FreeRTOS project to continue with its mission of providing *\r
- * professional grade, cross platform, de facto standard solutions *\r
- * for microcontrollers - completely free of charge! *\r
- * *\r
- * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *\r
- * *\r
- * Thank you for using FreeRTOS, and thank you for your support! *\r
- * *\r
- ***************************************************************************\r
+ FreeRTOS V9.0.0rc2 - Copyright (C) 2016 Real Time Engineers Ltd.\r
+ All rights reserved\r
\r
+ VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.\r
\r
This file is part of the FreeRTOS distribution.\r
\r
FreeRTOS is free software; you can redistribute it and/or modify it under\r
the terms of the GNU General Public License (version 2) as published by the\r
- Free Software Foundation AND MODIFIED BY the FreeRTOS exception.\r
- >>>NOTE<<< The modification to the GPL is included to allow you to\r
- distribute a combined work that includes FreeRTOS without being obliged to\r
- provide the source code for proprietary components outside of the FreeRTOS\r
- kernel. FreeRTOS is distributed in the hope that it will be useful, but\r
- WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY\r
- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for\r
- more details. You should have received a copy of the GNU General Public\r
- License and the FreeRTOS license exception along with FreeRTOS; if not it\r
- can be viewed here: http://www.freertos.org/a00114.html and also obtained\r
- by writing to Richard Barry, contact details for whom are available on the\r
- FreeRTOS WEB site.\r
+ Free Software Foundation >>>> AND MODIFIED BY <<<< the FreeRTOS exception.\r
+\r
+ ***************************************************************************\r
+ >>! NOTE: The modification to the GPL is included to allow you to !<<\r
+ >>! distribute a combined work that includes FreeRTOS without being !<<\r
+ >>! obliged to provide the source code for proprietary components !<<\r
+ >>! outside of the FreeRTOS kernel. !<<\r
+ ***************************************************************************\r
+\r
+ FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY\r
+ WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS\r
+ FOR A PARTICULAR PURPOSE. Full license text is available on the following\r
+ link: http://www.freertos.org/a00114.html\r
\r
- 1 tab == 4 spaces!\r
- \r
***************************************************************************\r
* *\r
- * Having a problem? Start by reading the FAQ "My application does *\r
- * not run, what could be wrong? *\r
+ * FreeRTOS provides completely free yet professionally developed, *\r
+ * robust, strictly quality controlled, supported, and cross *\r
+ * platform software that is more than just the market leader, it *\r
+ * is the industry's de facto standard. *\r
* *\r
- * http://www.FreeRTOS.org/FAQHelp.html *\r
+ * Help yourself get started quickly while simultaneously helping *\r
+ * to support the FreeRTOS project by purchasing a FreeRTOS *\r
+ * tutorial book, reference manual, or both: *\r
+ * http://www.FreeRTOS.org/Documentation *\r
* *\r
***************************************************************************\r
\r
- \r
- http://www.FreeRTOS.org - Documentation, training, latest information, \r
- license and contact details.\r
- \r
+ http://www.FreeRTOS.org/FAQHelp.html - Having a problem? Start by reading\r
+ the FAQ page "My application does not run, what could be wrong?". Have you\r
+ defined configASSERT()?\r
+\r
+ http://www.FreeRTOS.org/support - In return for receiving this top quality\r
+ embedded software for free we request you assist our global community by\r
+ participating in the support forum.\r
+\r
+ http://www.FreeRTOS.org/training - Investing in training allows your team to\r
+ be as productive as possible as early as possible. Now you can receive\r
+ FreeRTOS training directly from Richard Barry, CEO of Real Time Engineers\r
+ Ltd, and the world's leading authority on the world's leading RTOS.\r
+\r
http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,\r
- including FreeRTOS+Trace - an indispensable productivity tool.\r
+ including FreeRTOS+Trace - an indispensable productivity tool, a DOS\r
+ compatible FAT file system, and our tiny thread aware UDP/IP stack.\r
+\r
+ http://www.FreeRTOS.org/labs - Where new FreeRTOS products go to incubate.\r
+ Come and try FreeRTOS+TCP, our new open source TCP/IP stack for FreeRTOS.\r
+\r
+ http://www.OpenRTOS.com - Real Time Engineers ltd. license FreeRTOS to High\r
+ Integrity Systems ltd. to sell under the OpenRTOS brand. Low cost OpenRTOS\r
+ licenses offer ticketed support, indemnification and commercial middleware.\r
\r
- Real Time Engineers ltd license FreeRTOS to High Integrity Systems, who sell \r
- the code with commercial support, indemnification, and middleware, under \r
- the OpenRTOS brand: http://www.OpenRTOS.com. High Integrity Systems also\r
- provide a safety engineered and independently SIL3 certified version under \r
- the SafeRTOS brand: http://www.SafeRTOS.com.\r
+ http://www.SafeRTOS.com - High Integrity Systems also provide a safety\r
+ engineered and independently SIL3 certified version for use in safety and\r
+ mission critical applications that require provable dependability.\r
+\r
+ 1 tab == 4 spaces!\r
*/\r
\r
/*\r
* Creates all the demo application tasks, then starts the scheduler. The WEB\r
* documentation provides more details of the demo application tasks.\r
- * \r
- * Main.c also creates a task called "Check". This only executes every three \r
- * seconds but has the highest priority so is guaranteed to get processor time. \r
+ *\r
+ * Main.c also creates a task called "Check". This only executes every three\r
+ * seconds but has the highest priority so is guaranteed to get processor time.\r
* Its main function is to check that all the other tasks are still operational.\r
- * Each task (other than the "flash" tasks) maintains a unique count that is \r
- * incremented each time the task successfully completes its function. Should \r
- * any error occur within such a task the count is permanently halted. The \r
+ * Each task (other than the "flash" tasks) maintains a unique count that is\r
+ * incremented each time the task successfully completes its function. Should\r
+ * any error occur within such a task the count is permanently halted. The\r
* check task inspects the count of each task to ensure it has changed since\r
- * the last time the check task executed. If all the count variables have \r
+ * the last time the check task executed. If all the count variables have\r
* changed all the tasks are still executing error free, and the check task\r
- * toggles the onboard LED. Should any task contain an error at any time \r
+ * toggles the onboard LED. Should any task contain an error at any time\r
* the LED toggle rate will change from 3 seconds to 500ms.\r
*\r
- * To check the operation of the memory allocator the check task also \r
- * dynamically creates a task before delaying, and deletes it again when it \r
+ * To check the operation of the memory allocator the check task also\r
+ * dynamically creates a task before delaying, and deletes it again when it\r
* wakes. If memory cannot be allocated for the new task the call to xTaskCreate\r
* will fail and an error is signalled. The dynamically created task itself\r
* allocates and frees memory just to give the allocator a bit more exercise.\r
\r
/* LED that is toggled by the check task. The check task periodically checks\r
that all the other tasks are operating without error. If no errors are found\r
-the LED is toggled with mainCHECK_PERIOD frequency. If an error is found \r
+the LED is toggled with mainCHECK_PERIOD frequency. If an error is found\r
the the toggle rate increases to mainERROR_CHECK_PERIOD. */\r
#define mainCHECK_TASK_LED ( 5 )\r
-#define mainCHECK_PERIOD ( ( portTickType ) 3000 / portTICK_RATE_MS )\r
-#define mainERROR_CHECK_PERIOD ( ( portTickType ) 500 / portTICK_RATE_MS )\r
+#define mainCHECK_PERIOD ( ( TickType_t ) 3000 / portTICK_PERIOD_MS )\r
+#define mainERROR_CHECK_PERIOD ( ( TickType_t ) 500 / portTICK_PERIOD_MS )\r
\r
/* Constants used by the vMemCheckTask() task. */\r
#define mainCOUNT_INITIAL_VALUE ( ( unsigned long ) 0 )\r
vStartBlockingQueueTasks( mainBLOCK_Q_PRIORITY );\r
\r
/* Start the 'Check' task. */\r
- xTaskCreate( vErrorChecks, ( signed char * )"Check", configMINIMAL_STACK_SIZE, NULL, mainCHECK_TASK_PRIORITY, NULL );\r
+ xTaskCreate( vErrorChecks, "Check", configMINIMAL_STACK_SIZE, NULL, mainCHECK_TASK_PRIORITY, NULL );\r
\r
- /* In this port, to use preemptive scheduler define configUSE_PREEMPTION \r
- as 1 in portmacro.h. To use the cooperative scheduler define \r
+ /* In this port, to use preemptive scheduler define configUSE_PREEMPTION\r
+ as 1 in portmacro.h. To use the cooperative scheduler define\r
configUSE_PREEMPTION as 0. */\r
vTaskStartScheduler();\r
\r
* Cycle for ever, delaying then checking all the other tasks are still\r
* operating without error. If an error is detected then the delay period\r
* is decreased from mainCHECK_PERIOD to mainERROR_CHECK_PERIOD so\r
- * the on board LED flash rate will increase. \r
+ * the on board LED flash rate will increase.\r
*\r
* In addition to the standard tests the memory allocator is tested through\r
- * the dynamic creation and deletion of a task each cycle. Each time the \r
+ * the dynamic creation and deletion of a task each cycle. Each time the\r
* task is created memory must be allocated for its stack. When the task is\r
- * deleted this memory is returned to the heap. If the task cannot be created \r
+ * deleted this memory is returned to the heap. If the task cannot be created\r
* then it is likely that the memory allocation failed. In addition the\r
- * dynamically created task allocates and frees memory while it runs. \r
+ * dynamically created task allocates and frees memory while it runs.\r
*/\r
static void vErrorChecks( void *pvParameters )\r
{\r
-portTickType xDelayPeriod = mainCHECK_PERIOD;\r
+TickType_t xDelayPeriod = mainCHECK_PERIOD;\r
volatile unsigned long ulMemCheckTaskRunningCount;\r
-xTaskHandle xCreatedTask;\r
-portTickType xLastWakeTime;\r
+TaskHandle_t xCreatedTask;\r
+TickType_t xLastWakeTime;\r
\r
/* Initialise xLastWakeTime to ensure the first call to vTaskDelayUntil()\r
functions correctly. */\r
later that it has changed. */\r
ulMemCheckTaskRunningCount = mainCOUNT_INITIAL_VALUE;\r
\r
- /* Dynamically create a task - passing ulMemCheckTaskRunningCount as a \r
- parameter. */ \r
+ /* Dynamically create a task - passing ulMemCheckTaskRunningCount as a\r
+ parameter. */\r
xCreatedTask = mainNO_TASK;\r
- if( xTaskCreate( vMemCheckTask, ( signed char * ) "MEM_CHECK", configMINIMAL_STACK_SIZE, ( void * ) &ulMemCheckTaskRunningCount, tskIDLE_PRIORITY, &xCreatedTask ) != pdPASS )\r
+ if( xTaskCreate( vMemCheckTask, "MEM_CHECK", configMINIMAL_STACK_SIZE, ( void * ) &ulMemCheckTaskRunningCount, tskIDLE_PRIORITY, &xCreatedTask ) != pdPASS )\r
{\r
/* Could not create the task - we have probably run out of heap. */\r
xDelayPeriod = mainERROR_CHECK_PERIOD;\r
}\r
\r
\r
- /* Delay until it is time to execute again. The delay period is \r
+ /* Delay until it is time to execute again. The delay period is\r
shorter following an error. */\r
vTaskDelayUntil( &xLastWakeTime, xDelayPeriod );\r
\r
- \r
+\r
/* Delete the dynamically created task. */\r
if( xCreatedTask != mainNO_TASK )\r
{\r
vTaskDelete( xCreatedTask );\r
}\r
\r
- /* Check all the standard demo application tasks are executing without \r
+ /* Check all the standard demo application tasks are executing without\r
error. ulMemCheckTaskRunningCount is checked to ensure it was\r
modified by the task just deleted. */\r
if( prvCheckOtherTasksAreStillRunning( ulMemCheckTaskRunningCount ) != pdPASS )\r
\r
/*\r
* Check each set of tasks in turn to see if they have experienced any\r
- * error conditions. \r
+ * error conditions.\r
*/\r
static long prvCheckOtherTasksAreStillRunning( unsigned long ulMemCheckTaskCount )\r
{\r
vErrorChecks task to check the operation of the memory allocator. Each time\r
the task is created memory is allocated for the stack and TCB. Each time\r
the task is deleted this memory is returned to the heap. This task itself\r
- exercises the allocator by allocating and freeing blocks. \r
- \r
- The task executes at the idle priority so does not require a delay. \r
- \r
+ exercises the allocator by allocating and freeing blocks.\r
+\r
+ The task executes at the idle priority so does not require a delay.\r
+\r
pulMemCheckTaskRunningCounter is incremented each cycle to indicate to the\r
vErrorChecks() task that this task is still executing without error. */\r
\r
}\r
else\r
{\r
- /* Reset the count so an error is detected by the \r
+ /* Reset the count so an error is detected by the\r
prvCheckOtherTasksAreStillRunning() function. */\r
*pulMemCheckTaskRunningCounter = mainCOUNT_INITIAL_VALUE;\r
}\r
\r
- /* Allocate some memory - just to give the allocator some extra \r
+ /* Allocate some memory - just to give the allocator some extra\r
exercise. This has to be in a critical section to ensure the\r
task does not get deleted while it has memory allocated. */\r
vTaskSuspendAll();\r
projects / freertos / blobdiff