2 FreeRTOS V8.1.2 - Copyright (C) 2014 Real Time Engineers Ltd.
\r
5 VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.
\r
7 ***************************************************************************
\r
9 * FreeRTOS provides completely free yet professionally developed, *
\r
10 * robust, strictly quality controlled, supported, and cross *
\r
11 * platform software that has become a de facto standard. *
\r
13 * Help yourself get started quickly and support the FreeRTOS *
\r
14 * project by purchasing a FreeRTOS tutorial book, reference *
\r
15 * manual, or both from: http://www.FreeRTOS.org/Documentation *
\r
19 ***************************************************************************
\r
21 This file is part of the FreeRTOS distribution.
\r
23 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
24 the terms of the GNU General Public License (version 2) as published by the
\r
25 Free Software Foundation >>!AND MODIFIED BY!<< the FreeRTOS exception.
\r
27 >>! NOTE: The modification to the GPL is included to allow you to !<<
\r
28 >>! distribute a combined work that includes FreeRTOS without being !<<
\r
29 >>! obliged to provide the source code for proprietary components !<<
\r
30 >>! outside of the FreeRTOS kernel. !<<
\r
32 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
33 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
34 FOR A PARTICULAR PURPOSE. Full license text is available from the following
\r
35 link: http://www.freertos.org/a00114.html
\r
39 ***************************************************************************
\r
41 * Having a problem? Start by reading the FAQ "My application does *
\r
42 * not run, what could be wrong?" *
\r
44 * http://www.FreeRTOS.org/FAQHelp.html *
\r
46 ***************************************************************************
\r
48 http://www.FreeRTOS.org - Documentation, books, training, latest versions,
\r
49 license and Real Time Engineers Ltd. contact details.
\r
51 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
52 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
53 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
55 http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High
\r
56 Integrity Systems to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
57 licenses offer ticketed support, indemnification and middleware.
\r
59 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
60 engineered and independently SIL3 certified version for use in safety and
\r
61 mission critical applications that require provable dependability.
\r
66 /******************************************************************************
\r
67 * This project provides two demo applications. A simple blinky style project,
\r
68 * and a more comprehensive test and demo application. The
\r
69 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in this file) is used to
\r
70 * select between the two. The simply blinky demo is implemented and described
\r
71 * in main_blinky.c. The more comprehensive test and demo application is
\r
72 * implemented and described in main_full.c.
\r
74 * This file implements the code that is not demo specific, including the
\r
75 * hardware setup and FreeRTOS hook functions.
\r
79 /* Standard includes. */
\r
82 /* Kernel includes. */
\r
83 #include "FreeRTOS.h"
\r
86 /* Standard demo includes - just needed for the LED (ParTest) initialisation
\r
88 #include "partest.h"
\r
90 /* Library includes. */
\r
93 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
94 or 0 to run the more comprehensive test and demo application. */
\r
95 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 0
\r
97 /*-----------------------------------------------------------*/
\r
100 * Set up the hardware ready to run this demo.
\r
102 static void prvSetupHardware( void );
\r
105 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
106 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
108 extern void main_blinky( void );
\r
109 extern void main_full( void );
\r
111 /*-----------------------------------------------------------*/
\r
113 /* See the documentation page for this demo on the FreeRTOS.org web site for
\r
114 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 /* Perform any configuration necessary to use the ParTest LED output
\r
140 vParTestInitialise();
\r
142 /*-----------------------------------------------------------*/
\r
144 void vApplicationMallocFailedHook( void )
\r
146 /* vApplicationMallocFailedHook() will only be called if
\r
147 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
148 function that will get called if a call to pvPortMalloc() fails.
\r
149 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
150 timer or semaphore is created. It is also called by various parts of the
\r
151 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
152 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
153 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
154 to query the size of free heap space that remains (although it does not
\r
155 provide information on how the remaining heap might be fragmented). */
\r
156 taskDISABLE_INTERRUPTS();
\r
159 /*-----------------------------------------------------------*/
\r
161 void vApplicationIdleHook( void )
\r
163 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
164 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
165 task. It is essential that code added to this hook function never attempts
\r
166 to block in any way (for example, call xQueueReceive() with a block time
\r
167 specified, or call vTaskDelay()). If the application makes use of the
\r
168 vTaskDelete() API function (as this demo application does) then it is also
\r
169 important that vApplicationIdleHook() is permitted to return to its calling
\r
170 function, because it is the responsibility of the idle task to clean up
\r
171 memory allocated by the kernel to any task that has since been deleted. */
\r
173 /*-----------------------------------------------------------*/
\r
175 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
177 ( void ) pcTaskName;
\r
180 /* Run time stack overflow checking is performed if
\r
181 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
182 function is called if a stack overflow is detected. */
\r
183 taskDISABLE_INTERRUPTS();
\r
186 /*-----------------------------------------------------------*/
\r
188 void vApplicationTickHook( void )
\r
190 /* This function will be called by each tick interrupt if
\r
191 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
192 added here, but the tick hook is called from an interrupt context, so
\r
193 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
194 functions can be used (those that end in FromISR()). */
\r
196 /*-----------------------------------------------------------*/
\r