2 FreeRTOS V7.6.0 - Copyright (C) 2013 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 distribute
\r
28 >>! a combined work that includes FreeRTOS without being obliged to provide
\r
29 >>! the source code for proprietary components outside of the FreeRTOS
\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 application that makes use of FreeRTOS+ add-on
\r
69 * components. The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in this
\r
70 * file) is used to select between the two. The simply blinky demo is
\r
71 * implemented and described in main_blinky.c. The more comprehensive demo
\r
72 * application is 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 /* Kernel includes. */
\r
80 #include "FreeRTOS.h"
\r
83 /* Demo application includes. */
\r
84 #include "partest.h"
\r
86 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
87 or 0 to run the more comprehensive demo application that includes add-on
\r
89 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 0
\r
91 /*-----------------------------------------------------------*/
\r
94 * Set up the hardware ready to run this demo.
\r
96 static void prvSetupHardware( void );
\r
99 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
100 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
102 extern void main_blinky( void );
\r
103 extern void main_full( void );
\r
105 /*-----------------------------------------------------------*/
\r
109 /* Prepare the hardware to run this demo. */
\r
110 prvSetupHardware();
\r
112 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
114 #if mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1
\r
126 /*-----------------------------------------------------------*/
\r
128 static void prvSetupHardware( void )
\r
130 /* Call the ASF initialisation functions. */
\r
133 pmc_enable_periph_clk( ID_GMAC );
\r
134 pmc_enable_periph_clk( ID_SMC );
\r
135 vParTestInitialise();
\r
137 /*-----------------------------------------------------------*/
\r
139 void vApplicationMallocFailedHook( void )
\r
141 /* vApplicationMallocFailedHook() will only be called if
\r
142 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
143 function that will get called if a call to pvPortMalloc() fails.
\r
144 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
145 timer or semaphore is created. It is also called by various parts of the
\r
146 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
147 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
148 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
149 to query the size of free heap space that remains (although it does not
\r
150 provide information on how the remaining heap might be fragmented). */
\r
151 vAssertCalled( __LINE__, __FILE__ );
\r
153 /*-----------------------------------------------------------*/
\r
155 void vApplicationIdleHook( void )
\r
157 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
158 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
159 task. It is essential that code added to this hook function never attempts
\r
160 to block in any way (for example, call xQueueReceive() with a block time
\r
161 specified, or call vTaskDelay()). If the application makes use of the
\r
162 vTaskDelete() API function (as this demo application does) then it is also
\r
163 important that vApplicationIdleHook() is permitted to return to its calling
\r
164 function, because it is the responsibility of the idle task to clean up
\r
165 memory allocated by the kernel to any task that has since been deleted. */
\r
167 /* The simple blinky demo does not use the idle hook - the full demo does. */
\r
168 #if( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 0 )
\r
170 extern void vFullDemoIdleHook( void );
\r
172 vFullDemoIdleHook();
\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 vAssertCalled( __LINE__, __FILE__ );
\r
188 /*-----------------------------------------------------------*/
\r
190 void vApplicationTickHook( void )
\r
192 /* This function will be called by each tick interrupt if
\r
193 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
194 added here, but the tick hook is called from an interrupt context, so
\r
195 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
196 functions can be used (those that end in FromISR()). */
\r
198 /* The simple blinky demo does not use the tick hook - the full demo does. */
\r
199 #if( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 0 )
\r
201 extern void vFullDemoTickHook( void );
\r
203 vFullDemoTickHook();
\r
207 /*-----------------------------------------------------------*/
\r
209 void vAssertCalled( uint32_t ulLine, const char *pcFile )
\r
211 /* The following two variables are just to ensure the parameters are not
\r
212 optimised away and therefore unavailable when viewed in the debugger. */
\r
213 volatile uint32_t ulLineNumber = ulLine, ulSetNoneZeroInDebuggerToReturn = 0;
\r
214 volatile const char * const pcFileName = pcFile;
\r
216 taskENTER_CRITICAL();
\r
217 while( ulSetNoneZeroInDebuggerToReturn == 0 )
\r
219 /* If you want to set out of this function in the debugger to see the
\r
220 assert() location then set ulSetNoneZeroInDebuggerToReturn to a non-zero
\r
223 taskEXIT_CRITICAL();
\r
225 ( void ) pcFileName;
\r
226 ( void ) ulLineNumber;
\r
228 /*-----------------------------------------------------------*/
\r
230 /* Provided to keep the linker happy. */
\r
231 void _exit_( int status )
\r
234 vAssertCalled( __LINE__, __FILE__ );
\r
237 /*-----------------------------------------------------------*/
\r
239 /* Provided to keep the linker happy. */
\r
244 /*-----------------------------------------------------------*/
\r
246 /* Provided to keep the linker happy. */
\r
247 int _write( int x )
\r
252 /*-----------------------------------------------------------*/
\r