2 FreeRTOS V7.5.0 - Copyright (C) 2013 Real Time Engineers Ltd.
\r
4 VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.
\r
6 ***************************************************************************
\r
8 * FreeRTOS provides completely free yet professionally developed, *
\r
9 * robust, strictly quality controlled, supported, and cross *
\r
10 * platform software that has become a de facto standard. *
\r
12 * Help yourself get started quickly and support the FreeRTOS *
\r
13 * project by purchasing a FreeRTOS tutorial book, reference *
\r
14 * manual, or both from: http://www.FreeRTOS.org/Documentation *
\r
18 ***************************************************************************
\r
20 This file is part of the FreeRTOS distribution.
\r
22 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
23 the terms of the GNU General Public License (version 2) as published by the
\r
24 Free Software Foundation >>!AND MODIFIED BY!<< the FreeRTOS exception.
\r
26 >>! NOTE: The modification to the GPL is included to allow you to distribute
\r
27 >>! a combined work that includes FreeRTOS without being obliged to provide
\r
28 >>! the source code for proprietary components outside of the FreeRTOS
\r
31 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
32 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
33 FOR A PARTICULAR PURPOSE. Full license text is available from the following
\r
34 link: http://www.freertos.org/a00114.html
\r
38 ***************************************************************************
\r
40 * Having a problem? Start by reading the FAQ "My application does *
\r
41 * not run, what could be wrong?" *
\r
43 * http://www.FreeRTOS.org/FAQHelp.html *
\r
45 ***************************************************************************
\r
47 http://www.FreeRTOS.org - Documentation, books, training, latest versions,
\r
48 license and Real Time Engineers Ltd. contact details.
\r
50 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
51 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
52 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
54 http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High
\r
55 Integrity Systems to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
56 licenses offer ticketed support, indemnification and middleware.
\r
58 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
59 engineered and independently SIL3 certified version for use in safety and
\r
60 mission critical applications that require provable dependability.
\r
65 /******************************************************************************
\r
66 * This project provides two demo applications. A simple blinky style project,
\r
67 * and a more comprehensive test and demo application. The
\r
68 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in this file) is used to
\r
69 * select between the two. The simply blinky demo is implemented and described
\r
70 * in main_blinky.c. The more comprehensive test and demo application is
\r
71 * implemented and described in main_full.c.
\r
73 * This file implements the code that is not demo specific, including the
\r
74 * hardware setup and FreeRTOS hook functions.
\r
78 /* Standard includes. */
\r
81 /* Kernel includes. */
\r
82 #include "FreeRTOS.h"
\r
85 /* Standard demo includes. */
\r
86 #include "partest.h"
\r
87 #include "QueueSet.h"
\r
89 /* Atmel library includes. */
\r
92 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
93 or 0 to run the more comprehensive test and demo application. */
\r
94 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 0
\r
96 /*-----------------------------------------------------------*/
\r
99 * Set up the hardware ready to run this demo.
\r
101 static void prvSetupHardware( void );
\r
104 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
105 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
107 extern void main_blinky( void );
\r
108 extern void main_full( void );
\r
110 /*-----------------------------------------------------------*/
\r
112 /* See the documentation page for this demo on the FreeRTOS.org web site for
\r
113 full information - including hardware setup requirements. */
\r
117 /* Prepare the hardware to run this demo. */
\r
118 prvSetupHardware();
\r
120 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
122 #if mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1
\r
134 /*-----------------------------------------------------------*/
\r
136 static void prvSetupHardware( void )
\r
138 extern void SystemCoreClockUpdate( void );
\r
140 /* ASF function to setup clocking. */
\r
143 /* Ensure all priority bits are assigned as preemption priority bits. */
\r
144 NVIC_SetPriorityGrouping( 0 );
\r
146 /* Atmel library function to setup for the evaluation kit being used. */
\r
149 /* Perform any configuration necessary to use the ParTest LED output
\r
151 vParTestInitialise();
\r
153 /*-----------------------------------------------------------*/
\r
155 void vApplicationMallocFailedHook( void )
\r
157 /* vApplicationMallocFailedHook() will only be called if
\r
158 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
159 function that will get called if a call to pvPortMalloc() fails.
\r
160 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
161 timer or semaphore is created. It is also called by various parts of the
\r
162 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
163 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
164 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
165 to query the size of free heap space that remains (although it does not
\r
166 provide information on how the remaining heap might be fragmented). */
\r
167 taskDISABLE_INTERRUPTS();
\r
170 /*-----------------------------------------------------------*/
\r
172 void vApplicationIdleHook( void )
\r
174 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
175 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
176 task. It is essential that code added to this hook function never attempts
\r
177 to block in any way (for example, call xQueueReceive() with a block time
\r
178 specified, or call vTaskDelay()). If the application makes use of the
\r
179 vTaskDelete() API function (as this demo application does) then it is also
\r
180 important that vApplicationIdleHook() is permitted to return to its calling
\r
181 function, because it is the responsibility of the idle task to clean up
\r
182 memory allocated by the kernel to any task that has since been deleted. */
\r
184 /*-----------------------------------------------------------*/
\r
186 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName )
\r
188 ( void ) pcTaskName;
\r
191 /* Run time stack overflow checking is performed if
\r
192 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
193 function is called if a stack overflow is detected. */
\r
194 taskDISABLE_INTERRUPTS();
\r
197 /*-----------------------------------------------------------*/
\r
199 void vApplicationTickHook( void )
\r
201 /* This function will be called by each tick interrupt if
\r
202 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
203 added here, but the tick hook is called from an interrupt context, so
\r
204 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
205 functions can be used (those that end in FromISR()). */
\r
207 #if ( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 0 )
\r
209 /* In this case the tick hook is used as part of the queue set test. */
\r
210 vQueueSetAccessQueueSetFromISR();
\r
212 #endif /* mainCREATE_SIMPLE_BLINKY_DEMO_ONLY */
\r
214 /*-----------------------------------------------------------*/
\r