2 FreeRTOS V8.2.0rc1 - Copyright (C) 2014 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 >>! NOTE: The modification to the GPL is included to allow you to !<<
\r
14 >>! distribute a combined work that includes FreeRTOS without being !<<
\r
15 >>! obliged to provide the source code for proprietary components !<<
\r
16 >>! outside of the FreeRTOS kernel. !<<
\r
18 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
19 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
20 FOR A PARTICULAR PURPOSE. Full license text is available on the following
\r
21 link: http://www.freertos.org/a00114.html
\r
25 ***************************************************************************
\r
27 * Having a problem? Start by reading the FAQ "My application does *
\r
28 * not run, what could be wrong?". Have you defined configASSERT()? *
\r
30 * http://www.FreeRTOS.org/FAQHelp.html *
\r
32 ***************************************************************************
\r
34 ***************************************************************************
\r
36 * FreeRTOS provides completely free yet professionally developed, *
\r
37 * robust, strictly quality controlled, supported, and cross *
\r
38 * platform software that is more than just the market leader, it *
\r
39 * is the industry's de facto standard. *
\r
41 * Help yourself get started quickly while simultaneously helping *
\r
42 * to support the FreeRTOS project by purchasing a FreeRTOS *
\r
43 * tutorial book, reference manual, or both: *
\r
44 * http://www.FreeRTOS.org/Documentation *
\r
46 ***************************************************************************
\r
48 ***************************************************************************
\r
50 * Investing in training allows your team to be as productive as *
\r
51 * possible as early as possible, lowering your overall development *
\r
52 * cost, and enabling you to bring a more robust product to market *
\r
53 * earlier than would otherwise be possible. Richard Barry is both *
\r
54 * the architect and key author of FreeRTOS, and so also the world's *
\r
55 * leading authority on what is the world's most popular real time *
\r
56 * kernel for deeply embedded MCU designs. Obtaining your training *
\r
57 * from Richard ensures your team will gain directly from his in-depth *
\r
58 * product knowledge and years of usage experience. Contact Real Time *
\r
59 * Engineers Ltd to enquire about the FreeRTOS Masterclass, presented *
\r
60 * by Richard Barry: http://www.FreeRTOS.org/contact
\r
62 ***************************************************************************
\r
64 ***************************************************************************
\r
66 * You are receiving this top quality software for free. Please play *
\r
67 * fair and reciprocate by reporting any suspected issues and *
\r
68 * participating in the community forum: *
\r
69 * http://www.FreeRTOS.org/support *
\r
73 ***************************************************************************
\r
75 http://www.FreeRTOS.org - Documentation, books, training, latest versions,
\r
76 license and Real Time Engineers Ltd. contact details.
\r
78 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
79 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
80 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
82 http://www.FreeRTOS.org/labs - Where new FreeRTOS products go to incubate.
\r
83 Come and try FreeRTOS+TCP, our new open source TCP/IP stack for FreeRTOS.
\r
85 http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High
\r
86 Integrity Systems ltd. to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
87 licenses offer ticketed support, indemnification and commercial middleware.
\r
89 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
90 engineered and independently SIL3 certified version for use in safety and
\r
91 mission critical applications that require provable dependability.
\r
96 /******************************************************************************
\r
97 * This project provides two demo applications. A simple blinky style project,
\r
98 * and a more comprehensive test and demo application. The
\r
99 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in this file) is used to
\r
100 * select between the two. The simply blinky demo is implemented and described
\r
101 * in main_blinky.c. The more comprehensive test and demo application is
\r
102 * implemented and described in main_full.c.
\r
104 * This file implements the code that is not demo specific, including the
\r
105 * hardware setup and FreeRTOS hook functions.
\r
110 * This demo does not contain a non-kernel interrupt service routine that
\r
111 * can be used as an example for application writers to use as a reference.
\r
112 * Therefore, the framework of a dummy (not installed) handler is provided
\r
113 * in this file. The dummy function is called Dummy_IRQHandler(). Please
\r
114 * ensure to read the comments in the function itself, but more importantly,
\r
115 * the notes on the function contained on the documentation page for this demo
\r
116 * that is found on the FreeRTOS.org web site.
\r
119 /* Standard includes. */
\r
122 /* Kernel includes. */
\r
123 #include "FreeRTOS.h"
\r
126 /* Hardware includes. */
\r
127 #include "XMC4500.h"
\r
128 #include "System_XMC4500.h"
\r
130 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
131 or 0 to run the more comprehensive test and demo application. */
\r
132 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 0
\r
134 /*-----------------------------------------------------------*/
\r
137 * Set up the hardware ready to run this demo.
\r
139 static void prvSetupHardware( void );
\r
142 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
143 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
145 extern void main_blinky( void );
\r
146 extern void main_full( void );
\r
148 /*-----------------------------------------------------------*/
\r
152 /* Prepare the hardware to run this demo. */
\r
153 prvSetupHardware();
\r
155 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
157 #if mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1
\r
169 /*-----------------------------------------------------------*/
\r
171 static void prvSetupHardware( void )
\r
173 extern void SystemCoreClockUpdate( void );
\r
175 /* Ensure SystemCoreClock variable is set. */
\r
176 SystemCoreClockUpdate();
\r
178 /* Configure pin P3.9 for the LED. */
\r
179 PORT3->IOCR8 = 0x00008000;
\r
181 /* Ensure all priority bits are assigned as preemption priority bits. */
\r
182 NVIC_SetPriorityGrouping( 0 );
\r
184 /*-----------------------------------------------------------*/
\r
186 void vApplicationMallocFailedHook( void )
\r
188 /* vApplicationMallocFailedHook() will only be called if
\r
189 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
190 function that will get called if a call to pvPortMalloc() fails.
\r
191 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
192 timer or semaphore is created. It is also called by various parts of the
\r
193 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
194 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
195 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
196 to query the size of free heap space that remains (although it does not
\r
197 provide information on how the remaining heap might be fragmented). */
\r
198 taskDISABLE_INTERRUPTS();
\r
201 /*-----------------------------------------------------------*/
\r
203 void vApplicationIdleHook( void )
\r
205 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
206 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
207 task. It is essential that code added to this hook function never attempts
\r
208 to block in any way (for example, call xQueueReceive() with a block time
\r
209 specified, or call vTaskDelay()). If the application makes use of the
\r
210 vTaskDelete() API function (as this demo application does) then it is also
\r
211 important that vApplicationIdleHook() is permitted to return to its calling
\r
212 function, because it is the responsibility of the idle task to clean up
\r
213 memory allocated by the kernel to any task that has since been deleted. */
\r
215 /*-----------------------------------------------------------*/
\r
217 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
219 ( void ) pcTaskName;
\r
222 /* Run time stack overflow checking is performed if
\r
223 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
224 function is called if a stack overflow is detected. */
\r
225 taskDISABLE_INTERRUPTS();
\r
228 /*-----------------------------------------------------------*/
\r
230 void vApplicationTickHook( void )
\r
232 /* This function will be called by each tick interrupt if
\r
233 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
234 added here, but the tick hook is called from an interrupt context, so
\r
235 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
236 functions can be used (those that end in FromISR()). */
\r
238 /*-----------------------------------------------------------*/
\r
240 #ifdef JUST_AN_EXAMPLE_ISR
\r
242 void Dummy_IRQHandler(void)
\r
244 long lHigherPriorityTaskWoken = pdFALSE;
\r
246 /* Clear the interrupt if necessary. */
\r
247 Dummy_ClearITPendingBit();
\r
249 /* This interrupt does nothing more than demonstrate how to synchronise a
\r
250 task with an interrupt. A semaphore is used for this purpose. Note
\r
251 lHigherPriorityTaskWoken is initialised to zero. */
\r
252 xSemaphoreGiveFromISR( xTestSemaphore, &lHigherPriorityTaskWoken );
\r
254 /* If there was a task that was blocked on the semaphore, and giving the
\r
255 semaphore caused the task to unblock, and the unblocked task has a priority
\r
256 higher than the current Running state task (the task that this interrupt
\r
257 interrupted), then lHigherPriorityTaskWoken will have been set to pdTRUE
\r
258 internally within xSemaphoreGiveFromISR(). Passing pdTRUE into the
\r
259 portEND_SWITCHING_ISR() macro will result in a context switch being pended to
\r
260 ensure this interrupt returns directly to the unblocked, higher priority,
\r
261 task. Passing pdFALSE into portEND_SWITCHING_ISR() has no effect. */
\r
262 portEND_SWITCHING_ISR( lHigherPriorityTaskWoken );
\r
265 #endif /* JUST_AN_EXAMPLE_ISR */
\r