2 FreeRTOS V7.4.2 - 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 it can 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
76 FreeRTOS V7.4.2 - Copyright (C) 2013 Real Time Engineers Ltd.
\r
78 FEATURES AND PORTS ARE ADDED TO FREERTOS ALL THE TIME. PLEASE VISIT
\r
79 http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.
\r
81 ***************************************************************************
\r
83 * FreeRTOS tutorial books are available in pdf and paperback. *
\r
84 * Complete, revised, and edited pdf reference manuals are also *
\r
87 * Purchasing FreeRTOS documentation will not only help you, by *
\r
88 * ensuring you get running as quickly as possible and with an *
\r
89 * in-depth knowledge of how to use FreeRTOS, it will also help *
\r
90 * the FreeRTOS project to continue with its mission of providing *
\r
91 * professional grade, cross platform, de facto standard solutions *
\r
92 * for microcontrollers - completely free of charge! *
\r
94 * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *
\r
96 * Thank you for using FreeRTOS, and thank you for your support! *
\r
98 ***************************************************************************
\r
101 This file is part of the FreeRTOS distribution.
\r
103 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
104 the terms of the GNU General Public License (version 2) as published by the
\r
105 Free Software Foundation AND MODIFIED BY the FreeRTOS exception.
\r
107 >>>>>>NOTE<<<<<< The modification to the GPL is included to allow you to
\r
108 distribute a combined work that includes FreeRTOS without being obliged to
\r
109 provide the source code for proprietary components outside of the FreeRTOS
\r
112 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
113 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
114 FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
\r
115 details. You should have received a copy of the GNU General Public License
\r
116 and the FreeRTOS license exception along with FreeRTOS; if not it can be
\r
117 viewed here: http://www.freertos.org/a00114.html and also obtained by
\r
118 writing to Real Time Engineers Ltd., contact details for whom are available
\r
119 on the FreeRTOS WEB site.
\r
123 ***************************************************************************
\r
125 * Having a problem? Start by reading the FAQ "My application does *
\r
126 * not run, what could be wrong?" *
\r
128 * http://www.FreeRTOS.org/FAQHelp.html *
\r
130 ***************************************************************************
\r
133 http://www.FreeRTOS.org - Documentation, books, training, latest versions,
\r
134 license and Real Time Engineers Ltd. contact details.
\r
136 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
137 including FreeRTOS+Trace - an indispensable productivity tool, and our new
\r
138 fully thread aware and reentrant UDP/IP stack.
\r
140 http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High
\r
141 Integrity Systems, who sell the code with commercial support,
\r
142 indemnification and middleware, under the OpenRTOS brand.
\r
144 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
145 engineered and independently SIL3 certified version for use in safety and
\r
146 mission critical applications that require provable dependability.
\r
149 /******************************************************************************
\r
150 * This project provides two demo applications. A low power project that
\r
151 * demonstrates the FreeRTOS tickless mode, and a more comprehensive test and
\r
152 * demo application. The configCREATE_LOW_POWER_DEMO setting (defined at the
\r
153 * top of FreeRTOSConfig.h) is used to select between the two. The low power
\r
154 * demo is implemented and described in main_low_power.c. The more
\r
155 * comprehensive test and demo application is implemented and described in
\r
158 * This file implements the code that is not demo specific, including the
\r
159 * hardware setup and FreeRTOS hook functions.
\r
162 /* Standard includes. */
\r
165 /* Kernel includes. */
\r
166 #include "FreeRTOS.h"
\r
169 /* Standard demo includes - just needed for the LED (ParTest) initialisation
\r
171 #include "partest.h"
\r
173 /* Atmel library includes. */
\r
176 /*-----------------------------------------------------------*/
\r
179 * Set up the hardware ready to run this demo.
\r
181 static void prvSetupHardware( void );
\r
184 * main_low_power() is used when configCREATE_LOW_POWER_DEMO is set to 1.
\r
185 * main_full() is used when configCREATE_LOW_POWER_DEMO is set to 0.
\r
186 * configCREATE_LOW_POWER_DEMO is defined at the top of main.c.
\r
188 extern void main_low_power( void );
\r
189 extern void main_full( void );
\r
191 /* Prototypes for the standard FreeRTOS callback/hook functions implemented
\r
192 within this file. */
\r
193 void vApplicationMallocFailedHook( void );
\r
194 void vApplicationIdleHook( void );
\r
195 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName );
\r
196 void vApplicationTickHook( void );
\r
198 /*-----------------------------------------------------------*/
\r
200 /* See the documentation page for this demo on the FreeRTOS.org web site for
\r
201 full information - including hardware setup requirements. */
\r
204 /* Prepare the hardware to run this demo. */
\r
205 prvSetupHardware();
\r
207 /* The configCREATE_LOW_POWER_DEMO setting is described at the top of
\r
209 #if configCREATE_LOW_POWER_DEMO == 1
\r
221 /*-----------------------------------------------------------*/
\r
223 static void prvSetupHardware( void )
\r
225 extern void SystemCoreClockUpdate( void );
\r
227 /* ASF function to setup clocking. */
\r
230 /* Ensure all priority bits are assigned as preemption priority bits. */
\r
231 NVIC_SetPriorityGrouping( 0 );
\r
233 /* Atmel library function to setup for the evaluation kit being used. */
\r
236 /* Initialise the sleep manager in case the low power demo is being used. */
\r
239 /*-----------------------------------------------------------*/
\r
241 void vApplicationMallocFailedHook( void )
\r
243 /* vApplicationMallocFailedHook() will only be called if
\r
244 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
245 function that will get called if a call to pvPortMalloc() fails.
\r
246 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
247 timer or semaphore is created. It is also called by various parts of the
\r
248 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
249 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
250 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
251 to query the size of free heap space that remains (although it does not
\r
252 provide information on how the remaining heap might be fragmented). */
\r
253 taskDISABLE_INTERRUPTS();
\r
256 /*-----------------------------------------------------------*/
\r
258 void vApplicationIdleHook( void )
\r
260 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
261 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
262 task. It is essential that code added to this hook function never attempts
\r
263 to block in any way (for example, call xQueueReceive() with a block time
\r
264 specified, or call vTaskDelay()). If the application makes use of the
\r
265 vTaskDelete() API function (as this demo application does) then it is also
\r
266 important that vApplicationIdleHook() is permitted to return to its calling
\r
267 function, because it is the responsibility of the idle task to clean up
\r
268 memory allocated by the kernel to any task that has since been deleted. */
\r
270 /*-----------------------------------------------------------*/
\r
272 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName )
\r
274 ( void ) pcTaskName;
\r
277 /* Run time stack overflow checking is performed if
\r
278 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
279 function is called if a stack overflow is detected. */
\r
280 taskDISABLE_INTERRUPTS();
\r
283 /*-----------------------------------------------------------*/
\r
285 void vApplicationTickHook( void )
\r
287 /* This function will be called by each tick interrupt if
\r
288 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
289 added here, but the tick hook is called from an interrupt context, so
\r
290 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
291 functions can be used (those that end in FromISR()). */
\r
293 /*-----------------------------------------------------------*/
\r
295 void vAssertCalled( void )
\r
297 volatile unsigned long ul = 0;
\r
299 taskENTER_CRITICAL();
\r
301 /* Set ul to a non-zero value using the debugger to step out of this
\r
305 __asm volatile( "NOP" );
\r
308 taskEXIT_CRITICAL();
\r