2 FreeRTOS V8.2.1 - Copyright (C) 2015 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
71 /******************************************************************************
\r
72 * NOTE 1: This project provides two demo applications. A simple blinky
\r
73 * style project, and a more comprehensive test and demo application. The
\r
74 * configCREATE_SIMPLE_TICKLESS_DEMO setting in FreeRTOSConfig.h is used to
\r
75 * select between the two. See the notes on using
\r
76 * configCREATE_SIMPLY_BLINKY_DEMO_ONLY in main.c. This file implements the
\r
77 * comprehensive version.
\r
79 * NOTE 2: This file only contains the source code that is specific to the
\r
80 * full demo. Generic functions, such FreeRTOS hook functions, and functions
\r
81 * required to configure the hardware, are defined in main.c.
\r
83 * See http://www.FreeRTOS.org/TI_MSP432_Free_RTOS_Demo.html for instructions.
\r
85 ******************************************************************************
\r
87 * main_full() creates all the demo application tasks and software timers, then
\r
88 * starts the scheduler. The web documentation provides more details of the
\r
89 * standard demo application tasks, which provide no particular functionality,
\r
90 * but do provide a good example of how to use the FreeRTOS API.
\r
92 * In addition to the standard demo tasks, the following tasks and tests are
\r
93 * defined and/or created within this file:
\r
95 * FreeRTOS+CLI command console. The command console is access through the
\r
96 * UART at 19200 baud. For reasons of robustness testing the UART driver is
\r
97 * deliberately written to be inefficient and should not be used as a template
\r
98 * for a production driver. Type "help" to see a list of registered commands.
\r
99 * The FreeRTOS+CLI license is different to the FreeRTOS license, see
\r
100 * http://www.FreeRTOS.org/cli for license and usage details.
\r
102 * "Reg test" tasks - These fill both the core and floating point registers with
\r
103 * known values, then check that each register maintains its expected value for
\r
104 * the lifetime of the task. Each task uses a different set of values. The reg
\r
105 * test tasks execute with a very low priority, so get preempted very
\r
106 * frequently. A register containing an unexpected value is indicative of an
\r
107 * error in the context switching mechanism.
\r
109 * "Check" task - The check task period is initially set to three seconds. The
\r
110 * task checks that all the standard demo tasks, and the register check tasks,
\r
111 * are not only still executing, but are executing without reporting any errors.
\r
112 * If the check task discovers that a task has either stalled, or reported an
\r
113 * error, then it changes its own execution period from the initial three
\r
114 * seconds, to just 200ms. The check task also toggles an LED each time it is
\r
115 * called. This provides a visual indication of the system status: If the LED
\r
116 * toggles every three seconds, then no issues have been discovered. If the LED
\r
117 * toggles every 200ms, then an issue has been discovered with at least one
\r
121 /* Standard includes. */
\r
124 /* Kernel includes. */
\r
125 #include "FreeRTOS.h"
\r
127 #include "timers.h"
\r
128 #include "semphr.h"
\r
130 /* Standard demo application includes. */
\r
132 #include "semtest.h"
\r
133 #include "countsem.h"
\r
134 #include "GenQTest.h"
\r
135 #include "recmutex.h"
\r
136 #include "partest.h"
\r
137 #include "serial.h"
\r
138 #include "TimerDemo.h"
\r
139 #include "IntQueue.h"
\r
140 #include "EventGroupsDemo.h"
\r
141 #include "TaskNotify.h"
\r
142 #include "IntSemTest.h"
\r
144 /* Priorities for the demo application tasks. */
\r
145 #define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1UL )
\r
146 #define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2UL )
\r
147 #define mainCREATOR_TASK_PRIORITY ( tskIDLE_PRIORITY + 3UL )
\r
148 #define mainFLOP_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
149 #define mainUART_COMMAND_CONSOLE_STACK_SIZE ( configMINIMAL_STACK_SIZE * 2UL )
\r
150 #define mainCOM_TEST_TASK_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
151 #define mainCHECK_TASK_PRIORITY ( configMAX_PRIORITIES - 1 )
\r
152 #define mainQUEUE_OVERWRITE_PRIORITY ( tskIDLE_PRIORITY )
\r
154 /* The priority used by the UART command console task. */
\r
155 #define mainUART_COMMAND_CONSOLE_TASK_PRIORITY ( configMAX_PRIORITIES - 2 )
\r
157 /* A block time of zero simply means "don't block". */
\r
158 #define mainDONT_BLOCK ( 0UL )
\r
160 /* The period after which the check timer will expire, in ms, provided no errors
\r
161 have been reported by any of the standard demo tasks. ms are converted to the
\r
162 equivalent in ticks using the portTICK_PERIOD_MS constant. */
\r
163 #define mainNO_ERROR_CHECK_TASK_PERIOD ( pdMS_TO_TICKS( 3000UL ) )
\r
165 /* The period at which the check timer will expire, in ms, if an error has been
\r
166 reported in one of the standard demo tasks. ms are converted to the equivalent
\r
167 in ticks using the portTICK_PERIOD_MS constant. */
\r
168 #define mainERROR_CHECK_TASK_PERIOD ( pdMS_TO_TICKS( 200UL ) )
\r
170 /* Parameters that are passed into the register check tasks solely for the
\r
171 purpose of ensuring parameters are passed into tasks correctly. */
\r
172 #define mainREG_TEST_TASK_1_PARAMETER ( ( void * ) 0x12345678 )
\r
173 #define mainREG_TEST_TASK_2_PARAMETER ( ( void * ) 0x87654321 )
\r
175 /* The base period used by the timer test tasks. */
\r
176 #define mainTIMER_TEST_PERIOD ( 50 )
\r
178 /* Dimensions the queue in which characters received from the UART are
\r
180 #define mainRX_QUEUE_LENGTH 10
\r
182 /*-----------------------------------------------------------*/
\r
186 * The check task, as described at the top of this file.
\r
188 static void prvCheckTask( void *pvParameters );
\r
191 * Register check tasks, and the tasks used to write over and check the contents
\r
192 * of the FPU registers, as described at the top of this file. The nature of
\r
193 * these files necessitates that they are written in an assembly file, but the
\r
194 * entry points are kept in the C file for the convenience of checking the task
\r
197 static void prvRegTestTaskEntry1( void *pvParameters );
\r
198 extern void vRegTest1Implementation( void );
\r
199 static void prvRegTestTaskEntry2( void *pvParameters );
\r
200 extern void vRegTest2Implementation( void );
\r
203 * Register commands that can be used with FreeRTOS+CLI. The commands are
\r
204 * defined in CLI-Commands.c and File-Related-CLI-Command.c respectively.
\r
206 extern void vRegisterSampleCLICommands( void );
\r
209 * The task that manages the FreeRTOS+CLI input and output.
\r
211 extern void vUARTCommandConsoleStart( uint16_t usStackSize, UBaseType_t uxPriority );
\r
214 * When the full demo is build the idle hook is used to create some timers that
\r
215 * cannot be created in main() because the timer demo tasks need the entire
\r
218 void vFullDemoIdleHook( void );
\r
221 * The full demo configures the clocks for maximum frequency, wheras the blinky
\r
222 * demo uses a slower clock as it also uses low power features.
\r
224 static void prvConfigureClocks( void );
\r
226 /*-----------------------------------------------------------*/
\r
228 /* The following two variables are used to communicate the status of the
\r
229 register check tasks to the check task. If the variables keep incrementing,
\r
230 then the register check tasks has not discovered any errors. If a variable
\r
231 stops incrementing, then an error has been found. */
\r
232 volatile unsigned long ulRegTest1LoopCounter = 0UL, ulRegTest2LoopCounter = 0UL;
\r
234 /*-----------------------------------------------------------*/
\r
236 void main_full( void )
\r
238 /* This demo sets the clock to its maximum. The blinky demo uses as slower
\r
239 clock as it uses low power features. */
\r
240 prvConfigureClocks();
\r
242 /* Init the serial port for use by the CLI. The baud rate parameter is not
\r
243 used so set to 0 to make this obvious. */
\r
244 xSerialPortInitMinimal( 0, mainRX_QUEUE_LENGTH );
\r
246 /* Start all the other standard demo/test tasks. They have not particular
\r
247 functionality, but do demonstrate how to use the FreeRTOS API and test the
\r
249 vStartInterruptQueueTasks();
\r
251 vStartCountingSemaphoreTasks();
\r
252 vStartGenericQueueTasks( tskIDLE_PRIORITY );
\r
253 vStartRecursiveMutexTasks();
\r
254 vStartSemaphoreTasks( mainSEM_TEST_PRIORITY );
\r
255 vStartTimerDemoTask( mainTIMER_TEST_PERIOD );
\r
256 vStartEventGroupTasks();
\r
257 vStartTaskNotifyTask();
\r
258 vStartInterruptSemaphoreTasks();
\r
260 /* Note - the set of standard demo tasks contains two versions of
\r
261 vStartMathTasks.c. One is defined in flop.c, and uses double precision
\r
262 floating point numbers and variables. The other is defined in sp_flop.c,
\r
263 and uses single precision floating point numbers and variables. sp_flop.
\r
264 c should be included in this project. */
\r
265 vStartMathTasks( mainFLOP_TASK_PRIORITY );
\r
267 /* Start the tasks that implements the command console on the UART, as
\r
268 described above. */
\r
269 vUARTCommandConsoleStart( mainUART_COMMAND_CONSOLE_STACK_SIZE, mainUART_COMMAND_CONSOLE_TASK_PRIORITY );
\r
271 /* Register the standard CLI commands. */
\r
272 vRegisterSampleCLICommands();
\r
274 /* Create the register check tasks, as described at the top of this file */
\r
275 xTaskCreate( prvRegTestTaskEntry1, "Reg1", configMINIMAL_STACK_SIZE, mainREG_TEST_TASK_1_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
276 xTaskCreate( prvRegTestTaskEntry2, "Reg2", configMINIMAL_STACK_SIZE, mainREG_TEST_TASK_2_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
278 /* Create the task that performs the 'check' functionality, as described at
\r
279 the top of this file. */
\r
280 xTaskCreate( prvCheckTask, "Check", configMINIMAL_STACK_SIZE, NULL, mainCHECK_TASK_PRIORITY, NULL );
\r
282 /* Start the scheduler. */
\r
283 vTaskStartScheduler();
\r
285 /* If all is well, the scheduler will now be running, and the following
\r
286 line will never be reached. If the following line does execute, then
\r
287 there was either insufficient FreeRTOS heap memory available for the idle
\r
288 and/or timer tasks to be created, or vTaskStartScheduler() was called from
\r
289 User mode. See the memory management section on the FreeRTOS web site for
\r
290 more details on the FreeRTOS heap http://www.freertos.org/a00111.html. The
\r
291 mode from which main() is called is set in the C start up code and must be
\r
292 a privileged mode (not user mode). */
\r
295 /*-----------------------------------------------------------*/
\r
297 static void prvCheckTask( void *pvParameters )
\r
299 TickType_t xDelayPeriod = mainNO_ERROR_CHECK_TASK_PERIOD;
\r
300 TickType_t xLastExecutionTime;
\r
301 static unsigned long ulLastRegTest1Value = 0, ulLastRegTest2Value = 0;
\r
302 unsigned long ulErrorFound = pdFALSE;
\r
304 /* Just to stop compiler warnings. */
\r
305 ( void ) pvParameters;
\r
307 /* Initialise xLastExecutionTime so the first call to vTaskDelayUntil()
\r
308 works correctly. */
\r
309 xLastExecutionTime = xTaskGetTickCount();
\r
311 /* Cycle for ever, delaying then checking all the other tasks are still
\r
312 operating without error. The onboard LED is toggled on each iteration.
\r
313 If an error is detected then the delay period is decreased from
\r
314 mainNO_ERROR_CHECK_TASK_PERIOD to mainERROR_CHECK_TASK_PERIOD. This has the
\r
315 effect of increasing the rate at which the onboard LED toggles, and in so
\r
316 doing gives visual feedback of the system status. */
\r
319 /* Delay until it is time to execute again. */
\r
320 vTaskDelayUntil( &xLastExecutionTime, xDelayPeriod );
\r
322 /* Check all the demo tasks to ensure that they are all still running,
\r
323 and that none have detected an error. */
\r
324 if( xAreIntQueueTasksStillRunning() != pdTRUE )
\r
326 ulErrorFound |= 1UL << 0UL;
\r
329 if( xAreMathsTaskStillRunning() != pdTRUE )
\r
331 ulErrorFound |= 1UL << 1UL;
\r
334 if( xAreGenericQueueTasksStillRunning() != pdTRUE )
\r
336 ulErrorFound |= 1UL << 5UL;
\r
339 if( xAreRecursiveMutexTasksStillRunning() != pdTRUE )
\r
341 ulErrorFound |= 1UL << 6UL;
\r
344 if( xAreSemaphoreTasksStillRunning() != pdTRUE )
\r
346 ulErrorFound |= 1UL << 8UL;
\r
349 if( xAreCountingSemaphoreTasksStillRunning() != pdTRUE )
\r
351 ulErrorFound |= 1UL << 10UL;
\r
354 if( xAreInterruptSemaphoreTasksStillRunning() != pdTRUE )
\r
356 ulErrorFound |= 1UL << 14UL;
\r
359 if( xAreTimerDemoTasksStillRunning( ( TickType_t ) mainNO_ERROR_CHECK_TASK_PERIOD ) != pdPASS )
\r
361 ulErrorFound |= 1UL << 9UL;
\r
364 if( xAreEventGroupTasksStillRunning() != pdPASS )
\r
366 ulErrorFound |= 1UL << 12UL;
\r
369 if( xAreTaskNotificationTasksStillRunning() != pdTRUE )
\r
371 ulErrorFound |= 1UL << 13UL;
\r
374 /* Check that the register test 1 task is still running. */
\r
375 if( ulLastRegTest1Value == ulRegTest1LoopCounter )
\r
377 ulErrorFound |= 1UL << 15UL;
\r
379 ulLastRegTest1Value = ulRegTest1LoopCounter;
\r
381 /* Check that the register test 2 task is still running. */
\r
382 if( ulLastRegTest2Value == ulRegTest2LoopCounter )
\r
384 ulErrorFound |= 1UL << 16UL;
\r
386 ulLastRegTest2Value = ulRegTest2LoopCounter;
\r
388 /* Toggle the check LED to give an indication of the system status. If
\r
389 the LED toggles every mainNO_ERROR_CHECK_TASK_PERIOD milliseconds then
\r
390 everything is ok. A faster toggle indicates an error. */
\r
391 configTOGGLE_LED();
\r
393 if( ulErrorFound != pdFALSE )
\r
395 /* An error has been detected in one of the tasks - flash the LED
\r
396 at a higher frequency to give visible feedback that something has
\r
397 gone wrong (it might just be that the loop back connector required
\r
398 by the comtest tasks has not been fitted). */
\r
399 xDelayPeriod = mainERROR_CHECK_TASK_PERIOD;
\r
403 /*-----------------------------------------------------------*/
\r
405 static void prvRegTestTaskEntry1( void *pvParameters )
\r
407 /* Although the regtest task is written in assembler, its entry point is
\r
408 written in C for convenience of checking the task parameter is being passed
\r
410 if( pvParameters == mainREG_TEST_TASK_1_PARAMETER )
\r
412 /* Start the part of the test that is written in assembler. */
\r
413 vRegTest1Implementation();
\r
416 /* The following line will only execute if the task parameter is found to
\r
417 be incorrect. The check timer will detect that the regtest loop counter is
\r
418 not being incremented and flag an error. */
\r
419 vTaskDelete( NULL );
\r
421 /*-----------------------------------------------------------*/
\r
423 static void prvRegTestTaskEntry2( void *pvParameters )
\r
425 /* Although the regtest task is written in assembler, its entry point is
\r
426 written in C for convenience of checking the task parameter is being passed
\r
428 if( pvParameters == mainREG_TEST_TASK_2_PARAMETER )
\r
430 /* Start the part of the test that is written in assembler. */
\r
431 vRegTest2Implementation();
\r
434 /* The following line will only execute if the task parameter is found to
\r
435 be incorrect. The check timer will detect that the regtest loop counter is
\r
436 not being incremented and flag an error. */
\r
437 vTaskDelete( NULL );
\r
439 /*-----------------------------------------------------------*/
\r
441 static void prvConfigureClocks( void )
\r
443 /* The full demo configures the clocks for maximum frequency, wheras the
\r
444 blinky demo uses a slower clock as it also uses low power features. Maximum
\r
445 freqency also needs more voltage.
\r
447 From the datashee: For AM_LDO_VCORE1 and AM_DCDC_VCORE1 modes, the maximum
\r
448 CPU operating frequency is 48 MHz and maximum input clock frequency for
\r
449 peripherals is 24 MHz. */
\r
450 PCM_setCoreVoltageLevel( PCM_VCORE1 );
\r
451 CS_setDCOCenteredFrequency( CS_DCO_FREQUENCY_48 );
\r
452 CS_initClockSignal( CS_HSMCLK, CS_DCOCLK_SELECT, CS_CLOCK_DIVIDER_1 );
\r
453 CS_initClockSignal( CS_SMCLK, CS_DCOCLK_SELECT, CS_CLOCK_DIVIDER_1 );
\r
454 CS_initClockSignal( CS_MCLK, CS_DCOCLK_SELECT, CS_CLOCK_DIVIDER_1 );
\r
455 CS_initClockSignal( CS_ACLK, CS_REFOCLK_SELECT, CS_CLOCK_DIVIDER_1 );
\r
457 /*-----------------------------------------------------------*/
\r
459 #if( configCREATE_SIMPLE_TICKLESS_DEMO == 0 )
\r
461 void vApplicationTickHook( void )
\r
463 /* This function will be called by each tick interrupt if
\r
464 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
465 added here, but the tick hook is called from an interrupt context, so
\r
466 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
467 functions can be used (those that end in FromISR()). */
\r
469 /* The full demo includes a software timer demo/test that requires
\r
470 prodding periodically from the tick interrupt. */
\r
471 vTimerPeriodicISRTests();
\r
473 /* Call the periodic event group from ISR demo. */
\r
474 vPeriodicEventGroupsProcessing();
\r
476 /* Use task notifications from an interrupt. */
\r
477 xNotifyTaskFromISR();
\r
479 /* Use mutexes from interrupts. */
\r
480 vInterruptSemaphorePeriodicTest();
\r
484 /*-----------------------------------------------------------*/
\r