2 FreeRTOS V8.2.3 - Copyright (C) 2015 Real Time Engineers Ltd.
\r
5 VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.
\r
7 This file is part of the FreeRTOS distribution.
\r
9 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
10 the terms of the GNU General Public License (version 2) as published by the
\r
11 Free Software Foundation >>>> AND MODIFIED BY <<<< the FreeRTOS exception.
\r
13 ***************************************************************************
\r
14 >>! NOTE: The modification to the GPL is included to allow you to !<<
\r
15 >>! distribute a combined work that includes FreeRTOS without being !<<
\r
16 >>! obliged to provide the source code for proprietary components !<<
\r
17 >>! outside of the FreeRTOS kernel. !<<
\r
18 ***************************************************************************
\r
20 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
21 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
22 FOR A PARTICULAR PURPOSE. Full license text is available on the following
\r
23 link: http://www.freertos.org/a00114.html
\r
25 ***************************************************************************
\r
27 * FreeRTOS provides completely free yet professionally developed, *
\r
28 * robust, strictly quality controlled, supported, and cross *
\r
29 * platform software that is more than just the market leader, it *
\r
30 * is the industry's de facto standard. *
\r
32 * Help yourself get started quickly while simultaneously helping *
\r
33 * to support the FreeRTOS project by purchasing a FreeRTOS *
\r
34 * tutorial book, reference manual, or both: *
\r
35 * http://www.FreeRTOS.org/Documentation *
\r
37 ***************************************************************************
\r
39 http://www.FreeRTOS.org/FAQHelp.html - Having a problem? Start by reading
\r
40 the FAQ page "My application does not run, what could be wrong?". Have you
\r
41 defined configASSERT()?
\r
43 http://www.FreeRTOS.org/support - In return for receiving this top quality
\r
44 embedded software for free we request you assist our global community by
\r
45 participating in the support forum.
\r
47 http://www.FreeRTOS.org/training - Investing in training allows your team to
\r
48 be as productive as possible as early as possible. Now you can receive
\r
49 FreeRTOS training directly from Richard Barry, CEO of Real Time Engineers
\r
50 Ltd, and the world's leading authority on the world's leading RTOS.
\r
52 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
53 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
54 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
56 http://www.FreeRTOS.org/labs - Where new FreeRTOS products go to incubate.
\r
57 Come and try FreeRTOS+TCP, our new open source TCP/IP stack for FreeRTOS.
\r
59 http://www.OpenRTOS.com - Real Time Engineers ltd. license FreeRTOS to High
\r
60 Integrity Systems ltd. to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
61 licenses offer ticketed support, indemnification and commercial middleware.
\r
63 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
64 engineered and independently SIL3 certified version for use in safety and
\r
65 mission critical applications that require provable dependability.
\r
70 /******************************************************************************
\r
71 * NOTE 1: This project provides two demo applications. A simple blinky style
\r
72 * project, and a more comprehensive test and demo application. The
\r
73 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting in main.c is used to select
\r
74 * between the two. See the notes on using mainCREATE_SIMPLE_BLINKY_DEMO_ONLY
\r
75 * in main.c. This file implements the comprehensive test and demo version.
\r
77 * NOTE 2: This file only contains the source code that is specific to the
\r
78 * full demo. Generic functions, such FreeRTOS hook functions, and functions
\r
79 * required to configure the hardware, are defined in main.c.
\r
81 ******************************************************************************
\r
83 * main_full() creates all the demo application tasks and software timers, then
\r
84 * starts the scheduler. The web documentation provides more details of the
\r
85 * standard demo application tasks, which provide no particular functionality,
\r
86 * but do provide a good example of how to use the FreeRTOS API.
\r
88 * In addition to the standard demo tasks, the following tasks and tests are
\r
89 * defined and/or created within this file:
\r
91 * "Reg test" tasks - These fill both the core and floating point registers with
\r
92 * known values, then check that each register maintains its expected value for
\r
93 * the lifetime of the task. Each task uses a different set of values. The reg
\r
94 * test tasks execute with a very low priority, so get preempted very
\r
95 * frequently. A register containing an unexpected value is indicative of an
\r
96 * error in the context switching mechanism.
\r
98 * "Check" task - The check task period is initially set to three seconds. The
\r
99 * task checks that all the standard demo tasks, and the register check tasks,
\r
100 * are not only still executing, but are executing without reporting any errors.
\r
101 * If the check task discovers that a task has either stalled, or reported an
\r
102 * error, then it changes its own execution period from the initial three
\r
103 * seconds, to just 200ms. The check task also toggles an LED each time it is
\r
104 * called. This provides a visual indication of the system status: If the LED
\r
105 * toggles every three seconds, then no issues have been discovered. If the LED
\r
106 * toggles every 200ms, then an issue has been discovered with at least one
\r
110 /* Standard includes. */
\r
113 /* Kernel includes. */
\r
114 #include "FreeRTOS.h"
\r
116 #include "timers.h"
\r
117 #include "semphr.h"
\r
119 /* Standard demo application includes. */
\r
121 #include "semtest.h"
\r
122 #include "dynamic.h"
\r
123 #include "BlockQ.h"
\r
124 #include "blocktim.h"
\r
125 #include "countsem.h"
\r
126 #include "GenQTest.h"
\r
127 #include "recmutex.h"
\r
129 #include "partest.h"
\r
130 #include "comtest2.h"
\r
131 #include "serial.h"
\r
132 #include "TimerDemo.h"
\r
133 #include "QueueOverwrite.h"
\r
134 #include "IntQueue.h"
\r
135 #include "EventGroupsDemo.h"
\r
136 #include "IntSemTest.h"
\r
137 #include "TaskNotify.h"
\r
139 /* Priorities for the demo application tasks. */
\r
140 #define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1UL )
\r
141 #define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2UL )
\r
142 #define mainCREATOR_TASK_PRIORITY ( tskIDLE_PRIORITY + 3UL )
\r
143 #define mainFLOP_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
144 #define mainCDC_COMMAND_CONSOLE_STACK_SIZE ( configMINIMAL_STACK_SIZE * 2UL )
\r
145 #define mainCOM_TEST_TASK_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
146 #define mainCHECK_TASK_PRIORITY ( configMAX_PRIORITIES - 1 )
\r
147 #define mainQUEUE_OVERWRITE_PRIORITY ( tskIDLE_PRIORITY )
\r
149 /* The initial priority used by the UART command console task. */
\r
150 #define mainUART_COMMAND_CONSOLE_TASK_PRIORITY ( configMAX_PRIORITIES - 2 )
\r
152 /* The LED used by the check timer. */
\r
153 #define mainCHECK_LED ( 0 )
\r
155 /* A block time of zero simply means "don't block". */
\r
156 #define mainDONT_BLOCK ( 0UL )
\r
158 /* The period after which the check timer will expire, in ms, provided no errors
\r
159 have been reported by any of the standard demo tasks. ms are converted to the
\r
160 equivalent in ticks using the portTICK_PERIOD_MS constant. */
\r
161 #define mainNO_ERROR_CHECK_TASK_PERIOD ( 3000UL / portTICK_PERIOD_MS )
\r
163 /* The period at which the check timer will expire, in ms, if an error has been
\r
164 reported in one of the standard demo tasks. ms are converted to the equivalent
\r
165 in ticks using the portTICK_PERIOD_MS constant. */
\r
166 #define mainERROR_CHECK_TASK_PERIOD ( 200UL / portTICK_PERIOD_MS )
\r
168 /* Parameters that are passed into the register check tasks solely for the
\r
169 purpose of ensuring parameters are passed into tasks correctly. */
\r
170 #define mainREG_TEST_TASK_1_PARAMETER ( ( void * ) 0x12345678 )
\r
171 #define mainREG_TEST_TASK_2_PARAMETER ( ( void * ) 0x87654321 )
\r
173 /* The base period used by the timer test tasks. */
\r
174 #define mainTIMER_TEST_PERIOD ( 50 )
\r
176 /*-----------------------------------------------------------*/
\r
179 * Called by main() to run the full demo (as opposed to the blinky demo) when
\r
180 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
182 void main_full( void );
\r
185 * The check task, as described at the top of this file.
\r
187 static void prvCheckTask( void *pvParameters );
\r
190 * Register check tasks, and the tasks used to write over and check the contents
\r
191 * of the FPU registers, as described at the top of this file. The nature of
\r
192 * these files necessitates that they are written in an assembly file, but the
\r
193 * entry points are kept in the C file for the convenience of checking the task
\r
196 static void prvRegTestTaskEntry1( void *pvParameters );
\r
197 extern void vRegTest1Implementation( void );
\r
198 static void prvRegTestTaskEntry2( void *pvParameters );
\r
199 extern void vRegTest2Implementation( void );
\r
201 /*-----------------------------------------------------------*/
\r
203 /* The following two variables are used to communicate the status of the
\r
204 register check tasks to the check task. If the variables keep incrementing,
\r
205 then the register check tasks have not discovered any errors. If a variable
\r
206 stops incrementing, then an error has been found. */
\r
207 volatile unsigned long ulRegTest1LoopCounter = 0UL, ulRegTest2LoopCounter = 0UL;
\r
209 /*-----------------------------------------------------------*/
\r
211 void main_full( void )
\r
213 /* Start all the other standard demo/test tasks. They have no particular
\r
214 functionality, but do demonstrate how to use the FreeRTOS API and test the
\r
216 vStartInterruptQueueTasks();
\r
217 vStartDynamicPriorityTasks();
\r
218 vStartBlockingQueueTasks( mainBLOCK_Q_PRIORITY );
\r
219 vCreateBlockTimeTasks();
\r
220 vStartCountingSemaphoreTasks();
\r
221 vStartGenericQueueTasks( tskIDLE_PRIORITY );
\r
222 vStartRecursiveMutexTasks();
\r
223 vStartSemaphoreTasks( mainSEM_TEST_PRIORITY );
\r
224 vStartMathTasks( mainFLOP_TASK_PRIORITY );
\r
225 vStartTimerDemoTask( mainTIMER_TEST_PERIOD );
\r
226 vStartQueueOverwriteTask( mainQUEUE_OVERWRITE_PRIORITY );
\r
227 vStartEventGroupTasks();
\r
228 vStartInterruptSemaphoreTasks();
\r
229 vStartTaskNotifyTask();
\r
231 /* Create the register check tasks, as described at the top of this file */
\r
232 xTaskCreate( prvRegTestTaskEntry1, "Reg1", configMINIMAL_STACK_SIZE, mainREG_TEST_TASK_1_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
233 xTaskCreate( prvRegTestTaskEntry2, "Reg2", configMINIMAL_STACK_SIZE, mainREG_TEST_TASK_2_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
235 /* Create the task that performs the 'check' functionality, as described at
\r
236 the top of this file. */
\r
237 xTaskCreate( prvCheckTask, "Check", configMINIMAL_STACK_SIZE, NULL, mainCHECK_TASK_PRIORITY, NULL );
\r
239 /* The set of tasks created by the following function call have to be
\r
240 created last as they keep account of the number of tasks they expect to see
\r
242 vCreateSuicidalTasks( mainCREATOR_TASK_PRIORITY );
\r
244 /* Start the scheduler. */
\r
245 vTaskStartScheduler();
\r
247 /* If all is well, the scheduler will now be running, and the following
\r
248 line will never be reached. If the following line does execute, then
\r
249 there was insufficient FreeRTOS heap memory available for the Idle and/or
\r
250 timer tasks to be created. See the memory management section on the
\r
251 FreeRTOS web site for more details on the FreeRTOS heap
\r
252 http://www.freertos.org/a00111.html. */
\r
255 /*-----------------------------------------------------------*/
\r
257 static void prvCheckTask( void *pvParameters )
\r
259 TickType_t xDelayPeriod = mainNO_ERROR_CHECK_TASK_PERIOD;
\r
260 TickType_t xLastExecutionTime;
\r
261 static unsigned long ulLastRegTest1Value = 0, ulLastRegTest2Value = 0;
\r
262 unsigned long ulErrorFound = pdFALSE;
\r
264 /* Just to stop compiler warnings. */
\r
265 ( void ) pvParameters;
\r
267 /* Initialise xLastExecutionTime so the first call to vTaskDelayUntil()
\r
268 works correctly. */
\r
269 xLastExecutionTime = xTaskGetTickCount();
\r
271 /* Cycle for ever, delaying then checking all the other tasks are still
\r
272 operating without error. The onboard LED is toggled on each iteration.
\r
273 If an error is detected then the delay period is decreased from
\r
274 mainNO_ERROR_CHECK_TASK_PERIOD to mainERROR_CHECK_TASK_PERIOD. This has the
\r
275 effect of increasing the rate at which the onboard LED toggles, and in so
\r
276 doing gives visual feedback of the system status. */
\r
279 /* Delay until it is time to execute again. */
\r
280 vTaskDelayUntil( &xLastExecutionTime, xDelayPeriod );
\r
282 /* Check all the demo tasks (other than the flash tasks) to ensure
\r
283 that they are all still running, and that none have detected an error. */
\r
284 if( xAreIntQueueTasksStillRunning() != pdTRUE )
\r
286 ulErrorFound = 1UL << 0UL;
\r
289 if( xAreMathsTaskStillRunning() != pdTRUE )
\r
291 ulErrorFound = 1UL << 1UL;
\r
294 if( xAreDynamicPriorityTasksStillRunning() != pdTRUE )
\r
296 ulErrorFound = 1UL << 2UL;
\r
299 if( xAreBlockingQueuesStillRunning() != pdTRUE )
\r
301 ulErrorFound = 1UL << 3UL;
\r
304 if ( xAreBlockTimeTestTasksStillRunning() != pdTRUE )
\r
306 ulErrorFound = 1UL << 4UL;
\r
309 if ( xAreGenericQueueTasksStillRunning() != pdTRUE )
\r
311 ulErrorFound = 1UL << 5UL;
\r
314 if ( xAreRecursiveMutexTasksStillRunning() != pdTRUE )
\r
316 ulErrorFound = 1UL << 6UL;
\r
319 if( xIsCreateTaskStillRunning() != pdTRUE )
\r
321 ulErrorFound = 1UL << 7UL;
\r
324 if( xAreSemaphoreTasksStillRunning() != pdTRUE )
\r
326 ulErrorFound = 1UL << 8UL;
\r
329 if( xAreTimerDemoTasksStillRunning( ( TickType_t ) xDelayPeriod ) != pdPASS )
\r
331 ulErrorFound = 1UL << 9UL;
\r
334 if( xAreCountingSemaphoreTasksStillRunning() != pdTRUE )
\r
336 ulErrorFound = 1UL << 10UL;
\r
339 if( xIsQueueOverwriteTaskStillRunning() != pdPASS )
\r
341 ulErrorFound = 1UL << 11UL;
\r
344 if( xAreEventGroupTasksStillRunning() != pdPASS )
\r
346 ulErrorFound = 1UL << 12UL;
\r
349 if( xAreInterruptSemaphoreTasksStillRunning() != pdPASS )
\r
351 ulErrorFound = 1UL << 13UL;
\r
354 if( xAreTaskNotificationTasksStillRunning() != pdPASS )
\r
356 ulErrorFound = 1UL << 14UL;
\r
359 /* Check that the register test 1 task is still running. */
\r
360 if( ulLastRegTest1Value == ulRegTest1LoopCounter )
\r
362 ulErrorFound = 1UL << 15UL;
\r
364 ulLastRegTest1Value = ulRegTest1LoopCounter;
\r
366 /* Check that the register test 2 task is still running. */
\r
367 if( ulLastRegTest2Value == ulRegTest2LoopCounter )
\r
369 ulErrorFound = 1UL << 16UL;
\r
371 ulLastRegTest2Value = ulRegTest2LoopCounter;
\r
373 /* Toggle the check LED to give an indication of the system status. If
\r
374 the LED toggles every mainNO_ERROR_CHECK_TASK_PERIOD milliseconds then
\r
375 everything is ok. A faster toggle indicates an error. */
\r
376 LED_Toggle( mainCHECK_LED );
\r
378 if( ulErrorFound != pdFALSE )
\r
380 /* An error has been detected in one of the tasks - flash the LED
\r
381 at a higher frequency to give visible feedback that something has
\r
382 gone wrong (it might just be that the loop back connector required
\r
383 by the comtest tasks has not been fitted). */
\r
384 xDelayPeriod = mainERROR_CHECK_TASK_PERIOD;
\r
388 /*-----------------------------------------------------------*/
\r
390 static void prvRegTestTaskEntry1( void *pvParameters )
\r
392 /* Although the regtest task is written in assembler, its entry point is
\r
393 written in C for convenience of checking the task parameter is being passed
\r
395 if( pvParameters == mainREG_TEST_TASK_1_PARAMETER )
\r
397 /* Start the part of the test that is written in assembler. */
\r
398 vRegTest1Implementation();
\r
401 /* The following line will only execute if the task parameter is found to
\r
402 be incorrect. The check timer will detect that the regtest loop counter is
\r
403 not being incremented and flag an error. */
\r
404 vTaskDelete( NULL );
\r
406 /*-----------------------------------------------------------*/
\r
408 static void prvRegTestTaskEntry2( void *pvParameters )
\r
410 /* Although the regtest task is written in assembler, its entry point is
\r
411 written in C for convenience of checking the task parameter is being passed
\r
413 if( pvParameters == mainREG_TEST_TASK_2_PARAMETER )
\r
415 /* Start the part of the test that is written in assembler. */
\r
416 vRegTest2Implementation();
\r
419 /* The following line will only execute if the task parameter is found to
\r
420 be incorrect. The check timer will detect that the regtest loop counter is
\r
421 not being incremented and flag an error. */
\r
422 vTaskDelete( NULL );
\r
424 /*-----------------------------------------------------------*/
\r