2 FreeRTOS V7.1.1 - Copyright (C) 2012 Real Time Engineers Ltd.
\r
5 ***************************************************************************
\r
7 * FreeRTOS tutorial books are available in pdf and paperback. *
\r
8 * Complete, revised, and edited pdf reference manuals are also *
\r
11 * Purchasing FreeRTOS documentation will not only help you, by *
\r
12 * ensuring you get running as quickly as possible and with an *
\r
13 * in-depth knowledge of how to use FreeRTOS, it will also help *
\r
14 * the FreeRTOS project to continue with its mission of providing *
\r
15 * professional grade, cross platform, de facto standard solutions *
\r
16 * for microcontrollers - completely free of charge! *
\r
18 * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *
\r
20 * Thank you for using FreeRTOS, and thank you for your support! *
\r
22 ***************************************************************************
\r
25 This file is part of the FreeRTOS distribution.
\r
27 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
28 the terms of the GNU General Public License (version 2) as published by the
\r
29 Free Software Foundation AND MODIFIED BY the FreeRTOS exception.
\r
30 >>>NOTE<<< The modification to the GPL is included to allow you to
\r
31 distribute a combined work that includes FreeRTOS without being obliged to
\r
32 provide the source code for proprietary components outside of the FreeRTOS
\r
33 kernel. FreeRTOS is distributed in the hope that it will be useful, but
\r
34 WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
\r
35 or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
\r
36 more details. You should have received a copy of the GNU General Public
\r
37 License and the FreeRTOS license exception along with FreeRTOS; if not it
\r
38 can be viewed here: http://www.freertos.org/a00114.html and also obtained
\r
39 by writing to Richard Barry, contact details for whom are available on the
\r
44 ***************************************************************************
\r
46 * Having a problem? Start by reading the FAQ "My application does *
\r
47 * not run, what could be wrong? *
\r
49 * http://www.FreeRTOS.org/FAQHelp.html *
\r
51 ***************************************************************************
\r
54 http://www.FreeRTOS.org - Documentation, training, latest information,
\r
55 license and contact details.
\r
57 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
58 including FreeRTOS+Trace - an indispensable productivity tool.
\r
60 Real Time Engineers ltd license FreeRTOS to High Integrity Systems, who sell
\r
61 the code with commercial support, indemnification, and middleware, under
\r
62 the OpenRTOS brand: http://www.OpenRTOS.com. High Integrity Systems also
\r
63 provide a safety engineered and independently SIL3 certified version under
\r
64 the SafeRTOS brand: http://www.SafeRTOS.com.
\r
67 /******************************************************************************
\r
68 * This project provides two demo applications. A simple blinky style project,
\r
69 * and a more comprehensive test and demo application. The
\r
70 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in this file) is used to
\r
71 * select between the two. The simply blinky demo is implemented and described
\r
72 * in main_blinky.c. The more comprehensive test and demo application is
\r
73 * implemented and described in main_full.c.
\r
75 * This file implements the code that is not demo specific, including the
\r
76 * hardware setup and FreeRTOS hook functions. It also contains a dummy
\r
77 * interrupt service routine called Dummy_IRQHandler() that is provided as an
\r
78 * example of how to use interrupt safe FreeRTOS API functions (those that end
\r
81 *****************************************************************************/
\r
84 /* Standard includes. */
\r
87 /* FreeRTOS includes. */
\r
88 #include "FreeRTOS.h"
\r
91 /* Demo application include. */
\r
92 #include "ParTest.h"
\r
94 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
95 or 0 to run the more comprehensive test and demo application. */
\r
96 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 1
\r
99 /*-----------------------------------------------------------*/
\r
102 * Perform any application specific hardware configuration. The clocks,
\r
103 * memory, etc. are configured before main() is called.
\r
105 static void prvSetupHardware( void );
\r
107 /* main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
108 main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0. */
\r
109 extern void main_blinky( void );
\r
110 extern void main_full( void );
\r
112 /*-----------------------------------------------------------*/
\r
116 /* Prepare the hardware to run this demo. */
\r
117 prvSetupHardware();
\r
119 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
121 #if mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1
\r
133 /*-----------------------------------------------------------*/
\r
135 static void prvSetupHardware( void )
\r
137 vParTestInitialise();
\r
139 /*-----------------------------------------------------------*/
\r
141 void vApplicationMallocFailedHook( void )
\r
143 /* vApplicationMallocFailedHook() will only be called if
\r
144 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
145 function that will get called if a call to pvPortMalloc() fails.
\r
146 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
147 timer or semaphore is created. It is also called by various parts of the
\r
148 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
149 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
150 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
151 to query the size of free heap space that remains (although it does not
\r
152 provide information on how the remaining heap might be fragmented). */
\r
153 taskDISABLE_INTERRUPTS();
\r
156 /*-----------------------------------------------------------*/
\r
158 void vApplicationIdleHook( void )
\r
160 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
161 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
162 task. It is essential that code added to this hook function never attempts
\r
163 to block in any way (for example, call xQueueReceive() with a block time
\r
164 specified, or call vTaskDelay()). If the application makes use of the
\r
165 vTaskDelete() API function (as this demo application does) then it is also
\r
166 important that vApplicationIdleHook() is permitted to return to its calling
\r
167 function, because it is the responsibility of the idle task to clean up
\r
168 memory allocated by the kernel to any task that has since been deleted. */
\r
170 /*-----------------------------------------------------------*/
\r
172 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName )
\r
174 ( void ) pcTaskName;
\r
177 /* Run time stack overflow checking is performed if
\r
178 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
179 function is called if a stack overflow is detected. */
\r
180 taskDISABLE_INTERRUPTS();
\r
183 /*-----------------------------------------------------------*/
\r
185 void vApplicationTickHook( void )
\r
187 /* This function will be called by each tick interrupt if
\r
188 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
189 added here, but the tick hook is called from an interrupt context, so
\r
190 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
191 functions can be used (those that end in FromISR()). */
\r
193 /*-----------------------------------------------------------*/
\r
195 #ifdef JUST_AN_EXAMPLE_ISR
\r
197 void Dummy_IRQHandler(void)
\r
199 long lHigherPriorityTaskWoken = pdFALSE;
\r
201 /* Clear the interrupt if necessary. */
\r
202 Dummy_ClearITPendingBit();
\r
204 /* This interrupt does nothing more than demonstrate how to synchronise a
\r
205 task with an interrupt. A semaphore is used for this purpose. Note
\r
206 lHigherPriorityTaskWoken is initialised to zero. Only FreeRTOS API functions
\r
207 that end in "FromISR" can be called from an ISR. */
\r
208 xSemaphoreGiveFromISR( xTestSemaphore, &lHigherPriorityTaskWoken );
\r
210 /* If there was a task that was blocked on the semaphore, and giving the
\r
211 semaphore caused the task to unblock, and the unblocked task has a priority
\r
212 higher than the current Running state task (the task that this interrupt
\r
213 interrupted), then lHigherPriorityTaskWoken will have been set to pdTRUE
\r
214 internally within xSemaphoreGiveFromISR(). Passing pdTRUE into the
\r
215 portEND_SWITCHING_ISR() macro will result in a context switch being pended to
\r
216 ensure this interrupt returns directly to the unblocked, higher priority,
\r
217 task. Passing pdFALSE into portEND_SWITCHING_ISR() has no effect. */
\r
218 portEND_SWITCHING_ISR( lHigherPriorityTaskWoken );
\r
221 #endif /* JUST_AN_EXAMPLE_ISR */
\r