2 FreeRTOS V8.0.0:rc1 - 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 simple blinky style project,
\r
68 * and a more comprehensive test and demo application. The
\r
69 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in this file) is used to
\r
70 * select between the two. The simply blinky demo is implemented and described
\r
71 * in main_blinky.c. The more comprehensive test and demo application is
\r
72 * implemented and described in main_full.c.
\r
74 * This file implements the code that is not demo specific, including the
\r
75 * hardware setup and FreeRTOS hook functions.
\r
78 /* Kernel includes. */
\r
79 #include "FreeRTOS.h"
\r
82 /* Standard demo includes. */
\r
83 #include "partest.h"
\r
85 /* Hardware specific includes. */
\r
86 #include "ConfigPerformance.h"
\r
88 /* Core configuratin fuse settings */
\r
89 #pragma config FPLLMUL = MUL_20, FPLLIDIV = DIV_2, FPLLODIV = DIV_1, FWDTEN = OFF
\r
90 #pragma config POSCMOD = HS, FNOSC = PRIPLL, FPBDIV = DIV_2
\r
91 #pragma config CP = OFF, BWP = OFF, PWP = OFF
\r
93 /* Additional config fuse settings for other supported processors */
\r
94 #if defined(__32MX460F512L__)
\r
95 #pragma config UPLLEN = OFF
\r
96 #elif defined(__32MX795F512L__)
\r
97 #pragma config UPLLEN = OFF
\r
98 #pragma config FSRSSEL = PRIORITY_7
\r
101 /*-----------------------------------------------------------*/
\r
103 /* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,
\r
104 or 0 to run the more comprehensive test and demo application. */
\r
105 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 1
\r
107 /*-----------------------------------------------------------*/
\r
110 * Set up the hardware ready to run this demo.
\r
112 static void prvSetupHardware( void );
\r
115 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
116 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
118 extern void main_blinky( void );
\r
119 extern void main_full( void );
\r
121 /*-----------------------------------------------------------*/
\r
124 * Create the demo tasks then start the scheduler.
\r
128 /* Prepare the hardware to run this demo. */
\r
129 prvSetupHardware();
\r
131 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
133 #if mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1
\r
145 /*-----------------------------------------------------------*/
\r
147 static void prvSetupHardware( void )
\r
149 /* Configure the hardware for maximum performance. */
\r
150 vHardwareConfigurePerformance();
\r
152 /* Setup to use the external interrupt controller. */
\r
153 vHardwareUseMultiVectoredInterrupts();
\r
155 portDISABLE_INTERRUPTS();
\r
157 /* Setup the digital IO for the LED's. */
\r
158 vParTestInitialise();
\r
160 /*-----------------------------------------------------------*/
\r
162 void vApplicationMallocFailedHook( void )
\r
164 /* vApplicationMallocFailedHook() will only be called if
\r
165 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
166 function that will get called if a call to pvPortMalloc() fails.
\r
167 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
168 timer or semaphore is created. It is also called by various parts of the
\r
169 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
170 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
171 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
172 to query the size of free heap space that remains (although it does not
\r
173 provide information on how the remaining heap might be fragmented). */
\r
174 taskDISABLE_INTERRUPTS();
\r
177 /*-----------------------------------------------------------*/
\r
179 void vApplicationIdleHook( void )
\r
181 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
182 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
183 task. It is essential that code added to this hook function never attempts
\r
184 to block in any way (for example, call xQueueReceive() with a block time
\r
185 specified, or call vTaskDelay()). If the application makes use of the
\r
186 vTaskDelete() API function (as this demo application does) then it is also
\r
187 important that vApplicationIdleHook() is permitted to return to its calling
\r
188 function, because it is the responsibility of the idle task to clean up
\r
189 memory allocated by the kernel to any task that has since been deleted. */
\r
191 /*-----------------------------------------------------------*/
\r
193 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
195 ( void ) pcTaskName;
\r
198 /* Run time task stack overflow checking is performed if
\r
199 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook function is
\r
200 called if a task stack overflow is detected. Note the system/interrupt
\r
201 stack is not checked. */
\r
202 taskDISABLE_INTERRUPTS();
\r
205 /*-----------------------------------------------------------*/
\r
207 void vApplicationTickHook( void )
\r
209 /* This function will be called by each tick interrupt if
\r
210 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
211 added here, but the tick hook is called from an interrupt context, so
\r
212 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
213 functions can be used (those that end in FromISR()). */
\r
215 /*-----------------------------------------------------------*/
\r
217 void _general_exception_handler( unsigned long ulCause, unsigned long ulStatus )
\r
219 /* This overrides the definition provided by the kernel. Other exceptions
\r
220 should be handled here. */
\r
223 /*-----------------------------------------------------------*/
\r
225 void vAssertCalled( const char * pcFile, unsigned long ulLine )
\r
227 volatile unsigned long ul = 0;
\r
232 __asm volatile( "di" );
\r
234 /* Set ul to a non-zero value using the debugger to step out of this
\r
241 __asm volatile( "ei" );
\r