2 FreeRTOS V7.5.2 - 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. It also contains a dummy
\r
75 * interrupt service routine called Dummy_IRQHandler() that is provided as an
\r
76 * example of how to use interrupt safe FreeRTOS API functions (those that end
\r
79 *****************************************************************************/
\r
82 /* Standard includes. */
\r
85 /* FreeRTOS includes. */
\r
86 #include "FreeRTOS.h"
\r
89 /* Demo application include. */
\r
90 #include "ParTest.h"
\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
97 /*-----------------------------------------------------------*/
\r
100 * Perform any application specific hardware configuration. The clocks,
\r
101 * memory, etc. are configured before main() is called.
\r
103 static void prvSetupHardware( void );
\r
106 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
107 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
109 extern void main_blinky( void );
\r
110 extern void main_full( void );
\r
113 * CMSIS clock configuration function.
\r
115 extern void SystemCoreClockUpdate( void );
\r
117 /*-----------------------------------------------------------*/
\r
121 /* Prepare the hardware to run this demo. */
\r
122 prvSetupHardware();
\r
124 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
126 #if mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1
\r
138 /*-----------------------------------------------------------*/
\r
140 static void prvSetupHardware( void )
\r
142 SystemCoreClockUpdate();
\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 /*-----------------------------------------------------------*/
\r
178 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName )
\r
180 ( void ) pcTaskName;
\r
183 /* Run time stack overflow checking is performed if
\r
184 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
185 function is called if a stack overflow is detected. */
\r
186 taskDISABLE_INTERRUPTS();
\r
189 /*-----------------------------------------------------------*/
\r
191 void vApplicationTickHook( void )
\r
193 /* This function will be called by each tick interrupt if
\r
194 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
195 added here, but the tick hook is called from an interrupt context, so
\r
196 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
197 functions can be used (those that end in FromISR()). */
\r
199 /*-----------------------------------------------------------*/
\r
201 #ifdef JUST_AN_EXAMPLE_ISR
\r
203 void Dummy_IRQHandler(void)
\r
205 long lHigherPriorityTaskWoken = pdFALSE;
\r
207 /* Clear the interrupt if necessary. */
\r
208 Dummy_ClearITPendingBit();
\r
210 /* This interrupt does nothing more than demonstrate how to synchronise a
\r
211 task with an interrupt. A semaphore is used for this purpose. Note
\r
212 lHigherPriorityTaskWoken is initialised to zero. Only FreeRTOS API functions
\r
213 that end in "FromISR" can be called from an ISR. */
\r
214 xSemaphoreGiveFromISR( xTestSemaphore, &lHigherPriorityTaskWoken );
\r
216 /* If there was a task that was blocked on the semaphore, and giving the
\r
217 semaphore caused the task to unblock, and the unblocked task has a priority
\r
218 higher than the current Running state task (the task that this interrupt
\r
219 interrupted), then lHigherPriorityTaskWoken will have been set to pdTRUE
\r
220 internally within xSemaphoreGiveFromISR(). Passing pdTRUE into the
\r
221 portEND_SWITCHING_ISR() macro will result in a context switch being pended to
\r
222 ensure this interrupt returns directly to the unblocked, higher priority,
\r
223 task. Passing pdFALSE into portEND_SWITCHING_ISR() has no effect. */
\r
224 portEND_SWITCHING_ISR( lHigherPriorityTaskWoken );
\r
227 #endif /* JUST_AN_EXAMPLE_ISR */
\r