2 FreeRTOS V7.4.0 - Copyright (C) 2013 Real Time Engineers Ltd.
\r
4 FEATURES AND PORTS ARE ADDED TO FREERTOS ALL THE TIME. PLEASE VISIT
\r
5 http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.
\r
7 ***************************************************************************
\r
9 * FreeRTOS tutorial books are available in pdf and paperback. *
\r
10 * Complete, revised, and edited pdf reference manuals are also *
\r
13 * Purchasing FreeRTOS documentation will not only help you, by *
\r
14 * ensuring you get running as quickly as possible and with an *
\r
15 * in-depth knowledge of how to use FreeRTOS, it will also help *
\r
16 * the FreeRTOS project to continue with its mission of providing *
\r
17 * professional grade, cross platform, de facto standard solutions *
\r
18 * for microcontrollers - completely free of charge! *
\r
20 * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *
\r
22 * Thank you for using FreeRTOS, and thank you for your support! *
\r
24 ***************************************************************************
\r
27 This file is part of the FreeRTOS distribution.
\r
29 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
30 the terms of the GNU General Public License (version 2) as published by the
\r
31 Free Software Foundation AND MODIFIED BY the FreeRTOS exception.
\r
33 >>>>>>NOTE<<<<<< The modification to the GPL is included to allow you to
\r
34 distribute a combined work that includes FreeRTOS without being obliged to
\r
35 provide the source code for proprietary components outside of the FreeRTOS
\r
38 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
39 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
40 FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
\r
41 details. You should have received a copy of the GNU General Public License
\r
42 and the FreeRTOS license exception along with FreeRTOS; if not itcan be
\r
43 viewed here: http://www.freertos.org/a00114.html and also obtained by
\r
44 writing to Real Time Engineers Ltd., contact details for whom are available
\r
45 on the FreeRTOS WEB site.
\r
49 ***************************************************************************
\r
51 * Having a problem? Start by reading the FAQ "My application does *
\r
52 * not run, what could be wrong?" *
\r
54 * http://www.FreeRTOS.org/FAQHelp.html *
\r
56 ***************************************************************************
\r
59 http://www.FreeRTOS.org - Documentation, books, training, latest versions,
\r
60 license and Real Time Engineers Ltd. contact details.
\r
62 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
63 including FreeRTOS+Trace - an indispensable productivity tool, and our new
\r
64 fully thread aware and reentrant UDP/IP stack.
\r
66 http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High
\r
67 Integrity Systems, who sell the code with commercial support,
\r
68 indemnification and middleware, under the OpenRTOS brand.
\r
70 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
71 engineered and independently SIL3 certified version for use in safety and
\r
72 mission critical applications that require provable dependability.
\r
75 /******************************************************************************
\r
76 * This project provides two demo applications. A simple blinky style project,
\r
77 * and a more comprehensive test and demo application. The
\r
78 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in this file) is used to
\r
79 * select between the two. The simply blinky demo is implemented and described
\r
80 * in main_blinky.c. The more comprehensive test and demo application is
\r
81 * implemented and described in main_full.c.
\r
83 * This file implements the code that is not demo specific, including the
\r
84 * hardware setup and FreeRTOS hook functions.
\r
88 /* Standard includes. */
\r
91 /* Kernel includes. */
\r
92 #include "FreeRTOS.h"
\r
95 /* Standard demo includes - just needed for the LED (ParTest) initialisation
\r
97 #include "partest.h"
\r
99 /* Atmel library includes. */
\r
102 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
103 or 0 to run the more comprehensive test and demo application. */
\r
104 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 0
\r
106 /*-----------------------------------------------------------*/
\r
109 * Set up the hardware ready to run this demo.
\r
111 static void prvSetupHardware( void );
\r
114 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
115 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
117 extern void main_blinky( void );
\r
118 extern void main_full( void );
\r
120 /* Prototypes for the standard FreeRTOS callback/hook functions implemented
\r
121 within this file. */
\r
122 void vApplicationMallocFailedHook( void );
\r
123 void vApplicationIdleHook( void );
\r
124 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName );
\r
125 void vApplicationTickHook( void );
\r
127 /*-----------------------------------------------------------*/
\r
129 /* See the documentation page for this demo on the FreeRTOS.org web site for
\r
130 full information - including hardware setup requirements. */
\r
134 /* Prepare the hardware to run this demo. */
\r
135 prvSetupHardware();
\r
137 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
139 #if mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1
\r
151 /*-----------------------------------------------------------*/
\r
153 static void prvSetupHardware( void )
\r
155 extern void SystemCoreClockUpdate( void );
\r
157 /* ASF function to setup clocking. */
\r
160 /* Ensure all priority bits are assigned as preemption priority bits. */
\r
161 NVIC_SetPriorityGrouping( 0 );
\r
163 /* Atmel library function to setup for the evaluation kit being used. */
\r
166 /* Perform any configuration necessary to use the ParTest LED output
\r
168 vParTestInitialise();
\r
170 /*-----------------------------------------------------------*/
\r
172 void vApplicationMallocFailedHook( void )
\r
174 /* vApplicationMallocFailedHook() will only be called if
\r
175 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
176 function that will get called if a call to pvPortMalloc() fails.
\r
177 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
178 timer or semaphore is created. It is also called by various parts of the
\r
179 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
180 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
181 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
182 to query the size of free heap space that remains (although it does not
\r
183 provide information on how the remaining heap might be fragmented). */
\r
184 taskDISABLE_INTERRUPTS();
\r
187 /*-----------------------------------------------------------*/
\r
189 void vApplicationIdleHook( void )
\r
191 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
192 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
193 task. It is essential that code added to this hook function never attempts
\r
194 to block in any way (for example, call xQueueReceive() with a block time
\r
195 specified, or call vTaskDelay()). If the application makes use of the
\r
196 vTaskDelete() API function (as this demo application does) then it is also
\r
197 important that vApplicationIdleHook() is permitted to return to its calling
\r
198 function, because it is the responsibility of the idle task to clean up
\r
199 memory allocated by the kernel to any task that has since been deleted. */
\r
201 /*-----------------------------------------------------------*/
\r
203 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName )
\r
205 ( void ) pcTaskName;
\r
208 /* Run time stack overflow checking is performed if
\r
209 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
210 function is called if a stack overflow is detected. */
\r
211 taskDISABLE_INTERRUPTS();
\r
214 /*-----------------------------------------------------------*/
\r
216 void vApplicationTickHook( void )
\r
218 /* This function will be called by each tick interrupt if
\r
219 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
220 added here, but the tick hook is called from an interrupt context, so
\r
221 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
222 functions can be used (those that end in FromISR()). */
\r
224 /*-----------------------------------------------------------*/
\r