2 FreeRTOS V9.0.0rc2 - 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 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in this file) is used to
\r
74 * select between the two. The simply blinky demo is implemented and described
\r
75 * in main_blinky.c. The more comprehensive test and demo application is
\r
76 * 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. It also contains a dummy
\r
80 * interrupt service routine called Dummy_IRQHandler() that is provided as an
\r
81 * example of how to use interrupt safe FreeRTOS API functions (those that end
\r
84 *****************************************************************************/
\r
87 /* Standard includes. */
\r
90 /* FreeRTOS includes. */
\r
91 #include "FreeRTOS.h"
\r
94 /* Demo application include. */
\r
95 #include "ParTest.h"
\r
97 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
98 or 0 to run the more comprehensive test and demo application. */
\r
99 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 1
\r
102 /*-----------------------------------------------------------*/
\r
105 * Perform any application specific hardware configuration. The clocks,
\r
106 * memory, etc. are configured before main() is called.
\r
108 static void prvSetupHardware( void );
\r
110 /* main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
111 main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0. */
\r
112 extern void main_blinky( void );
\r
113 extern void main_full( void );
\r
115 /*-----------------------------------------------------------*/
\r
119 /* Prepare the hardware to run this demo. */
\r
120 prvSetupHardware();
\r
122 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
124 #if mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1
\r
136 /*-----------------------------------------------------------*/
\r
138 static void prvSetupHardware( void )
\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
198 #ifdef JUST_AN_EXAMPLE_ISR
\r
200 void Dummy_IRQHandler(void)
\r
202 long lHigherPriorityTaskWoken = pdFALSE;
\r
204 /* Clear the interrupt if necessary. */
\r
205 Dummy_ClearITPendingBit();
\r
207 /* This interrupt does nothing more than demonstrate how to synchronise a
\r
208 task with an interrupt. A semaphore is used for this purpose. Note
\r
209 lHigherPriorityTaskWoken is initialised to zero. Only FreeRTOS API functions
\r
210 that end in "FromISR" can be called from an ISR. */
\r
211 xSemaphoreGiveFromISR( xTestSemaphore, &lHigherPriorityTaskWoken );
\r
213 /* If there was a task that was blocked on the semaphore, and giving the
\r
214 semaphore caused the task to unblock, and the unblocked task has a priority
\r
215 higher than the current Running state task (the task that this interrupt
\r
216 interrupted), then lHigherPriorityTaskWoken will have been set to pdTRUE
\r
217 internally within xSemaphoreGiveFromISR(). Passing pdTRUE into the
\r
218 portEND_SWITCHING_ISR() macro will result in a context switch being pended to
\r
219 ensure this interrupt returns directly to the unblocked, higher priority,
\r
220 task. Passing pdFALSE into portEND_SWITCHING_ISR() has no effect. */
\r
221 portEND_SWITCHING_ISR( lHigherPriorityTaskWoken );
\r
224 #endif /* JUST_AN_EXAMPLE_ISR */
\r