2 FreeRTOS V9.0.0 - 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 /* Kernel includes. */
\r
84 #include "FreeRTOS.h"
\r
87 /* Platform includes. */
\r
90 /*-----------------------------------------------------------*/
\r
93 * main_low_power() is used when configCREATE_LOW_POWER_DEMO is set to 1.
\r
94 * main_full() is used when configCREATE_LOW_POWER_DEMO is set to 0.
\r
96 extern void main_low_power( void );
\r
97 extern void main_full( void );
\r
99 /* Prototypes for the standard FreeRTOS callback/hook functions implemented
\r
100 within this file. */
\r
101 void vApplicationMallocFailedHook( void );
\r
102 void vApplicationIdleHook( void );
\r
103 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName );
\r
104 void vApplicationTickHook( void );
\r
106 /*-----------------------------------------------------------*/
\r
108 /* See the documentation page for this demo on the FreeRTOS.org web site for
\r
109 full information - including hardware setup requirements. */
\r
114 lcd_display( LCD_LINE1, "FreeRTOS" );
\r
116 /* The configCREATE_LOW_POWER_DEMO setting is described in FreeRTOSConfig.h. */
\r
117 #if configCREATE_LOW_POWER_DEMO == 1
\r
119 lcd_display( LCD_LINE2, "LP Demo" );
\r
124 lcd_display( LCD_LINE2, "Ful Demo" );
\r
129 /*-----------------------------------------------------------*/
\r
131 void vApplicationMallocFailedHook( void )
\r
133 /* vApplicationMallocFailedHook() will only be called if
\r
134 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
135 function that will get called if a call to pvPortMalloc() fails.
\r
136 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
137 timer or semaphore is created. It is also called by various parts of the
\r
138 demo application. If heap_1.c, heap_2.c or heap_4.c are used, then the size
\r
139 of the heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE
\r
140 in FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
141 to query the size of free heap space that remains (although it does not
\r
142 provide information on how the remaining heap might be fragmented). */
\r
143 taskDISABLE_INTERRUPTS();
\r
146 /*-----------------------------------------------------------*/
\r
148 void vApplicationIdleHook( void )
\r
150 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
151 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
152 task. It is essential that code added to this hook function never attempts
\r
153 to block in any way (for example, call xQueueReceive() with a block time
\r
154 specified, or call vTaskDelay()). If the application makes use of the
\r
155 vTaskDelete() API function (as this demo application does) then it is also
\r
156 important that vApplicationIdleHook() is permitted to return to its calling
\r
157 function, because it is the responsibility of the idle task to clean up
\r
158 memory allocated by the kernel to any task that has since been deleted. */
\r
160 /*-----------------------------------------------------------*/
\r
162 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
164 ( void ) pcTaskName;
\r
167 /* Run time stack overflow checking is performed if
\r
168 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook function is
\r
169 called if a stack overflow is detected. */
\r
170 taskDISABLE_INTERRUPTS();
\r
173 /*-----------------------------------------------------------*/
\r
175 void vApplicationTickHook( void )
\r
177 /* This function will be called by each tick interrupt if
\r
178 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
179 added here, but the tick hook is called from an interrupt context, so
\r
180 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
181 functions can be used (those that end in FromISR()). */
\r
183 /*-----------------------------------------------------------*/
\r
185 void vAssertCalled( void )
\r
187 volatile unsigned long ul = 0;
\r
189 taskENTER_CRITICAL();
\r
191 /* Set ul to a non-zero value using the debugger to step out of this
\r
195 __asm volatile( "NOP" );
\r
198 taskEXIT_CRITICAL();
\r