2 FreeRTOS V8.1.2 - Copyright (C) 2014 Real Time Engineers Ltd.
\r
5 VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.
\r
7 ***************************************************************************
\r
9 * FreeRTOS provides completely free yet professionally developed, *
\r
10 * robust, strictly quality controlled, supported, and cross *
\r
11 * platform software that has become a de facto standard. *
\r
13 * Help yourself get started quickly and support the FreeRTOS *
\r
14 * project by purchasing a FreeRTOS tutorial book, reference *
\r
15 * manual, or both from: http://www.FreeRTOS.org/Documentation *
\r
19 ***************************************************************************
\r
21 This file is part of the FreeRTOS distribution.
\r
23 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
24 the terms of the GNU General Public License (version 2) as published by the
\r
25 Free Software Foundation >>!AND MODIFIED BY!<< the FreeRTOS exception.
\r
27 >>! NOTE: The modification to the GPL is included to allow you to !<<
\r
28 >>! distribute a combined work that includes FreeRTOS without being !<<
\r
29 >>! obliged to provide the source code for proprietary components !<<
\r
30 >>! outside of the FreeRTOS kernel. !<<
\r
32 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
33 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
34 FOR A PARTICULAR PURPOSE. Full license text is available from the following
\r
35 link: http://www.freertos.org/a00114.html
\r
39 ***************************************************************************
\r
41 * Having a problem? Start by reading the FAQ "My application does *
\r
42 * not run, what could be wrong?" *
\r
44 * http://www.FreeRTOS.org/FAQHelp.html *
\r
46 ***************************************************************************
\r
48 http://www.FreeRTOS.org - Documentation, books, training, latest versions,
\r
49 license and Real Time Engineers Ltd. contact details.
\r
51 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
52 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
53 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
55 http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High
\r
56 Integrity Systems to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
57 licenses offer ticketed support, indemnification and middleware.
\r
59 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
60 engineered and independently SIL3 certified version for use in safety and
\r
61 mission critical applications that require provable dependability.
\r
66 /******************************************************************************
\r
67 * NOTE 1: This project provides three demo applications. A simple blinky
\r
68 * style project, a more comprehensive test and demo application, and an
\r
69 * lwIP example. The mainSELECTED_APPLICATION setting in main.c is used to
\r
70 * select between the three. See the notes on using mainSELECTED_APPLICATION
\r
71 * in main.c. This file implements the comprehensive version.
\r
73 * NOTE 2: This file only contains the source code that is specific to the
\r
74 * full demo. Generic functions, such FreeRTOS hook functions, and functions
\r
75 * required to configure the hardware, are defined in main.c.
\r
77 * NOTE 3: The full demo includes a test that checks the floating point context
\r
78 * is maintained correctly across task switches. The standard GCC libraries can
\r
79 * use floating point registers and made this test fail (unless the tasks that
\r
80 * use the library are given a floating point context as described on the
\r
81 * documentation page for this demo). printf-stdarg.c is included in this
\r
82 * project to prevent the standard GCC libraries being linked into the project.
\r
84 ******************************************************************************
\r
86 * main_full() creates all the demo application tasks and software timers, then
\r
87 * starts the scheduler. The web documentation provides more details of the
\r
88 * standard demo application tasks, which provide no particular functionality,
\r
89 * but do provide a good example of how to use the FreeRTOS API.
\r
91 * In addition to the standard demo tasks, the following tasks and tests are
\r
92 * defined and/or created within this file:
\r
94 * FreeRTOS+CLI command console. The command console is access through the
\r
95 * UART to USB connector on the ZC702 Zynq development board (marked J2). For
\r
96 * reasons of robustness testing the UART driver is deliberately written to be
\r
97 * inefficient and should not be used as a template for a production driver.
\r
98 * Type "help" to see a list of registered commands. The FreeRTOS+CLI license
\r
99 * is different to the FreeRTOS license, see http://www.FreeRTOS.org/cli for
\r
100 * license and usage details. The default baud rate is 115200.
\r
102 * "Reg test" tasks - These fill both the core and floating point registers with
\r
103 * known values, then check that each register maintains its expected value for
\r
104 * the lifetime of the task. Each task uses a different set of values. The reg
\r
105 * test tasks execute with a very low priority, so get preempted very
\r
106 * frequently. A register containing an unexpected value is indicative of an
\r
107 * error in the context switching mechanism.
\r
109 * "Check" task - The check task period is initially set to three seconds. The
\r
110 * task checks that all the standard demo tasks, and the register check tasks,
\r
111 * are not only still executing, but are executing without reporting any errors.
\r
112 * If the check task discovers that a task has either stalled, or reported an
\r
113 * error, then it changes its own execution period from the initial three
\r
114 * seconds, to just 200ms. The check task also toggles an LED each time it is
\r
115 * called. This provides a visual indication of the system status: If the LED
\r
116 * toggles every three seconds, then no issues have been discovered. If the LED
\r
117 * toggles every 200ms, then an issue has been discovered with at least one
\r
121 /* Standard includes. */
\r
124 /* Kernel includes. */
\r
125 #include "FreeRTOS.h"
\r
127 #include "timers.h"
\r
128 #include "semphr.h"
\r
130 /* Standard demo application includes. */
\r
132 #include "semtest.h"
\r
133 #include "dynamic.h"
\r
134 #include "BlockQ.h"
\r
135 #include "blocktim.h"
\r
136 #include "countsem.h"
\r
137 #include "GenQTest.h"
\r
138 #include "recmutex.h"
\r
140 #include "partest.h"
\r
141 #include "comtest2.h"
\r
142 #include "serial.h"
\r
143 #include "TimerDemo.h"
\r
144 #include "QueueOverwrite.h"
\r
145 #include "IntQueue.h"
\r
146 #include "EventGroupsDemo.h"
\r
148 /* Priorities for the demo application tasks. */
\r
149 #define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1UL )
\r
150 #define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2UL )
\r
151 #define mainCREATOR_TASK_PRIORITY ( tskIDLE_PRIORITY + 3UL )
\r
152 #define mainFLOP_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
153 #define mainUART_COMMAND_CONSOLE_STACK_SIZE ( configMINIMAL_STACK_SIZE * 3UL )
\r
154 #define mainCOM_TEST_TASK_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
155 #define mainCHECK_TASK_PRIORITY ( configMAX_PRIORITIES - 1 )
\r
156 #define mainQUEUE_OVERWRITE_PRIORITY ( tskIDLE_PRIORITY )
\r
158 /* The priority used by the UART command console task. */
\r
159 #define mainUART_COMMAND_CONSOLE_TASK_PRIORITY ( configMAX_PRIORITIES - 2 )
\r
161 /* The LED used by the check timer. */
\r
162 #define mainCHECK_LED ( 0 )
\r
164 /* A block time of zero simply means "don't block". */
\r
165 #define mainDONT_BLOCK ( 0UL )
\r
167 /* The period after which the check timer will expire, in ms, provided no errors
\r
168 have been reported by any of the standard demo tasks. ms are converted to the
\r
169 equivalent in ticks using the portTICK_PERIOD_MS constant. */
\r
170 #define mainNO_ERROR_CHECK_TASK_PERIOD ( 3000UL / portTICK_PERIOD_MS )
\r
172 /* The period at which the check timer will expire, in ms, if an error has been
\r
173 reported in one of the standard demo tasks. ms are converted to the equivalent
\r
174 in ticks using the portTICK_PERIOD_MS constant. */
\r
175 #define mainERROR_CHECK_TASK_PERIOD ( 200UL / portTICK_PERIOD_MS )
\r
177 /* Parameters that are passed into the register check tasks solely for the
\r
178 purpose of ensuring parameters are passed into tasks correctly. */
\r
179 #define mainREG_TEST_TASK_1_PARAMETER ( ( void * ) 0x12345678 )
\r
180 #define mainREG_TEST_TASK_2_PARAMETER ( ( void * ) 0x87654321 )
\r
182 /* The base period used by the timer test tasks. */
\r
183 #define mainTIMER_TEST_PERIOD ( 50 )
\r
185 /*-----------------------------------------------------------*/
\r
189 * The check task, as described at the top of this file.
\r
191 static void prvCheckTask( void *pvParameters );
\r
194 * Register check tasks, and the tasks used to write over and check the contents
\r
195 * of the FPU registers, as described at the top of this file. The nature of
\r
196 * these files necessitates that they are written in an assembly file, but the
\r
197 * entry points are kept in the C file for the convenience of checking the task
\r
200 static void prvRegTestTaskEntry1( void *pvParameters );
\r
201 extern void vRegTest1Implementation( void );
\r
202 static void prvRegTestTaskEntry2( void *pvParameters );
\r
203 extern void vRegTest2Implementation( void );
\r
206 * Register commands that can be used with FreeRTOS+CLI. The commands are
\r
207 * defined in CLI-Commands.c and File-Related-CLI-Command.c respectively.
\r
209 extern void vRegisterSampleCLICommands( void );
\r
212 * The task that manages the FreeRTOS+CLI input and output.
\r
214 extern void vUARTCommandConsoleStart( uint16_t usStackSize, UBaseType_t uxPriority );
\r
217 * A high priority task that does nothing other than execute at a pseudo random
\r
218 * time to ensure the other test tasks don't just execute in a repeating
\r
221 static void prvPseudoRandomiser( void *pvParameters );
\r
223 /*-----------------------------------------------------------*/
\r
225 /* The following two variables are used to communicate the status of the
\r
226 register check tasks to the check task. If the variables keep incrementing,
\r
227 then the register check tasks has not discovered any errors. If a variable
\r
228 stops incrementing, then an error has been found. */
\r
229 volatile unsigned long ulRegTest1LoopCounter = 0UL, ulRegTest2LoopCounter = 0UL;
\r
231 /* String for display in the web server. It is set to an error message if the
\r
232 check task detects an error. */
\r
233 char *pcStatusMessage = "All tasks running without error";
\r
234 /*-----------------------------------------------------------*/
\r
236 void main_full( void )
\r
238 /* Start all the other standard demo/test tasks. They have not particular
\r
239 functionality, but do demonstrate how to use the FreeRTOS API and test the
\r
241 vStartInterruptQueueTasks();
\r
242 vStartDynamicPriorityTasks();
\r
243 vStartBlockingQueueTasks( mainBLOCK_Q_PRIORITY );
\r
244 vCreateBlockTimeTasks();
\r
245 vStartCountingSemaphoreTasks();
\r
246 vStartGenericQueueTasks( tskIDLE_PRIORITY );
\r
247 vStartRecursiveMutexTasks();
\r
248 vStartSemaphoreTasks( mainSEM_TEST_PRIORITY );
\r
249 vStartMathTasks( mainFLOP_TASK_PRIORITY );
\r
250 vStartTimerDemoTask( mainTIMER_TEST_PERIOD );
\r
251 vStartQueueOverwriteTask( mainQUEUE_OVERWRITE_PRIORITY );
\r
252 vStartEventGroupTasks();
\r
254 /* Start the tasks that implements the command console on the UART, as
\r
255 described above. */
\r
256 vUARTCommandConsoleStart( mainUART_COMMAND_CONSOLE_STACK_SIZE, mainUART_COMMAND_CONSOLE_TASK_PRIORITY );
\r
258 /* Register the standard CLI commands. */
\r
259 vRegisterSampleCLICommands();
\r
261 /* Create the register check tasks, as described at the top of this file */
\r
262 xTaskCreate( prvRegTestTaskEntry1, "Reg1", configMINIMAL_STACK_SIZE, mainREG_TEST_TASK_1_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
263 xTaskCreate( prvRegTestTaskEntry2, "Reg2", configMINIMAL_STACK_SIZE, mainREG_TEST_TASK_2_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
265 /* Create the task that just adds a little random behaviour. */
\r
266 xTaskCreate( prvPseudoRandomiser, "Rnd", configMINIMAL_STACK_SIZE, NULL, configMAX_PRIORITIES - 1, NULL );
\r
268 /* Create the task that performs the 'check' functionality, as described at
\r
269 the top of this file. */
\r
270 xTaskCreate( prvCheckTask, "Check", configMINIMAL_STACK_SIZE, NULL, mainCHECK_TASK_PRIORITY, NULL );
\r
272 /* The set of tasks created by the following function call have to be
\r
273 created last as they keep account of the number of tasks they expect to see
\r
275 vCreateSuicidalTasks( mainCREATOR_TASK_PRIORITY );
\r
277 /* Start the scheduler. */
\r
278 vTaskStartScheduler();
\r
280 /* If all is well, the scheduler will now be running, and the following
\r
281 line will never be reached. If the following line does execute, then
\r
282 there was either insufficient FreeRTOS heap memory available for the idle
\r
283 and/or timer tasks to be created, or vTaskStartScheduler() was called from
\r
284 User mode. See the memory management section on the FreeRTOS web site for
\r
285 more details on the FreeRTOS heap http://www.freertos.org/a00111.html. The
\r
286 mode from which main() is called is set in the C start up code and must be
\r
287 a privileged mode (not user mode). */
\r
290 /*-----------------------------------------------------------*/
\r
292 static void prvCheckTask( void *pvParameters )
\r
294 TickType_t xDelayPeriod = mainNO_ERROR_CHECK_TASK_PERIOD;
\r
295 TickType_t xLastExecutionTime;
\r
296 static unsigned long ulLastRegTest1Value = 0, ulLastRegTest2Value = 0;
\r
297 unsigned long ulErrorFound = pdFALSE;
\r
299 /* Just to stop compiler warnings. */
\r
300 ( void ) pvParameters;
\r
302 /* Initialise xLastExecutionTime so the first call to vTaskDelayUntil()
\r
303 works correctly. */
\r
304 xLastExecutionTime = xTaskGetTickCount();
\r
306 /* Cycle for ever, delaying then checking all the other tasks are still
\r
307 operating without error. The onboard LED is toggled on each iteration.
\r
308 If an error is detected then the delay period is decreased from
\r
309 mainNO_ERROR_CHECK_TASK_PERIOD to mainERROR_CHECK_TASK_PERIOD. This has the
\r
310 effect of increasing the rate at which the onboard LED toggles, and in so
\r
311 doing gives visual feedback of the system status. */
\r
314 /* Delay until it is time to execute again. */
\r
315 vTaskDelayUntil( &xLastExecutionTime, xDelayPeriod );
\r
317 /* Check all the demo tasks (other than the flash tasks) to ensure
\r
318 that they are all still running, and that none have detected an error. */
\r
319 if( xAreIntQueueTasksStillRunning() != pdTRUE )
\r
321 ulErrorFound = pdTRUE;
\r
324 if( xAreMathsTaskStillRunning() != pdTRUE )
\r
326 ulErrorFound = pdTRUE;
\r
329 if( xAreDynamicPriorityTasksStillRunning() != pdTRUE )
\r
331 ulErrorFound = pdTRUE;
\r
334 if( xAreBlockingQueuesStillRunning() != pdTRUE )
\r
336 ulErrorFound = pdTRUE;
\r
339 if ( xAreBlockTimeTestTasksStillRunning() != pdTRUE )
\r
341 ulErrorFound = pdTRUE;
\r
344 if ( xAreGenericQueueTasksStillRunning() != pdTRUE )
\r
346 ulErrorFound = pdTRUE;
\r
349 if ( xAreRecursiveMutexTasksStillRunning() != pdTRUE )
\r
351 ulErrorFound = pdTRUE;
\r
354 if( xIsCreateTaskStillRunning() != pdTRUE )
\r
356 ulErrorFound = pdTRUE;
\r
359 if( xAreSemaphoreTasksStillRunning() != pdTRUE )
\r
361 ulErrorFound = pdTRUE;
\r
364 if( xAreTimerDemoTasksStillRunning( ( TickType_t ) mainNO_ERROR_CHECK_TASK_PERIOD ) != pdPASS )
\r
366 ulErrorFound = pdTRUE;
\r
369 if( xAreCountingSemaphoreTasksStillRunning() != pdTRUE )
\r
371 ulErrorFound = pdTRUE;
\r
374 if( xIsQueueOverwriteTaskStillRunning() != pdPASS )
\r
376 ulErrorFound = pdTRUE;
\r
379 if( xAreEventGroupTasksStillRunning() != pdPASS )
\r
381 ulErrorFound = pdTRUE;
\r
384 /* Check that the register test 1 task is still running. */
\r
385 if( ulLastRegTest1Value == ulRegTest1LoopCounter )
\r
387 ulErrorFound = pdTRUE;
\r
389 ulLastRegTest1Value = ulRegTest1LoopCounter;
\r
391 /* Check that the register test 2 task is still running. */
\r
392 if( ulLastRegTest2Value == ulRegTest2LoopCounter )
\r
394 ulErrorFound = pdTRUE;
\r
396 ulLastRegTest2Value = ulRegTest2LoopCounter;
\r
398 /* Toggle the check LED to give an indication of the system status. If
\r
399 the LED toggles every mainNO_ERROR_CHECK_TASK_PERIOD milliseconds then
\r
400 everything is ok. A faster toggle indicates an error. */
\r
401 vParTestToggleLED( mainCHECK_LED );
\r
403 if( ulErrorFound != pdFALSE )
\r
405 /* An error has been detected in one of the tasks - flash the LED
\r
406 at a higher frequency to give visible feedback that something has
\r
407 gone wrong (it might just be that the loop back connector required
\r
408 by the comtest tasks has not been fitted). */
\r
409 xDelayPeriod = mainERROR_CHECK_TASK_PERIOD;
\r
410 pcStatusMessage = "Error found in at least one task.";
\r
414 /*-----------------------------------------------------------*/
\r
416 char *pcMainGetTaskStatusMessage( void )
\r
418 return pcStatusMessage;
\r
420 /*-----------------------------------------------------------*/
\r
422 static void prvRegTestTaskEntry1( void *pvParameters )
\r
424 /* Although the regtest task is written in assembler, its entry point is
\r
425 written in C for convenience of checking the task parameter is being passed
\r
427 if( pvParameters == mainREG_TEST_TASK_1_PARAMETER )
\r
429 /* The reg test task also tests the floating point registers. Tasks
\r
430 that use the floating point unit must call vPortTaskUsesFPU() before
\r
431 any floating point instructions are executed. */
\r
432 vPortTaskUsesFPU();
\r
434 /* Start the part of the test that is written in assembler. */
\r
435 vRegTest1Implementation();
\r
438 /* The following line will only execute if the task parameter is found to
\r
439 be incorrect. The check timer will detect that the regtest loop counter is
\r
440 not being incremented and flag an error. */
\r
441 vTaskDelete( NULL );
\r
443 /*-----------------------------------------------------------*/
\r
445 static void prvRegTestTaskEntry2( void *pvParameters )
\r
447 /* Although the regtest task is written in assembler, its entry point is
\r
448 written in C for convenience of checking the task parameter is being passed
\r
450 if( pvParameters == mainREG_TEST_TASK_2_PARAMETER )
\r
452 /* The reg test task also tests the floating point registers. Tasks
\r
453 that use the floating point unit must call vPortTaskUsesFPU() before
\r
454 any floating point instructions are executed. */
\r
455 vPortTaskUsesFPU();
\r
457 /* Start the part of the test that is written in assembler. */
\r
458 vRegTest2Implementation();
\r
461 /* The following line will only execute if the task parameter is found to
\r
462 be incorrect. The check timer will detect that the regtest loop counter is
\r
463 not being incremented and flag an error. */
\r
464 vTaskDelete( NULL );
\r
466 /*-----------------------------------------------------------*/
\r
468 static void prvPseudoRandomiser( void *pvParameters )
\r
470 const uint32_t ulMultiplier = 0x015a4e35UL, ulIncrement = 1UL, ulMinDelay = ( 35 / portTICK_PERIOD_MS );
\r
471 volatile uint32_t ulNextRand = ( uint32_t ) &pvParameters, ulValue;
\r
473 /* This task does nothing other than ensure there is a little bit of
\r
474 disruption in the scheduling pattern of the other tasks. Normally this is
\r
475 done by generating interrupts at pseudo random times. */
\r
478 ulNextRand = ( ulMultiplier * ulNextRand ) + ulIncrement;
\r
479 ulValue = ( ulNextRand >> 16UL ) & 0xffUL;
\r
481 if( ulValue < ulMinDelay )
\r
483 ulValue = ulMinDelay;
\r
486 vTaskDelay( ulValue );
\r
488 while( ulValue > 0 )
\r
490 __asm volatile( "NOP" );
\r
491 __asm volatile( "NOP" );
\r
492 __asm volatile( "NOP" );
\r
493 __asm volatile( "NOP" );
\r