2 FreeRTOS V8.2.0 - 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
71 NOTE : Tasks run in system mode and the scheduler runs in Supervisor mode.
\r
72 The processor MUST be in supervisor mode when vTaskStartScheduler is
\r
73 called. The demo applications included in the FreeRTOS.org download switch
\r
74 to supervisor mode prior to main being called. If you are not using one of
\r
75 these demo application projects then ensure Supervisor mode is used.
\r
80 * Creates all the demo application tasks, then starts the scheduler. The WEB
\r
81 * documentation provides more details of the demo application tasks.
\r
83 * Main.c also creates a task called "Check". This only executes every three
\r
84 * seconds but has the highest priority so is guaranteed to get processor time.
\r
85 * Its main function is to check that all the other tasks are still operational.
\r
86 * Each task (other than the "flash" tasks) maintains a unique count that is
\r
87 * incremented each time the task successfully completes its function. Should
\r
88 * any error occur within such a task the count is permanently halted. The
\r
89 * check task inspects the count of each task to ensure it has changed since
\r
90 * the last time the check task executed. If all the count variables have
\r
91 * changed all the tasks are still executing error free, and the check task
\r
92 * toggles the onboard LED. Should any task contain an error at any time
\r
93 * the LED toggle rate will change from 3 seconds to 500ms.
\r
97 /* Standard includes. */
\r
100 /* Scheduler includes. */
\r
101 #include "FreeRTOS.h"
\r
104 /* Demo application includes. */
\r
105 #include "partest.h"
\r
107 #include "comtest2.h"
\r
108 #include "serial.h"
\r
110 #include "BlockQ.h"
\r
111 #include "semtest.h"
\r
112 #include "dynamic.h"
\r
114 /*-----------------------------------------------------------*/
\r
116 /* Constants to setup I/O and processor. */
\r
117 #define mainTX_ENABLE ( ( unsigned long ) 0x00010000 ) /* UART1. */
\r
118 #define mainRX_ENABLE ( ( unsigned long ) 0x00040000 ) /* UART1. */
\r
119 #define mainBUS_CLK_FULL ( ( unsigned char ) 0x01 )
\r
120 #define mainLED_TO_OUTPUT ( ( unsigned long ) 0xff0000 )
\r
122 /* Constants for the ComTest demo application tasks. */
\r
123 #define mainCOM_TEST_BAUD_RATE ( ( unsigned long ) 115200 )
\r
124 #define mainCOM_TEST_LED ( 3 )
\r
126 /* Priorities for the demo application tasks. */
\r
127 #define mainLED_TASK_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
128 #define mainCOM_TEST_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
129 #define mainQUEUE_POLL_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
130 #define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
131 #define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
132 #define mainCHECK_TASK_PRIORITY ( tskIDLE_PRIORITY + 3 )
\r
134 /* Constants used by the "check" task. As described at the head of this file
\r
135 the check task toggles an LED. The rate at which the LED flashes is used to
\r
136 indicate whether an error has been detected or not. If the LED toggles every
\r
137 3 seconds then no errors have been detected. If the rate increases to 500ms
\r
138 then an error has been detected in at least one of the demo application tasks. */
\r
139 #define mainCHECK_LED ( 7 )
\r
140 #define mainNO_ERROR_FLASH_PERIOD ( ( TickType_t ) 3000 / portTICK_PERIOD_MS )
\r
141 #define mainERROR_FLASH_PERIOD ( ( TickType_t ) 500 / portTICK_PERIOD_MS )
\r
143 /*-----------------------------------------------------------*/
\r
146 * Checks that all the demo application tasks are still executing without error
\r
147 * - as described at the top of the file.
\r
149 static long prvCheckOtherTasksAreStillRunning( void );
\r
152 * The task that executes at the highest priority and calls
\r
153 * prvCheckOtherTasksAreStillRunning(). See the description at the top
\r
156 static void vErrorChecks( void *pvParameters );
\r
159 * Configure the processor for use with the Keil demo board. This is very
\r
160 * minimal as most of the setup is managed by the settings in the project
\r
163 static void prvSetupHardware( void );
\r
165 /*-----------------------------------------------------------*/
\r
170 * Application entry point:
\r
171 * Starts all the other tasks, then starts the scheduler.
\r
175 /* Setup the hardware for use with the Keil demo board. */
\r
176 prvSetupHardware();
\r
178 /* Start the demo/test application tasks. */
\r
179 vAltStartComTestTasks( mainCOM_TEST_PRIORITY, mainCOM_TEST_BAUD_RATE, mainCOM_TEST_LED );
\r
180 vStartLEDFlashTasks( mainLED_TASK_PRIORITY );
\r
181 vStartPolledQueueTasks( mainQUEUE_POLL_PRIORITY );
\r
182 vStartBlockingQueueTasks( mainBLOCK_Q_PRIORITY );
\r
183 vStartSemaphoreTasks( mainSEM_TEST_PRIORITY );
\r
184 vStartDynamicPriorityTasks();
\r
186 /* Start the check task - which is defined in this file. This is the task
\r
187 that periodically checks to see that all the other tasks are executing
\r
189 xTaskCreate( vErrorChecks, "Check", configMINIMAL_STACK_SIZE, NULL, mainCHECK_TASK_PRIORITY, NULL );
\r
191 /* Now all the tasks have been started - start the scheduler.
\r
193 NOTE : Tasks run in system mode and the scheduler runs in Supervisor mode.
\r
194 The processor MUST be in supervisor mode when vTaskStartScheduler is
\r
195 called. The demo applications included in the FreeRTOS.org download switch
\r
196 to supervisor mode prior to main being called. If you are not using one of
\r
197 these demo application projects then ensure Supervisor mode is used here. */
\r
198 vTaskStartScheduler();
\r
200 /* Should never reach here! If you do then there was not enough heap
\r
201 available for the idle task to be created. */
\r
204 /*-----------------------------------------------------------*/
\r
206 static void vErrorChecks( void *pvParameters )
\r
208 TickType_t xDelayPeriod = mainNO_ERROR_FLASH_PERIOD;
\r
210 /* Parameters are not used. */
\r
211 ( void ) pvParameters;
\r
213 /* Cycle for ever, delaying then checking all the other tasks are still
\r
214 operating without error. If an error is detected then the delay period
\r
215 is decreased from mainNO_ERROR_FLASH_PERIOD to mainERROR_FLASH_PERIOD so
\r
216 the on board LED flash rate will increase.
\r
218 This task runs at the highest priority. */
\r
222 /* The period of the delay depends on whether an error has been
\r
223 detected or not. If an error has been detected then the period
\r
224 is reduced to increase the LED flash rate. */
\r
225 vTaskDelay( xDelayPeriod );
\r
227 if( prvCheckOtherTasksAreStillRunning() != pdPASS )
\r
229 /* An error has been detected in one of the tasks - flash faster. */
\r
230 xDelayPeriod = mainERROR_FLASH_PERIOD;
\r
233 /* Toggle the LED before going back to wait for the next cycle. */
\r
234 vParTestToggleLED( mainCHECK_LED );
\r
237 /*-----------------------------------------------------------*/
\r
239 static void prvSetupHardware( void )
\r
241 /* Perform the hardware setup required. This is minimal as most of the
\r
242 setup is managed by the settings in the project file. */
\r
244 /* Configure the UART1 pins. All other pins remain at their default of 0. */
\r
245 PINSEL0 |= mainTX_ENABLE;
\r
246 PINSEL0 |= mainRX_ENABLE;
\r
248 /* LED pins need to be output. */
\r
249 IODIR1 = mainLED_TO_OUTPUT;
\r
251 /* Setup the peripheral bus to be the same as the PLL output. */
\r
252 VPBDIV = mainBUS_CLK_FULL;
\r
254 /*-----------------------------------------------------------*/
\r
256 static long prvCheckOtherTasksAreStillRunning( void )
\r
258 long lReturn = pdPASS;
\r
260 /* Check all the demo tasks (other than the flash tasks) to ensure
\r
261 that they are all still running, and that none of them have detected
\r
263 if( xAreComTestTasksStillRunning() != pdPASS )
\r
268 if( xArePollingQueuesStillRunning() != pdTRUE )
\r
273 if( xAreBlockingQueuesStillRunning() != pdTRUE )
\r
278 if( xAreSemaphoreTasksStillRunning() != pdTRUE )
\r
283 if( xAreDynamicPriorityTasksStillRunning() != pdTRUE )
\r
290 /*-----------------------------------------------------------*/
\r