2 FreeRTOS V8.0.0 - 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 low power project that
\r
68 * demonstrates the FreeRTOS tickless mode, and a more comprehensive test and
\r
69 * demo application. The configCREATE_LOW_POWER_DEMO setting (defined at the
\r
70 * top of FreeRTOSConfig.h) is used to select between the two. The low power
\r
71 * demo is implemented and described in main_low_power.c. The more
\r
72 * comprehensive test and demo application is implemented and described in
\r
75 * This file implements the code that is not demo specific, including the
\r
76 * hardware setup and FreeRTOS hook functions.
\r
79 /* Kernel includes. */
\r
80 #include "FreeRTOS.h"
\r
83 /* Platform includes. */
\r
86 /*-----------------------------------------------------------*/
\r
89 * Prepare the board of the demo.
\r
91 extern void vHardwareSetup( void );
\r
94 * main_low_power() is used when configCREATE_LOW_POWER_DEMO is set to 1.
\r
95 * main_full() is used when configCREATE_LOW_POWER_DEMO is set to 0.
\r
97 extern void main_low_power( void );
\r
98 extern void main_full( void );
\r
100 /* Prototypes for the standard FreeRTOS callback/hook functions implemented
\r
101 within this file. */
\r
102 void vApplicationMallocFailedHook( void );
\r
103 void vApplicationIdleHook( void );
\r
104 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName );
\r
105 void vApplicationTickHook( void );
\r
107 /*-----------------------------------------------------------*/
\r
109 /* See the documentation page for this demo on the FreeRTOS.org web site for
\r
110 full information - including hardware setup requirements. */
\r
114 /* Call the Renesas provided setup. */
\r
117 lcd_display( LCD_LINE1, "FreeRTOS" );
\r
119 /* The configCREATE_LOW_POWER_DEMO setting is described in FreeRTOSConfig.h. */
\r
120 #if configCREATE_LOW_POWER_DEMO == 1
\r
122 lcd_display( LCD_LINE2, "LP Demo" );
\r
127 lcd_display( LCD_LINE2, "Ful Demo" );
\r
132 /*-----------------------------------------------------------*/
\r
134 void vApplicationMallocFailedHook( void )
\r
136 /* vApplicationMallocFailedHook() will only be called if
\r
137 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
138 function that will get called if a call to pvPortMalloc() fails.
\r
139 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
140 timer or semaphore is created. It is also called by various parts of the
\r
141 demo application. If heap_1.c, heap_2.c or heap_4.c are used, then the size
\r
142 of the heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE
\r
143 in FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
144 to query the size of free heap space that remains (although it does not
\r
145 provide information on how the remaining heap might be fragmented). */
\r
146 taskDISABLE_INTERRUPTS();
\r
149 /*-----------------------------------------------------------*/
\r
151 void vApplicationIdleHook( void )
\r
153 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
154 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
155 task. It is essential that code added to this hook function never attempts
\r
156 to block in any way (for example, call xQueueReceive() with a block time
\r
157 specified, or call vTaskDelay()). If the application makes use of the
\r
158 vTaskDelete() API function (as this demo application does) then it is also
\r
159 important that vApplicationIdleHook() is permitted to return to its calling
\r
160 function, because it is the responsibility of the idle task to clean up
\r
161 memory allocated by the kernel to any task that has since been deleted. */
\r
163 /*-----------------------------------------------------------*/
\r
165 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
167 ( void ) pcTaskName;
\r
170 /* Run time stack overflow checking is performed if
\r
171 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook function is
\r
172 called if a stack overflow is detected. */
\r
173 taskDISABLE_INTERRUPTS();
\r
176 /*-----------------------------------------------------------*/
\r
178 void vApplicationTickHook( void )
\r
180 /* This function will be called by each tick interrupt if
\r
181 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
182 added here, but the tick hook is called from an interrupt context, so
\r
183 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
184 functions can be used (those that end in FromISR()). */
\r
186 /*-----------------------------------------------------------*/
\r
188 void vAssertCalled( void )
\r
190 volatile unsigned long ul = 0;
\r
192 taskENTER_CRITICAL();
\r
194 /* Set ul to a non-zero value using the debugger to step out of this
\r
198 __asm volatile( "NOP" );
\r
201 taskEXIT_CRITICAL();
\r