2 FreeRTOS V8.0.0:rc1 - Copyright (C) 2014 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 includes FreeRTOS+CLI, FreeRTOS+UDP
\r
69 * and FreeRTOS+FAT SL. The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined
\r
70 * in this 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 and full user
\r
73 * instructions are provided on the following URL:
\r
74 * http://www.FreeRTOS.org/Atmel_SAM4E_RTOS_Demo.html
\r
76 * This file implements the code that is not demo specific, including the
\r
77 * hardware setup and FreeRTOS hook functions.
\r
81 /* Kernel includes. */
\r
82 #include "FreeRTOS.h"
\r
85 /* Demo application includes. */
\r
86 #include "partest.h"
\r
88 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
89 or 0 to run the more comprehensive demo application that includes add-on
\r
91 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 1
\r
93 /*-----------------------------------------------------------*/
\r
96 * Set up the hardware ready to run this demo.
\r
98 static void prvSetupHardware( void );
\r
101 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
102 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
104 extern void main_blinky( void );
\r
105 extern void main_full( void );
\r
107 /*-----------------------------------------------------------*/
\r
111 /* Prepare the hardware to run this demo. */
\r
112 prvSetupHardware();
\r
114 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
116 #if ( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1 )
\r
122 /* Full user instructions are provided on the following URL:
\r
123 http://www.FreeRTOS.org/Atmel_SAM4E_RTOS_Demo.html */
\r
126 #endif /* mainCREATE_SIMPLE_BLINKY_DEMO_ONLY */
\r
130 /*-----------------------------------------------------------*/
\r
132 static void prvSetupHardware( void )
\r
134 /* Call the ASF initialisation functions. */
\r
137 pmc_enable_periph_clk( ID_GMAC );
\r
138 pmc_enable_periph_clk( ID_SMC );
\r
140 /*-----------------------------------------------------------*/
\r
142 void vApplicationMallocFailedHook( void )
\r
144 /* vApplicationMallocFailedHook() will only be called if
\r
145 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
146 function that will get called if a call to pvPortMalloc() fails.
\r
147 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
148 timer or semaphore is created. It is also called by various parts of the
\r
149 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
150 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
151 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
152 to query the size of free heap space that remains (although it does not
\r
153 provide information on how the remaining heap might be fragmented). */
\r
154 vAssertCalled( __LINE__, __FILE__ );
\r
156 /*-----------------------------------------------------------*/
\r
158 void vApplicationIdleHook( void )
\r
160 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
161 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
162 task. It is essential that code added to this hook function never attempts
\r
163 to block in any way (for example, call xQueueReceive() with a block time
\r
164 specified, or call vTaskDelay()). If the application makes use of the
\r
165 vTaskDelete() API function (as this demo application does) then it is also
\r
166 important that vApplicationIdleHook() is permitted to return to its calling
\r
167 function, because it is the responsibility of the idle task to clean up
\r
168 memory allocated by the kernel to any task that has since been deleted. */
\r
170 /* The simple blinky demo does not use the idle hook - the full demo does. */
\r
171 #if( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 0 )
\r
173 extern void vFullDemoIdleHook( void );
\r
175 /* Implemented in main_full.c. */
\r
176 vFullDemoIdleHook();
\r
180 /*-----------------------------------------------------------*/
\r
182 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
184 ( void ) pcTaskName;
\r
187 /* Run time stack overflow checking is performed if
\r
188 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook function is
\r
189 called if a stack overflow is detected. */
\r
190 vAssertCalled( __LINE__, __FILE__ );
\r
192 /*-----------------------------------------------------------*/
\r
194 void vApplicationTickHook( void )
\r
196 /* This function will be called by each tick interrupt if
\r
197 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
198 added here, but the tick hook is called from an interrupt context, so
\r
199 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
200 functions can be used (those that end in FromISR()). */
\r
202 /* The simple blinky demo does not use the tick hook - the full demo does. */
\r
203 #if( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 0 )
\r
205 extern void vFullDemoTickHook( void );
\r
207 /* Implemented in main_full.c. */
\r
208 vFullDemoTickHook();
\r
212 /*-----------------------------------------------------------*/
\r
214 void vAssertCalled( uint32_t ulLine, const char *pcFile )
\r
216 /* The following two variables are just to ensure the parameters are not
\r
217 optimised away and therefore unavailable when viewed in the debugger. */
\r
218 volatile uint32_t ulLineNumber = ulLine, ulSetNonZeroInDebuggerToReturn = 0;
\r
219 volatile const char * const pcFileName = pcFile;
\r
221 taskENTER_CRITICAL();
\r
222 while( ulSetNonZeroInDebuggerToReturn == 0 )
\r
224 /* If you want to set out of this function in the debugger to see the
\r
225 assert() location then set ulSetNonZeroInDebuggerToReturn to a non-zero
\r
228 taskEXIT_CRITICAL();
\r
230 ( void ) pcFileName;
\r
231 ( void ) ulLineNumber;
\r
233 /*-----------------------------------------------------------*/
\r
235 /* Provided to keep the linker happy. */
\r
236 void _exit_( int status )
\r
239 vAssertCalled( __LINE__, __FILE__ );
\r
242 /*-----------------------------------------------------------*/
\r
244 /* Provided to keep the linker happy. */
\r
249 /*-----------------------------------------------------------*/
\r
251 /* Provided to keep the linker happy. */
\r
252 int _write( int x )
\r
257 /*-----------------------------------------------------------*/
\r