2 FreeRTOS V9.0.1 - Copyright (C) 2017 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 simple blinky style project,
\r
72 * and a more comprehensive test and demo application. The
\r
73 * configCREATE_SIMPLE_TICKLESS_DEMO setting (defined in FreeRTOSConfig.h) is
\r
74 * used to select between the two. The simply blinky demo is implemented and
\r
75 * described in main_blinky.c. The more comprehensive test and demo application
\r
76 * is implemented and described in main_full.c.
\r
78 * The comprehensive demo uses FreeRTOS+CLI to create a simple command line
\r
79 * interface through a UART.
\r
81 * The blinky demo uses FreeRTOS's tickless idle mode to reduce power
\r
82 * consumption. See the notes on the web page below regarding the difference
\r
83 * in power saving that can be achieved between using the generic tickless
\r
84 * implementation (as used by the blinky demo) and a tickless implementation
\r
85 * that is tailored specifically to the MSP432.
\r
87 * This file implements the code that is not demo specific.
\r
89 * See http://www.FreeRTOS.org/TI_MSP432_Free_RTOS_Demo.html for instructions.
\r
93 /* Standard includes. */
\r
96 /* Kernel includes. */
\r
97 #include "FreeRTOS.h"
\r
100 /*-----------------------------------------------------------*/
\r
103 * Set up the hardware ready to run this demo.
\r
105 static void prvSetupHardware( void );
\r
108 * main_blinky() is used when configCREATE_SIMPLE_TICKLESS_DEMO is set to 1.
\r
109 * main_full() is used when configCREATE_SIMPLE_TICKLESS_DEMO is set to 0.
\r
111 extern void main_blinky( void );
\r
112 extern void main_full( void );
\r
114 /*-----------------------------------------------------------*/
\r
118 /* See http://www.FreeRTOS.org/TI_MSP432_Free_RTOS_Demo.html for instructions. */
\r
120 /* Prepare the hardware to run this demo. */
\r
121 prvSetupHardware();
\r
123 /* The configCREATE_SIMPLE_TICKLESS_DEMO setting is described at the top
\r
125 #if( configCREATE_SIMPLE_TICKLESS_DEMO == 1 )
\r
137 /*-----------------------------------------------------------*/
\r
139 static void prvSetupHardware( void )
\r
141 extern void FPU_enableModule( void );
\r
143 /* The clocks are not configured here, but inside main_full() and
\r
144 main_blinky() as the full demo uses a fast clock and the blinky demo uses
\r
147 /* Stop the watchdog timer. */
\r
148 MAP_WDT_A_holdTimer();
\r
150 /* Ensure the FPU is enabled. */
\r
151 FPU_enableModule();
\r
153 /* Selecting P1.2 and P1.3 in UART mode and P1.0 as output (LED) */
\r
154 MAP_GPIO_setAsPeripheralModuleFunctionInputPin( GPIO_PORT_P1, GPIO_PIN2 | GPIO_PIN3, GPIO_PRIMARY_MODULE_FUNCTION );
\r
155 MAP_GPIO_setOutputLowOnPin( GPIO_PORT_P1, GPIO_PIN0 );
\r
156 MAP_GPIO_setAsOutputPin( GPIO_PORT_P1, GPIO_PIN0 );
\r
158 /*-----------------------------------------------------------*/
\r
160 void vApplicationMallocFailedHook( void )
\r
162 /* vApplicationMallocFailedHook() will only be called if
\r
163 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
164 function that will get called if a call to pvPortMalloc() fails.
\r
165 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
166 timer or semaphore is created. It is also called by various parts of the
\r
167 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
168 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
169 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
170 to query the size of free heap space that remains (although it does not
\r
171 provide information on how the remaining heap might be fragmented). */
\r
172 taskDISABLE_INTERRUPTS();
\r
175 /*-----------------------------------------------------------*/
\r
177 void vApplicationIdleHook( void )
\r
179 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
180 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
181 task. It is essential that code added to this hook function never attempts
\r
182 to block in any way (for example, call xQueueReceive() with a block time
\r
183 specified, or call vTaskDelay()). If the application makes use of the
\r
184 vTaskDelete() API function (as this demo application does) then it is also
\r
185 important that vApplicationIdleHook() is permitted to return to its calling
\r
186 function, because it is the responsibility of the idle task to clean up
\r
187 memory allocated by the kernel to any task that has since been deleted. */
\r
189 /*-----------------------------------------------------------*/
\r
191 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
193 ( void ) pcTaskName;
\r
196 /* Run time stack overflow checking is performed if
\r
197 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
198 function is called if a stack overflow is detected. */
\r
199 taskDISABLE_INTERRUPTS();
\r
202 /*-----------------------------------------------------------*/
\r
204 void *malloc( size_t xSize )
\r
206 /* There should not be a heap defined, so trap any attempts to call
\r
208 Interrupt_disableMaster();
\r
211 /*-----------------------------------------------------------*/
\r