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 that demonstrates the tickless low power features of FreeRTOS, and a
\r
73 * more comprehensive test and demo application. The configCREATE_LOW_POWER_DEMO
\r
74 * setting in FreeRTOSConifg.h is used to select between the two. See the notes
\r
75 * on using conifgCREATE_LOW_POWER_DEMO in main.c. This file implements the
\r
76 * comprehensive test and demo version.
\r
78 * NOTE 2: This file only contains the source code that is specific to the
\r
79 * full demo. Generic functions, such FreeRTOS hook functions, and functions
\r
80 * required to configure the hardware, are defined in main.c.
\r
82 ******************************************************************************
\r
84 * main_full() creates all the demo application tasks and software timers, then
\r
85 * starts the scheduler. The web documentation provides more details of the
\r
86 * standard demo application tasks, which provide no particular functionality,
\r
87 * but do provide a good example of how to use the FreeRTOS API.
\r
89 * In addition to the standard demo tasks, the following tasks and tests are
\r
90 * defined and/or created within this file:
\r
92 * "Reg test" tasks - These fill both the core and floating point registers with
\r
93 * known values, then check that each register maintains its expected value for
\r
94 * the lifetime of the task. Each task uses a different set of values. The reg
\r
95 * test tasks execute with a very low priority, so get preempted very
\r
96 * frequently. A register containing an unexpected value is indicative of an
\r
97 * error in the context switching mechanism.
\r
99 * "Check" task - The check task period is initially set to three seconds. The
\r
100 * task checks that all the standard demo tasks, and the register check tasks,
\r
101 * are not only still executing, but are executing without reporting any errors.
\r
102 * If the check task discovers that a task has either stalled, or reported an
\r
103 * error, then it changes its own execution period from the initial three
\r
104 * seconds, to just 200ms. The check task also toggles an LED each time it is
\r
105 * called. This provides a visual indication of the system status: If the LED
\r
106 * toggles every three seconds, then no issues have been discovered. If the LED
\r
107 * toggles every 200ms, then an issue has been discovered with at least one
\r
111 /* Standard includes. */
\r
114 /* Kernel includes. */
\r
115 #include "FreeRTOS.h"
\r
117 #include "timers.h"
\r
118 #include "semphr.h"
\r
120 /* Standard demo application includes. */
\r
122 #include "semtest.h"
\r
123 #include "dynamic.h"
\r
124 #include "blocktim.h"
\r
125 #include "countsem.h"
\r
126 #include "GenQTest.h"
\r
128 #include "TimerDemo.h"
\r
129 #include "IntQueue.h"
\r
130 #include "EventGroupsDemo.h"
\r
131 #include "TaskNotify.h"
\r
133 /* Priorities for the demo application tasks. */
\r
134 #define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1UL )
\r
135 #define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2UL )
\r
136 #define mainCREATOR_TASK_PRIORITY ( tskIDLE_PRIORITY + 3UL )
\r
137 #define mainFLOP_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
138 #define mainCHECK_TASK_PRIORITY ( configMAX_PRIORITIES - 1 )
\r
140 /* A block time of zero simply means "don't block". */
\r
141 #define mainDONT_BLOCK ( 0UL )
\r
143 /* The period of the check task, in ms, provided no errors have been reported by
\r
144 any of the standard demo tasks. ms are converted to the equivalent in ticks
\r
145 using the pdMS_TO_TICKS() macro constant. */
\r
146 #define mainNO_ERROR_CHECK_TASK_PERIOD pdMS_TO_TICKS( 3000UL )
\r
148 /* The period of the check task, in ms, if an error has been reported in one of
\r
149 the standard demo tasks. ms are converted to the equivalent in ticks using the
\r
150 pdMS_TO_TICKS() macro. */
\r
151 #define mainERROR_CHECK_TASK_PERIOD pdMS_TO_TICKS( 200UL )
\r
153 /* Parameters that are passed into the register check tasks solely for the
\r
154 purpose of ensuring parameters are passed into tasks correctly. */
\r
155 #define mainREG_TEST_TASK_1_PARAMETER ( ( void * ) 0x12345678 )
\r
156 #define mainREG_TEST_TASK_2_PARAMETER ( ( void * ) 0x87654321 )
\r
158 /* The base period used by the timer test tasks. */
\r
159 #define mainTIMER_TEST_PERIOD ( 50 )
\r
161 /*-----------------------------------------------------------*/
\r
164 * Called by main() to run the full demo (as opposed to the blinky demo) when
\r
165 * configCREATE_LOW_POWER_DEMO is set to 0.
\r
167 void main_full( void );
\r
170 * The check task, as described at the top of this file.
\r
172 static void prvCheckTask( void *pvParameters );
\r
175 * Some of the tests and demo tasks executed by the full demo include
\r
176 * interaction from an interrupt - for which the tick interrupt is used via the
\r
177 * tick hook function.
\r
179 void vFullDemoTickHook( void );
\r
182 * Register check tasks, and the tasks used to write over and check the contents
\r
183 * of the FPU registers, as described at the top of this file. The nature of
\r
184 * these files necessitates that they are written in an assembly file, but the
\r
185 * entry points are kept in the C file for the convenience of checking the task
\r
188 static void prvRegTestTaskEntry1( void *pvParameters );
\r
189 extern void vRegTest1Implementation( void );
\r
190 static void prvRegTestTaskEntry2( void *pvParameters );
\r
191 extern void vRegTest2Implementation( void );
\r
193 /*-----------------------------------------------------------*/
\r
195 /* The following two variables are used to communicate the status of the
\r
196 register check tasks to the check task. If the variables keep incrementing,
\r
197 then the register check tasks have not discovered any errors. If a variable
\r
198 stops incrementing, then an error has been found. */
\r
199 volatile unsigned long ulRegTest1LoopCounter = 0UL, ulRegTest2LoopCounter = 0UL;
\r
201 /* The variable that is incremented to represent each LED toggle. On the
\r
202 clicker hardware the LED state is set to the value of the least significant bit
\r
203 of this variable. On other hardware, where an LED is not used, the LED just
\r
204 keeps a count of the number of times the LED would otherwise have been toggled.
\r
205 See the comments at the top of this file for information on the expected LED
\r
207 extern volatile uint32_t ulLED;
\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 vStartDynamicPriorityTasks();
\r
217 vCreateBlockTimeTasks();
\r
218 vStartCountingSemaphoreTasks();
\r
219 vStartGenericQueueTasks( tskIDLE_PRIORITY );
\r
220 vStartSemaphoreTasks( mainSEM_TEST_PRIORITY );
\r
221 vStartMathTasks( mainFLOP_TASK_PRIORITY );
\r
222 vStartTimerDemoTask( mainTIMER_TEST_PERIOD );
\r
223 vStartEventGroupTasks();
\r
224 vStartTaskNotifyTask();
\r
225 vStartInterruptQueueTasks();
\r
227 /* Create the register check tasks, as described at the top of this file */
\r
228 xTaskCreate( prvRegTestTaskEntry1, "Reg1", configMINIMAL_STACK_SIZE, mainREG_TEST_TASK_1_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
229 xTaskCreate( prvRegTestTaskEntry2, "Reg2", configMINIMAL_STACK_SIZE, mainREG_TEST_TASK_2_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
231 /* Create the task that performs the 'check' functionality, as described at
\r
232 the top of this file. */
\r
233 xTaskCreate( prvCheckTask, "Check", configMINIMAL_STACK_SIZE, NULL, mainCHECK_TASK_PRIORITY, NULL );
\r
235 /* The set of tasks created by the following function call have to be
\r
236 created last as they keep account of the number of tasks they expect to see
\r
238 vCreateSuicidalTasks( mainCREATOR_TASK_PRIORITY );
\r
240 /* Start the scheduler. */
\r
241 vTaskStartScheduler();
\r
243 /* If all is well, the scheduler will now be running, and the following
\r
244 line will never be reached. If the following line does execute, then
\r
245 there was insufficient FreeRTOS heap memory available for the Idle and/or
\r
246 timer tasks to be created. See the memory management section on the
\r
247 FreeRTOS web site for more details on the FreeRTOS heap
\r
248 http://www.freertos.org/a00111.html. */
\r
251 /*-----------------------------------------------------------*/
\r
253 static void prvCheckTask( void *pvParameters )
\r
255 TickType_t xDelayPeriod = mainNO_ERROR_CHECK_TASK_PERIOD;
\r
256 TickType_t xLastExecutionTime;
\r
257 static unsigned long ulLastRegTest1Value = 0, ulLastRegTest2Value = 0;
\r
258 unsigned long ulErrorFound = pdFALSE;
\r
260 /* Just to stop compiler warnings. */
\r
261 ( void ) pvParameters;
\r
263 /* Initialise xLastExecutionTime so the first call to vTaskDelayUntil()
\r
264 works correctly. */
\r
265 xLastExecutionTime = xTaskGetTickCount();
\r
267 /* Cycle for ever, delaying then checking all the other tasks are still
\r
268 operating without error. The onboard LED is toggled on each iteration.
\r
269 If an error is detected then the delay period is decreased from
\r
270 mainNO_ERROR_CHECK_TASK_PERIOD to mainERROR_CHECK_TASK_PERIOD. This has the
\r
271 effect of increasing the rate at which the onboard LED toggles, and in so
\r
272 doing gives visual feedback of the system status. */
\r
275 /* Delay until it is time to execute again. */
\r
276 vTaskDelayUntil( &xLastExecutionTime, xDelayPeriod );
\r
278 /* Check all the demo tasks (other than the flash tasks) to ensure
\r
279 that they are all still running, and that none have detected an error. */
\r
280 if( xAreIntQueueTasksStillRunning() != pdTRUE )
\r
282 ulErrorFound = 1UL << 0UL;
\r
285 if( xAreMathsTaskStillRunning() != pdTRUE )
\r
287 ulErrorFound = 1UL << 1UL;
\r
290 if( xAreDynamicPriorityTasksStillRunning() != pdTRUE )
\r
292 ulErrorFound = 1UL << 2UL;
\r
295 if( xAreBlockTimeTestTasksStillRunning() != pdTRUE )
\r
297 ulErrorFound = 1UL << 4UL;
\r
300 if( xAreGenericQueueTasksStillRunning() != pdTRUE )
\r
302 ulErrorFound = 1UL << 5UL;
\r
305 if( xIsCreateTaskStillRunning() != pdTRUE )
\r
307 ulErrorFound = 1UL << 7UL;
\r
310 if( xAreSemaphoreTasksStillRunning() != pdTRUE )
\r
312 ulErrorFound = 1UL << 8UL;
\r
315 if( xAreTimerDemoTasksStillRunning( ( TickType_t ) xDelayPeriod ) != pdPASS )
\r
317 ulErrorFound = 1UL << 9UL;
\r
320 if( xAreCountingSemaphoreTasksStillRunning() != pdTRUE )
\r
322 ulErrorFound = 1UL << 10UL;
\r
325 if( xAreEventGroupTasksStillRunning() != pdPASS )
\r
327 ulErrorFound = 1UL << 12UL;
\r
330 if( xAreTaskNotificationTasksStillRunning() != pdPASS )
\r
332 ulErrorFound = 1UL << 14UL;
\r
335 /* Check that the register test 1 task is still running. */
\r
336 if( ulLastRegTest1Value == ulRegTest1LoopCounter )
\r
338 ulErrorFound = 1UL << 15UL;
\r
340 ulLastRegTest1Value = ulRegTest1LoopCounter;
\r
342 /* Check that the register test 2 task is still running. */
\r
343 if( ulLastRegTest2Value == ulRegTest2LoopCounter )
\r
345 ulErrorFound = 1UL << 16UL;
\r
347 ulLastRegTest2Value = ulRegTest2LoopCounter;
\r
349 /* Toggle the check LED to give an indication of the system status. If
\r
350 the LED toggles every mainNO_ERROR_CHECK_TASK_PERIOD milliseconds then
\r
351 everything is ok. A faster toggle indicates an error. */
\r
352 configTOGGLE_LED();
\r
354 if( ulErrorFound != pdFALSE )
\r
356 /* An error has been detected in one of the tasks - flash the LED
\r
357 at a higher frequency to give visible feedback that something has
\r
358 gone wrong (it might just be that the loop back connector required
\r
359 by the comtest tasks has not been fitted). */
\r
360 xDelayPeriod = mainERROR_CHECK_TASK_PERIOD;
\r
363 configASSERT( ulErrorFound == pdFALSE );
\r
365 /* Just testing the xPortIsInsideInterrupt() functionality. */
\r
366 configASSERT( xPortIsInsideInterrupt() == pdFALSE );
\r
369 /*-----------------------------------------------------------*/
\r
371 static void prvRegTestTaskEntry1( void *pvParameters )
\r
373 /* Although the regtest task is written in assembler, its entry point is
\r
374 written in C for convenience of checking the task parameter is being passed
\r
376 if( pvParameters == mainREG_TEST_TASK_1_PARAMETER )
\r
378 /* Start the part of the test that is written in assembler. */
\r
379 vRegTest1Implementation();
\r
382 /* The following line will only execute if the task parameter is found to
\r
383 be incorrect. The check task will detect that the regtest loop counter is
\r
384 not being incremented and flag an error. */
\r
385 vTaskDelete( NULL );
\r
387 /*-----------------------------------------------------------*/
\r
389 static void prvRegTestTaskEntry2( void *pvParameters )
\r
391 /* Although the regtest task is written in assembler, its entry point is
\r
392 written in C for convenience of checking the task parameter is being passed
\r
394 if( pvParameters == mainREG_TEST_TASK_2_PARAMETER )
\r
396 /* Start the part of the test that is written in assembler. */
\r
397 vRegTest2Implementation();
\r
400 /* The following line will only execute if the task parameter is found to
\r
401 be incorrect. The check task will detect that the regtest loop counter is
\r
402 not being incremented and flag an error. */
\r
403 vTaskDelete( NULL );
\r
405 /*-----------------------------------------------------------*/
\r
407 void vFullDemoTickHook( void )
\r
409 /* Some of the tests and demo tasks executed by the full demo include
\r
410 interaction from an interrupt - for which the tick interrupt is used via
\r
411 the tick hook function. */
\r
413 /* The full demo includes a software timer demo/test that requires
\r
414 prodding periodically from the tick interrupt. */
\r
415 vTimerPeriodicISRTests();
\r
417 /* Call the periodic event group from ISR demo. */
\r
418 vPeriodicEventGroupsProcessing();
\r
420 /* Call the code that 'gives' a task notification from an ISR. */
\r
421 xNotifyTaskFromISR();
\r