2 FreeRTOS V7.2.0 - Copyright (C) 2012 Real Time Engineers Ltd.
\r
5 ***************************************************************************
\r
7 * FreeRTOS tutorial books are available in pdf and paperback. *
\r
8 * Complete, revised, and edited pdf reference manuals are also *
\r
11 * Purchasing FreeRTOS documentation will not only help you, by *
\r
12 * ensuring you get running as quickly as possible and with an *
\r
13 * in-depth knowledge of how to use FreeRTOS, it will also help *
\r
14 * the FreeRTOS project to continue with its mission of providing *
\r
15 * professional grade, cross platform, de facto standard solutions *
\r
16 * for microcontrollers - completely free of charge! *
\r
18 * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *
\r
20 * Thank you for using FreeRTOS, and thank you for your support! *
\r
22 ***************************************************************************
\r
25 This file is part of the FreeRTOS distribution.
\r
27 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
28 the terms of the GNU General Public License (version 2) as published by the
\r
29 Free Software Foundation AND MODIFIED BY the FreeRTOS exception.
\r
30 >>>NOTE<<< The modification to the GPL is included to allow you to
\r
31 distribute a combined work that includes FreeRTOS without being obliged to
\r
32 provide the source code for proprietary components outside of the FreeRTOS
\r
33 kernel. FreeRTOS is distributed in the hope that it will be useful, but
\r
34 WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
\r
35 or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
\r
36 more details. You should have received a copy of the GNU General Public
\r
37 License and the FreeRTOS license exception along with FreeRTOS; if not it
\r
38 can be viewed here: http://www.freertos.org/a00114.html and also obtained
\r
39 by writing to Richard Barry, contact details for whom are available on the
\r
44 ***************************************************************************
\r
46 * Having a problem? Start by reading the FAQ "My application does *
\r
47 * not run, what could be wrong? *
\r
49 * http://www.FreeRTOS.org/FAQHelp.html *
\r
51 ***************************************************************************
\r
54 http://www.FreeRTOS.org - Documentation, training, latest information,
\r
55 license and contact details.
\r
57 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
58 including FreeRTOS+Trace - an indispensable productivity tool.
\r
60 Real Time Engineers ltd license FreeRTOS to High Integrity Systems, who sell
\r
61 the code with commercial support, indemnification, and middleware, under
\r
62 the OpenRTOS brand: http://www.OpenRTOS.com. High Integrity Systems also
\r
63 provide a safety engineered and independently SIL3 certified version under
\r
64 the SafeRTOS brand: http://www.SafeRTOS.com.
\r
67 /******************************************************************************
\r
68 * This project provides two demo applications. A simple blinky style project,
\r
69 * and a more comprehensive test and demo application. The
\r
70 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in this file) is used to
\r
71 * select between the two. The simply blinky demo is implemented and described
\r
72 * in main_blinky.c. The more comprehensive test and demo application is
\r
73 * implemented and described in main_full.c.
\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 /* Standard demo includes. */
\r
84 #include "partest.h"
\r
86 /* Core configuratin fuse settings */
\r
87 #pragma config FPLLMUL = MUL_20, FPLLIDIV = DIV_2, FPLLODIV = DIV_1, FWDTEN = OFF
\r
88 #pragma config POSCMOD = HS, FNOSC = PRIPLL, FPBDIV = DIV_2
\r
89 #pragma config CP = OFF, BWP = OFF, PWP = OFF
\r
91 /* Additional config fuse settings for other supported processors */
\r
92 #if defined(__32MX460F512L__)
\r
93 #pragma config UPLLEN = OFF
\r
94 #elif defined(__32MX795F512L__)
\r
95 #pragma config UPLLEN = OFF
\r
96 #pragma config FSRSSEL = PRIORITY_7
\r
99 /*-----------------------------------------------------------*/
\r
101 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
102 or 0 to run the more comprehensive test and demo application. */
\r
103 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 1
\r
105 /*-----------------------------------------------------------*/
\r
108 * Set up the hardware ready to run this demo.
\r
110 static void prvSetupHardware( void );
\r
113 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
114 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
116 extern void main_blinky( void );
\r
117 extern void main_full( void );
\r
119 /*-----------------------------------------------------------*/
\r
122 * Create the demo tasks then start the scheduler.
\r
126 /* Prepare the hardware to run this demo. */
\r
127 prvSetupHardware();
\r
129 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
131 #if mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1
\r
143 /*-----------------------------------------------------------*/
\r
145 static void prvSetupHardware( void )
\r
147 /* Set the system and peripheral bus speeds and enable the program cache*/
\r
148 SYSTEMConfigPerformance( configCPU_CLOCK_HZ - 1 );
\r
149 mOSCSetPBDIV( OSC_PB_DIV_2 );
\r
151 /* Setup to use the external interrupt controller. */
\r
152 INTEnableSystemMultiVectoredInt();
\r
154 portDISABLE_INTERRUPTS();
\r
156 /* Setup the digital IO for the LED's. */
\r
157 vParTestInitialise();
\r
159 /*-----------------------------------------------------------*/
\r
161 void vApplicationMallocFailedHook( void )
\r
163 /* vApplicationMallocFailedHook() will only be called if
\r
164 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
165 function that will get called if a call to pvPortMalloc() fails.
\r
166 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
167 timer or semaphore is created. It is also called by various parts of the
\r
168 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
169 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
170 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
171 to query the size of free heap space that remains (although it does not
\r
172 provide information on how the remaining heap might be fragmented). */
\r
173 taskDISABLE_INTERRUPTS();
\r
176 /*-----------------------------------------------------------*/
\r
178 void vApplicationIdleHook( void )
\r
180 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
181 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
182 task. It is essential that code added to this hook function never attempts
\r
183 to block in any way (for example, call xQueueReceive() with a block time
\r
184 specified, or call vTaskDelay()). If the application makes use of the
\r
185 vTaskDelete() API function (as this demo application does) then it is also
\r
186 important that vApplicationIdleHook() is permitted to return to its calling
\r
187 function, because it is the responsibility of the idle task to clean up
\r
188 memory allocated by the kernel to any task that has since been deleted. */
\r
190 /*-----------------------------------------------------------*/
\r
192 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName )
\r
194 ( void ) pcTaskName;
\r
197 /* Run time task 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 task stack overflow is detected. Note the system/interrupt
\r
200 stack is not checked. */
\r
201 taskDISABLE_INTERRUPTS();
\r
204 /*-----------------------------------------------------------*/
\r
206 void vApplicationTickHook( void )
\r
208 /* This function will be called by each tick interrupt if
\r
209 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
210 added here, but the tick hook is called from an interrupt context, so
\r
211 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
212 functions can be used (those that end in FromISR()). */
\r
214 /*-----------------------------------------------------------*/
\r
216 void _general_exception_handler( unsigned long ulCause, unsigned long ulStatus )
\r
218 /* This overrides the definition provided by the kernel. Other exceptions
\r
219 should be handled here. */
\r
222 /*-----------------------------------------------------------*/
\r