2 FreeRTOS V9.0.0rc2 - Copyright (C) 2016 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 ***************************************************************************
\r
14 >>! NOTE: The modification to the GPL is included to allow you to !<<
\r
15 >>! distribute a combined work that includes FreeRTOS without being !<<
\r
16 >>! obliged to provide the source code for proprietary components !<<
\r
17 >>! outside of the FreeRTOS kernel. !<<
\r
18 ***************************************************************************
\r
20 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
21 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
22 FOR A PARTICULAR PURPOSE. Full license text is available on the following
\r
23 link: http://www.freertos.org/a00114.html
\r
25 ***************************************************************************
\r
27 * FreeRTOS provides completely free yet professionally developed, *
\r
28 * robust, strictly quality controlled, supported, and cross *
\r
29 * platform software that is more than just the market leader, it *
\r
30 * is the industry's de facto standard. *
\r
32 * Help yourself get started quickly while simultaneously helping *
\r
33 * to support the FreeRTOS project by purchasing a FreeRTOS *
\r
34 * tutorial book, reference manual, or both: *
\r
35 * http://www.FreeRTOS.org/Documentation *
\r
37 ***************************************************************************
\r
39 http://www.FreeRTOS.org/FAQHelp.html - Having a problem? Start by reading
\r
40 the FAQ page "My application does not run, what could be wrong?". Have you
\r
41 defined configASSERT()?
\r
43 http://www.FreeRTOS.org/support - In return for receiving this top quality
\r
44 embedded software for free we request you assist our global community by
\r
45 participating in the support forum.
\r
47 http://www.FreeRTOS.org/training - Investing in training allows your team to
\r
48 be as productive as possible as early as possible. Now you can receive
\r
49 FreeRTOS training directly from Richard Barry, CEO of Real Time Engineers
\r
50 Ltd, and the world's leading authority on the world's leading RTOS.
\r
52 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
53 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
54 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
56 http://www.FreeRTOS.org/labs - Where new FreeRTOS products go to incubate.
\r
57 Come and try FreeRTOS+TCP, our new open source TCP/IP stack for FreeRTOS.
\r
59 http://www.OpenRTOS.com - Real Time Engineers ltd. license FreeRTOS to High
\r
60 Integrity Systems ltd. to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
61 licenses offer ticketed support, indemnification and commercial middleware.
\r
63 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
64 engineered and independently SIL3 certified version for use in safety and
\r
65 mission critical applications that require provable dependability.
\r
70 /******************************************************************************
\r
71 * This project provides two demo applications. A simple blinky style project,
\r
72 * and a more comprehensive application that includes FreeRTOS+CLI, FreeRTOS+UDP
\r
73 * and FreeRTOS+FAT SL. The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined
\r
74 * in this file) is used to select between the two. The simply blinky demo is
\r
75 * implemented and described in main_blinky.c. The more comprehensive demo
\r
76 * application is implemented and described in main_full.c and full user
\r
77 * instructions are provided on the following URL:
\r
78 * http://www.FreeRTOS.org/Atmel_SAM4E_RTOS_Demo.html
\r
80 * This file implements the code that is not demo specific, including the
\r
81 * hardware setup and FreeRTOS hook functions.
\r
85 /* Kernel includes. */
\r
86 #include "FreeRTOS.h"
\r
89 /* Demo application includes. */
\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 demo application that includes add-on
\r
95 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 1
\r
97 /*-----------------------------------------------------------*/
\r
100 * Set up the hardware ready to run this demo.
\r
102 static void prvSetupHardware( void );
\r
105 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
106 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
108 extern void main_blinky( void );
\r
109 extern void main_full( void );
\r
111 /*-----------------------------------------------------------*/
\r
115 /* Prepare the hardware to run this demo. */
\r
116 prvSetupHardware();
\r
118 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
120 #if ( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1 )
\r
126 /* Full user instructions are provided on the following URL:
\r
127 http://www.FreeRTOS.org/Atmel_SAM4E_RTOS_Demo.html */
\r
130 #endif /* mainCREATE_SIMPLE_BLINKY_DEMO_ONLY */
\r
134 /*-----------------------------------------------------------*/
\r
136 static void prvSetupHardware( void )
\r
138 /* Call the ASF initialisation functions. */
\r
141 pmc_enable_periph_clk( ID_GMAC );
\r
142 pmc_enable_periph_clk( ID_SMC );
\r
144 /*-----------------------------------------------------------*/
\r
146 void vApplicationMallocFailedHook( void )
\r
148 static volatile uint32_t ulCount = 0;
\r
150 /* vApplicationMallocFailedHook() will only be called if
\r
151 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
152 function that will get called if a call to pvPortMalloc() fails.
\r
153 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
154 timer or semaphore is created. It is also called by various parts of the
\r
155 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
156 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
157 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
158 to query the size of free heap space that remains (although it does not
\r
159 provide information on how the remaining heap might be fragmented).
\r
161 Just count the number of malloc fails as some failures may occur simply
\r
162 because the network load is very high, resulting in the consumption of a
\r
163 lot of network buffers. */
\r
166 /*-----------------------------------------------------------*/
\r
168 void vApplicationIdleHook( void )
\r
170 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
171 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
172 task. It is essential that code added to this hook function never attempts
\r
173 to block in any way (for example, call xQueueReceive() with a block time
\r
174 specified, or call vTaskDelay()). If the application makes use of the
\r
175 vTaskDelete() API function (as this demo application does) then it is also
\r
176 important that vApplicationIdleHook() is permitted to return to its calling
\r
177 function, because it is the responsibility of the idle task to clean up
\r
178 memory allocated by the kernel to any task that has since been deleted. */
\r
180 /* The simple blinky demo does not use the idle hook - the full demo does. */
\r
181 #if( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 0 )
\r
183 extern void vFullDemoIdleHook( void );
\r
185 /* Implemented in main_full.c. */
\r
186 vFullDemoIdleHook();
\r
190 /*-----------------------------------------------------------*/
\r
192 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
194 ( void ) pcTaskName;
\r
197 /* Run time stack overflow checking is performed if
\r
198 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook function is
\r
199 called if a stack overflow is detected. */
\r
200 vAssertCalled( __LINE__, __FILE__ );
\r
202 /*-----------------------------------------------------------*/
\r
204 void vApplicationTickHook( void )
\r
206 /* This function will be called by each tick interrupt if
\r
207 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
208 added here, but the tick hook is called from an interrupt context, so
\r
209 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
210 functions can be used (those that end in FromISR()). */
\r
212 /* The simple blinky demo does not use the tick hook - the full demo does. */
\r
213 #if( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 0 )
\r
215 extern void vFullDemoTickHook( void );
\r
217 /* Implemented in main_full.c. */
\r
218 vFullDemoTickHook();
\r
222 /*-----------------------------------------------------------*/
\r
224 void vAssertCalled( uint32_t ulLine, const char *pcFile )
\r
226 /* The following two variables are just to ensure the parameters are not
\r
227 optimised away and therefore unavailable when viewed in the debugger. */
\r
228 volatile uint32_t ulLineNumber = ulLine, ulSetNonZeroInDebuggerToReturn = 0;
\r
229 volatile const char * const pcFileName = pcFile;
\r
231 taskENTER_CRITICAL();
\r
232 while( ulSetNonZeroInDebuggerToReturn == 0 )
\r
234 /* If you want to set out of this function in the debugger to see the
\r
235 assert() location then set ulSetNonZeroInDebuggerToReturn to a non-zero
\r
238 taskEXIT_CRITICAL();
\r
240 ( void ) pcFileName;
\r
241 ( void ) ulLineNumber;
\r
243 /*-----------------------------------------------------------*/
\r
245 /* Provided to keep the linker happy. */
\r
246 void _exit_( int status )
\r
249 vAssertCalled( __LINE__, __FILE__ );
\r
252 /*-----------------------------------------------------------*/
\r
254 /* Provided to keep the linker happy. */
\r
259 /*-----------------------------------------------------------*/
\r
261 /* Provided to keep the linker happy. */
\r
262 int _write( int x )
\r
267 /*-----------------------------------------------------------*/
\r