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 application that includes FreeRTOS+CLI, FreeRTOS+UDP
\r
99 * and FreeRTOS+FAT SL. The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined
\r
100 * in this file) is used to select between the two. The simply blinky demo is
\r
101 * implemented and described in main_blinky.c. The more comprehensive demo
\r
102 * application is implemented and described in main_full.c and full user
\r
103 * instructions are provided on the following URL:
\r
104 * http://www.FreeRTOS.org/Atmel_SAM4E_RTOS_Demo.html
\r
106 * This file implements the code that is not demo specific, including the
\r
107 * hardware setup and FreeRTOS hook functions.
\r
111 /* Kernel includes. */
\r
112 #include "FreeRTOS.h"
\r
115 /* Demo application includes. */
\r
116 #include "partest.h"
\r
118 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
119 or 0 to run the more comprehensive demo application that includes add-on
\r
121 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 1
\r
123 /*-----------------------------------------------------------*/
\r
126 * Set up the hardware ready to run this demo.
\r
128 static void prvSetupHardware( void );
\r
131 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
132 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
134 extern void main_blinky( void );
\r
135 extern void main_full( void );
\r
137 /*-----------------------------------------------------------*/
\r
141 /* Prepare the hardware to run this demo. */
\r
142 prvSetupHardware();
\r
144 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
146 #if ( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1 )
\r
152 /* Full user instructions are provided on the following URL:
\r
153 http://www.FreeRTOS.org/Atmel_SAM4E_RTOS_Demo.html */
\r
156 #endif /* mainCREATE_SIMPLE_BLINKY_DEMO_ONLY */
\r
160 /*-----------------------------------------------------------*/
\r
162 static void prvSetupHardware( void )
\r
164 /* Call the ASF initialisation functions. */
\r
167 pmc_enable_periph_clk( ID_GMAC );
\r
168 pmc_enable_periph_clk( ID_SMC );
\r
170 /*-----------------------------------------------------------*/
\r
172 void vApplicationMallocFailedHook( void )
\r
174 static volatile uint32_t ulCount = 0;
\r
176 /* vApplicationMallocFailedHook() will only be called if
\r
177 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
178 function that will get called if a call to pvPortMalloc() fails.
\r
179 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
180 timer or semaphore is created. It is also called by various parts of the
\r
181 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
182 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
183 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
184 to query the size of free heap space that remains (although it does not
\r
185 provide information on how the remaining heap might be fragmented).
\r
187 Just count the number of malloc fails as some failures may occur simply
\r
188 because the network load is very high, resulting in the consumption of a
\r
189 lot of network buffers. */
\r
192 /*-----------------------------------------------------------*/
\r
194 void vApplicationIdleHook( void )
\r
196 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
197 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
198 task. It is essential that code added to this hook function never attempts
\r
199 to block in any way (for example, call xQueueReceive() with a block time
\r
200 specified, or call vTaskDelay()). If the application makes use of the
\r
201 vTaskDelete() API function (as this demo application does) then it is also
\r
202 important that vApplicationIdleHook() is permitted to return to its calling
\r
203 function, because it is the responsibility of the idle task to clean up
\r
204 memory allocated by the kernel to any task that has since been deleted. */
\r
206 /* The simple blinky demo does not use the idle hook - the full demo does. */
\r
207 #if( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 0 )
\r
209 extern void vFullDemoIdleHook( void );
\r
211 /* Implemented in main_full.c. */
\r
212 vFullDemoIdleHook();
\r
216 /*-----------------------------------------------------------*/
\r
218 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
220 ( void ) pcTaskName;
\r
223 /* Run time stack overflow checking is performed if
\r
224 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook function is
\r
225 called if a stack overflow is detected. */
\r
226 vAssertCalled( __LINE__, __FILE__ );
\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 /* The simple blinky demo does not use the tick hook - the full demo does. */
\r
239 #if( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 0 )
\r
241 extern void vFullDemoTickHook( void );
\r
243 /* Implemented in main_full.c. */
\r
244 vFullDemoTickHook();
\r
248 /*-----------------------------------------------------------*/
\r
250 void vAssertCalled( uint32_t ulLine, const char *pcFile )
\r
252 /* The following two variables are just to ensure the parameters are not
\r
253 optimised away and therefore unavailable when viewed in the debugger. */
\r
254 volatile uint32_t ulLineNumber = ulLine, ulSetNonZeroInDebuggerToReturn = 0;
\r
255 volatile const char * const pcFileName = pcFile;
\r
257 taskENTER_CRITICAL();
\r
258 while( ulSetNonZeroInDebuggerToReturn == 0 )
\r
260 /* If you want to set out of this function in the debugger to see the
\r
261 assert() location then set ulSetNonZeroInDebuggerToReturn to a non-zero
\r
264 taskEXIT_CRITICAL();
\r
266 ( void ) pcFileName;
\r
267 ( void ) ulLineNumber;
\r
269 /*-----------------------------------------------------------*/
\r
271 /* Provided to keep the linker happy. */
\r
272 void _exit_( int status )
\r
275 vAssertCalled( __LINE__, __FILE__ );
\r
278 /*-----------------------------------------------------------*/
\r
280 /* Provided to keep the linker happy. */
\r
285 /*-----------------------------------------------------------*/
\r
287 /* Provided to keep the linker happy. */
\r
288 int _write( int x )
\r
293 /*-----------------------------------------------------------*/
\r