2 FreeRTOS V9.0.0rc1 - Copyright (C) 2016 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 ***************************************************************************
\r
14 >>! NOTE: The modification to the GPL is included to allow you to !<<
\r
15 >>! distribute a combined work that includes FreeRTOS without being !<<
\r
16 >>! obliged to provide the source code for proprietary components !<<
\r
17 >>! outside of the FreeRTOS kernel. !<<
\r
18 ***************************************************************************
\r
20 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
21 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
22 FOR A PARTICULAR PURPOSE. Full license text is available on the following
\r
23 link: http://www.freertos.org/a00114.html
\r
25 ***************************************************************************
\r
27 * FreeRTOS provides completely free yet professionally developed, *
\r
28 * robust, strictly quality controlled, supported, and cross *
\r
29 * platform software that is more than just the market leader, it *
\r
30 * is the industry's de facto standard. *
\r
32 * Help yourself get started quickly while simultaneously helping *
\r
33 * to support the FreeRTOS project by purchasing a FreeRTOS *
\r
34 * tutorial book, reference manual, or both: *
\r
35 * http://www.FreeRTOS.org/Documentation *
\r
37 ***************************************************************************
\r
39 http://www.FreeRTOS.org/FAQHelp.html - Having a problem? Start by reading
\r
40 the FAQ page "My application does not run, what could be wrong?". Have you
\r
41 defined configASSERT()?
\r
43 http://www.FreeRTOS.org/support - In return for receiving this top quality
\r
44 embedded software for free we request you assist our global community by
\r
45 participating in the support forum.
\r
47 http://www.FreeRTOS.org/training - Investing in training allows your team to
\r
48 be as productive as possible as early as possible. Now you can receive
\r
49 FreeRTOS training directly from Richard Barry, CEO of Real Time Engineers
\r
50 Ltd, and the world's leading authority on the world's leading RTOS.
\r
52 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
53 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
54 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
56 http://www.FreeRTOS.org/labs - Where new FreeRTOS products go to incubate.
\r
57 Come and try FreeRTOS+TCP, our new open source TCP/IP stack for FreeRTOS.
\r
59 http://www.OpenRTOS.com - Real Time Engineers ltd. license FreeRTOS to High
\r
60 Integrity Systems ltd. to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
61 licenses offer ticketed support, indemnification and commercial middleware.
\r
63 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
64 engineered and independently SIL3 certified version for use in safety and
\r
65 mission critical applications that require provable dependability.
\r
70 /******************************************************************************
\r
71 * This project provides two demo applications. A simple blinky style project,
\r
72 * and a more comprehensive test and demo application. The
\r
73 * configCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in FreeRTOSConfig.h) is
\r
74 * used to select between the two. The simply blinky demo is implemented and
\r
75 * described in main_blinky.c. The more comprehensive test and demo application
\r
76 * is implemented and described in main_full.c.
\r
78 * This file implements the code that is not demo specific, including the
\r
79 * hardware setup and FreeRTOS hook functions.
\r
83 /* Standard includes. */
\r
86 /* Kernel includes. */
\r
87 #include "FreeRTOS.h"
\r
90 /* Standard demo includes - just needed for the LED (ParTest) initialisation
\r
92 #include "partest.h"
\r
95 * Set up the hardware ready to run this demo.
\r
97 static void prvSetupHardware( void );
\r
100 * main_blinky() is used when configCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
101 * main_full() is used when configCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
103 extern void main_blinky( void );
\r
104 extern void main_full( void );
\r
106 /* Prototypes for the standard FreeRTOS callback/hook functions implemented
\r
107 within this file. */
\r
108 void vApplicationMallocFailedHook( void );
\r
109 void vApplicationIdleHook( void );
\r
110 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName );
\r
111 void vApplicationTickHook( void );
\r
113 /*-----------------------------------------------------------*/
\r
114 /* See the documentation page for this demo on the FreeRTOS.org web site for
\r
115 full information - including hardware setup requirements. */
\r
119 /* Prepare the hardware to run this demo. */
\r
120 prvSetupHardware();
\r
122 /* The configCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
124 #if configCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1
\r
136 /*-----------------------------------------------------------*/
\r
138 static void prvSetupHardware( void )
\r
140 /* Perform any configuration necessary to use the ParTest LED output
\r
141 functions. The name ParTest is now somewhat obsolete - originally it
\r
142 stood for PARallel port Test. */
\r
143 vParTestInitialise();
\r
145 /*-----------------------------------------------------------*/
\r
147 void vApplicationMallocFailedHook( void )
\r
149 /* vApplicationMallocFailedHook() will only be called if
\r
150 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
151 function that will get called if a call to pvPortMalloc() fails.
\r
152 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
153 timer or semaphore is created. It is also called by various parts of the
\r
154 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
155 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
156 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
157 to query the size of free heap space that remains (although it does not
\r
158 provide information on how the remaining heap might be fragmented). */
\r
159 taskDISABLE_INTERRUPTS();
\r
162 /*-----------------------------------------------------------*/
\r
164 void vApplicationIdleHook( void )
\r
166 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
167 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
168 task. It is essential that code added to this hook function never attempts
\r
169 to block in any way (for example, call xQueueReceive() with a block time
\r
170 specified, or call vTaskDelay()). If the application makes use of the
\r
171 vTaskDelete() API function (as this demo application does) then it is also
\r
172 important that vApplicationIdleHook() is permitted to return to its calling
\r
173 function, because it is the responsibility of the idle task to clean up
\r
174 memory allocated by the kernel to any task that has since been deleted. */
\r
176 #if configCREATE_SIMPLE_BLINKY_DEMO_ONLY != 1
\r
178 /* If the file system is only going to be accessed from one task then
\r
179 F_FS_THREAD_AWARE can be set to 0 and the set of example files is created
\r
180 before the RTOS scheduler is started. If the file system is going to be
\r
181 access from more than one task then F_FS_THREAD_AWARE must be set to 1 and
\r
182 the set of sample files are created from the idle task hook function. */
\r
183 #if F_FS_THREAD_AWARE == 1
\r
185 static portBASE_TYPE xCreatedSampleFiles = pdFALSE;
\r
187 /* Initialise the drive and file system, then create a few example
\r
188 files. The output from this function just goes to the stdout window,
\r
189 allowing the output to be viewed when the UDP command console is not
\r
191 if( xCreatedSampleFiles == pdFALSE )
\r
193 vCreateAndVerifySampleFiles();
\r
194 xCreatedSampleFiles = pdTRUE;
\r
201 /*-----------------------------------------------------------*/
\r
203 void vApplicationStackOverflowHook( TaskHandle_t pxTask, 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