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 low power project that
\r
72 * demonstrates the FreeRTOS tickless mode, and a more comprehensive test and
\r
73 * demo application. The configCREATE_LOW_POWER_DEMO setting (defined at the
\r
74 * top of FreeRTOSConfig.h) is used to select between the two. The low power
\r
75 * demo is implemented and described in main_low_power.c. The more
\r
76 * comprehensive test and demo application is implemented and described in
\r
79 * This file implements the code that is not demo specific, including the
\r
80 * hardware setup and FreeRTOS hook functions.
\r
83 /* Standard includes. */
\r
86 /* Kernel includes. */
\r
87 #include "FreeRTOS.h"
\r
90 /* Standard demo includes - just needed for the LED (ParTest) initialisation
\r
92 #include "partest.h"
\r
94 /* Atmel library includes. */
\r
97 /*-----------------------------------------------------------*/
\r
100 * Set up the hardware ready to run this demo.
\r
102 static void prvSetupHardware( void );
\r
105 * main_low_power() is used when configCREATE_LOW_POWER_DEMO is set to 1.
\r
106 * main_full() is used when configCREATE_LOW_POWER_DEMO is set to 0.
\r
107 * configCREATE_LOW_POWER_DEMO is defined at the top of main.c.
\r
109 extern void main_low_power( void );
\r
110 extern void main_full( void );
\r
112 /* Prototypes for the standard FreeRTOS callback/hook functions implemented
\r
113 within this file. */
\r
114 void vApplicationMallocFailedHook( void );
\r
115 void vApplicationIdleHook( void );
\r
116 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName );
\r
117 void vApplicationTickHook( void );
\r
119 /* A handler for a button interrupt. The button's only purpose is to bring the
\r
120 CPU out of sleep mode early. */
\r
121 static void prvButtonISR( void );
\r
123 /*-----------------------------------------------------------*/
\r
125 /* See the documentation page for this demo on the FreeRTOS.org web site for
\r
126 full information - including hardware setup requirements. */
\r
129 /* Prepare the hardware to run this demo. */
\r
130 prvSetupHardware();
\r
132 /* The configCREATE_LOW_POWER_DEMO setting is described at the top of
\r
134 #if( configCREATE_LOW_POWER_DEMO == 1 )
\r
146 /*-----------------------------------------------------------*/
\r
148 static void prvButtonISR( void )
\r
150 /* The button doesn't do anything other than providing a means for brining
\r
151 the MCU out of sleep mode early. */
\r
152 if( eic_line_interrupt_is_pending( EIC, GPIO_PUSH_BUTTON_EIC_LINE ) )
\r
154 eic_line_clear_interrupt( EIC, GPIO_PUSH_BUTTON_EIC_LINE );
\r
157 /*-----------------------------------------------------------*/
\r
159 static void prvSetupHardware( void )
\r
161 extern void SystemCoreClockUpdate( void );
\r
162 struct eic_line_config xEICLineConfiguration;
\r
164 /* Configure the external interrupt controller so button pushes can
\r
165 generate interrupts. */
\r
166 xEICLineConfiguration.eic_mode = EIC_MODE_EDGE_TRIGGERED;
\r
167 xEICLineConfiguration.eic_edge = EIC_EDGE_FALLING_EDGE;
\r
168 xEICLineConfiguration.eic_level = EIC_LEVEL_LOW_LEVEL;
\r
169 xEICLineConfiguration.eic_filter = EIC_FILTER_DISABLED;
\r
170 xEICLineConfiguration.eic_async = EIC_ASYNCH_MODE;
\r
172 eic_line_set_config( EIC, GPIO_PUSH_BUTTON_EIC_LINE, &xEICLineConfiguration );
\r
173 eic_line_set_callback( EIC, GPIO_PUSH_BUTTON_EIC_LINE, prvButtonISR, EIC_5_IRQn, 0 );
\r
174 eic_line_enable( EIC, GPIO_PUSH_BUTTON_EIC_LINE );
\r
176 /* ASF function to setup clocking. */
\r
179 /* Ensure all priority bits are assigned as preemption priority bits. */
\r
180 NVIC_SetPriorityGrouping( 0 );
\r
182 /* Atmel library function to setup for the evaluation kit being used. */
\r
185 /* Initialise the sleep manager in case the low power demo is being used. */
\r
188 /*-----------------------------------------------------------*/
\r
190 void vApplicationMallocFailedHook( void )
\r
192 /* vApplicationMallocFailedHook() will only be called if
\r
193 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
194 function that will get called if a call to pvPortMalloc() fails.
\r
195 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
196 timer or semaphore is created. It is also called by various parts of the
\r
197 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
198 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
199 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
200 to query the size of free heap space that remains (although it does not
\r
201 provide information on how the remaining heap might be fragmented). */
\r
202 taskDISABLE_INTERRUPTS();
\r
205 /*-----------------------------------------------------------*/
\r
207 void vApplicationIdleHook( void )
\r
209 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
210 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
211 task. It is essential that code added to this hook function never attempts
\r
212 to block in any way (for example, call xQueueReceive() with a block time
\r
213 specified, or call vTaskDelay()). If the application makes use of the
\r
214 vTaskDelete() API function (as this demo application does) then it is also
\r
215 important that vApplicationIdleHook() is permitted to return to its calling
\r
216 function, because it is the responsibility of the idle task to clean up
\r
217 memory allocated by the kernel to any task that has since been deleted. */
\r
219 /*-----------------------------------------------------------*/
\r
221 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
223 ( void ) pcTaskName;
\r
226 /* Run time stack overflow checking is performed if
\r
227 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
228 function is called if a stack overflow is detected. */
\r
229 taskDISABLE_INTERRUPTS();
\r
232 /*-----------------------------------------------------------*/
\r
234 void vApplicationTickHook( void )
\r
236 /* This function will be called by each tick interrupt if
\r
237 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
238 added here, but the tick hook is called from an interrupt context, so
\r
239 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
240 functions can be used (those that end in FromISR()). */
\r
242 /*-----------------------------------------------------------*/
\r
244 void vAssertCalled( void )
\r
246 volatile unsigned long ul = 0;
\r
248 taskENTER_CRITICAL();
\r
250 /* Set ul to a non-zero value using the debugger to step out of this
\r
254 __asm volatile( "NOP" );
\r
257 taskEXIT_CRITICAL();
\r