2 FreeRTOS V8.2.0rc1 - Copyright (C) 2014 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 >>! NOTE: The modification to the GPL is included to allow you to !<<
\r
14 >>! distribute a combined work that includes FreeRTOS without being !<<
\r
15 >>! obliged to provide the source code for proprietary components !<<
\r
16 >>! outside of the FreeRTOS kernel. !<<
\r
18 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
19 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
20 FOR A PARTICULAR PURPOSE. Full license text is available on the following
\r
21 link: http://www.freertos.org/a00114.html
\r
25 ***************************************************************************
\r
27 * Having a problem? Start by reading the FAQ "My application does *
\r
28 * not run, what could be wrong?". Have you defined configASSERT()? *
\r
30 * http://www.FreeRTOS.org/FAQHelp.html *
\r
32 ***************************************************************************
\r
34 ***************************************************************************
\r
36 * FreeRTOS provides completely free yet professionally developed, *
\r
37 * robust, strictly quality controlled, supported, and cross *
\r
38 * platform software that is more than just the market leader, it *
\r
39 * is the industry's de facto standard. *
\r
41 * Help yourself get started quickly while simultaneously helping *
\r
42 * to support the FreeRTOS project by purchasing a FreeRTOS *
\r
43 * tutorial book, reference manual, or both: *
\r
44 * http://www.FreeRTOS.org/Documentation *
\r
46 ***************************************************************************
\r
48 ***************************************************************************
\r
50 * Investing in training allows your team to be as productive as *
\r
51 * possible as early as possible, lowering your overall development *
\r
52 * cost, and enabling you to bring a more robust product to market *
\r
53 * earlier than would otherwise be possible. Richard Barry is both *
\r
54 * the architect and key author of FreeRTOS, and so also the world's *
\r
55 * leading authority on what is the world's most popular real time *
\r
56 * kernel for deeply embedded MCU designs. Obtaining your training *
\r
57 * from Richard ensures your team will gain directly from his in-depth *
\r
58 * product knowledge and years of usage experience. Contact Real Time *
\r
59 * Engineers Ltd to enquire about the FreeRTOS Masterclass, presented *
\r
60 * by Richard Barry: http://www.FreeRTOS.org/contact
\r
62 ***************************************************************************
\r
64 ***************************************************************************
\r
66 * You are receiving this top quality software for free. Please play *
\r
67 * fair and reciprocate by reporting any suspected issues and *
\r
68 * participating in the community forum: *
\r
69 * http://www.FreeRTOS.org/support *
\r
73 ***************************************************************************
\r
75 http://www.FreeRTOS.org - Documentation, books, training, latest versions,
\r
76 license and Real Time Engineers Ltd. contact details.
\r
78 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
79 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
80 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
82 http://www.FreeRTOS.org/labs - Where new FreeRTOS products go to incubate.
\r
83 Come and try FreeRTOS+TCP, our new open source TCP/IP stack for FreeRTOS.
\r
85 http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High
\r
86 Integrity Systems ltd. to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
87 licenses offer ticketed support, indemnification and commercial middleware.
\r
89 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
90 engineered and independently SIL3 certified version for use in safety and
\r
91 mission critical applications that require provable dependability.
\r
96 /******************************************************************************
\r
97 * This project provides two demo applications. A simple blinky style project,
\r
98 * and a more comprehensive test and demo application. The
\r
99 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in this file) is used to
\r
100 * select between the two. The simply blinky demo is implemented and described
\r
101 * in main_blinky.c. The more comprehensive test and demo application is
\r
102 * implemented and described in main_full.c.
\r
104 * This file implements the code that is not demo specific, including the
\r
105 * hardware setup and FreeRTOS hook functions.
\r
109 /* Standard includes. */
\r
112 /* Kernel includes. */
\r
113 #include "FreeRTOS.h"
\r
116 /* Standard demo includes - just needed for the LED (ParTest) initialisation
\r
118 #include "partest.h"
\r
120 /* Atmel library includes. */
\r
123 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
124 or 0 to run the more comprehensive test and demo application. */
\r
125 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 0
\r
127 /*-----------------------------------------------------------*/
\r
130 * Set up the hardware ready to run this demo.
\r
132 static void prvSetupHardware( void );
\r
135 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
136 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
138 extern void main_blinky( void );
\r
139 extern void main_full( void );
\r
141 /* Prototypes for the standard FreeRTOS callback/hook functions implemented
\r
142 within this file. */
\r
143 void vApplicationMallocFailedHook( void );
\r
144 void vApplicationIdleHook( void );
\r
145 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName );
\r
146 void vApplicationTickHook( void );
\r
148 /*-----------------------------------------------------------*/
\r
150 /* See the documentation page for this demo on the FreeRTOS.org web site for
\r
151 full information - including hardware setup requirements. */
\r
155 /* Prepare the hardware to run this demo. */
\r
156 prvSetupHardware();
\r
158 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
160 #if mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1
\r
172 /*-----------------------------------------------------------*/
\r
174 static void prvSetupHardware( void )
\r
176 extern void SystemCoreClockUpdate( void );
\r
178 /* ASF function to setup clocking. */
\r
181 /* Ensure all priority bits are assigned as preemption priority bits. */
\r
182 NVIC_SetPriorityGrouping( 0 );
\r
184 /* Atmel library function to setup for the evaluation kit being used. */
\r
187 /* Perform any configuration necessary to use the ParTest LED output
\r
189 vParTestInitialise();
\r
191 /*-----------------------------------------------------------*/
\r
193 void vApplicationMallocFailedHook( void )
\r
195 /* vApplicationMallocFailedHook() will only be called if
\r
196 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
197 function that will get called if a call to pvPortMalloc() fails.
\r
198 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
199 timer or semaphore is created. It is also called by various parts of the
\r
200 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
201 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
202 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
203 to query the size of free heap space that remains (although it does not
\r
204 provide information on how the remaining heap might be fragmented). */
\r
205 taskDISABLE_INTERRUPTS();
\r
208 /*-----------------------------------------------------------*/
\r
210 void vApplicationIdleHook( void )
\r
212 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
213 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
214 task. It is essential that code added to this hook function never attempts
\r
215 to block in any way (for example, call xQueueReceive() with a block time
\r
216 specified, or call vTaskDelay()). If the application makes use of the
\r
217 vTaskDelete() API function (as this demo application does) then it is also
\r
218 important that vApplicationIdleHook() is permitted to return to its calling
\r
219 function, because it is the responsibility of the idle task to clean up
\r
220 memory allocated by the kernel to any task that has since been deleted. */
\r
222 /*-----------------------------------------------------------*/
\r
224 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
226 ( void ) pcTaskName;
\r
229 /* Run time stack overflow checking is performed if
\r
230 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
231 function is called if a stack overflow is detected. */
\r
232 taskDISABLE_INTERRUPTS();
\r
235 /*-----------------------------------------------------------*/
\r
237 void vApplicationTickHook( void )
\r
239 /* This function will be called by each tick interrupt if
\r
240 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
241 added here, but the tick hook is called from an interrupt context, so
\r
242 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
243 functions can be used (those that end in FromISR()). */
\r
245 /*-----------------------------------------------------------*/
\r