2 FreeRTOS V9.0.0rc1 - Copyright (C) 2016 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 * NOTE 1: This project provides two demo applications. A simple blinky
\r
72 * style project, and a more comprehensive test and demo application. The
\r
73 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting in main.c is used to
\r
74 * select between the two. See the notes on using
\r
75 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY in main.c. This file implements the
\r
76 * comprehensive version.
\r
78 * NOTE 2: This file only contains the source code that is specific to the
\r
79 * full demo. Generic functions, such FreeRTOS hook functions, and functions
\r
80 * required to configure the hardware, are defined in main.c.
\r
82 ******************************************************************************
\r
84 * main_full() creates a set of demo application tasks and software timers, then
\r
85 * starts the scheduler. The web documentation provides more details of the
\r
86 * standard demo application tasks, which provide no particular functionality,
\r
87 * but do provide a good example of how to use the FreeRTOS API.
\r
89 * In addition to the standard demo tasks, the following tasks and tests are
\r
90 * defined and/or created within this file:
\r
92 * "FreeRTOS+CLI command console" - The command console uses SCI1 for its
\r
93 * input and output. The baud rate is set to 19200. Type "help" to see a list
\r
94 * of registered commands. The FreeRTOS+CLI license is different to the
\r
95 * FreeRTOS license, see http://www.FreeRTOS.org/cli for license and usage
\r
98 * "Reg test" tasks - These fill both the core and floating point registers with
\r
99 * known values, then check that each register maintains its expected value for
\r
100 * the lifetime of the task. Each task uses a different set of values. The reg
\r
101 * test tasks execute with a very low priority, so get preempted very
\r
102 * frequently. A register containing an unexpected value is indicative of an
\r
103 * error in the context switching mechanism.
\r
105 * "Check" task - The check task period is initially set to three seconds. The
\r
106 * task checks that all the standard demo tasks are not only still executing,
\r
107 * but are executing without reporting any errors. If the check task discovers
\r
108 * that a task has either stalled, or reported an error, then it changes its own
\r
109 * execution period from the initial three seconds, to just 200ms. The check
\r
110 * task also toggles an LED on each iteration of its loop. This provides a
\r
111 * visual indication of the system status: If the LED toggles every three
\r
112 * seconds, then no issues have been discovered. If the LED toggles every
\r
113 * 200ms, then an issue has been discovered with at least one task.
\r
116 /* Standard includes. */
\r
119 /* Kernel includes. */
\r
120 #include "FreeRTOS.h"
\r
122 #include "timers.h"
\r
123 #include "semphr.h"
\r
125 /* Standard demo application includes. */
\r
126 #include "semtest.h"
\r
127 #include "dynamic.h"
\r
128 #include "BlockQ.h"
\r
129 #include "blocktim.h"
\r
130 #include "countsem.h"
\r
131 #include "GenQTest.h"
\r
132 #include "recmutex.h"
\r
134 #include "partest.h"
\r
135 #include "comtest2.h"
\r
136 #include "serial.h"
\r
137 #include "QueueOverwrite.h"
\r
138 #include "IntQueue.h"
\r
139 #include "EventGroupsDemo.h"
\r
140 #include "TaskNotify.h"
\r
141 #include "IntSemTest.h"
\r
143 /* Renesas includes. */
\r
144 #include <rskrx113def.h>
\r
145 #include "r_cg_macrodriver.h"
\r
146 #include "r_cg_userdefine.h"
\r
148 /* Priorities for the demo application tasks. */
\r
149 #define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1UL )
\r
150 #define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2UL )
\r
151 #define mainCREATOR_TASK_PRIORITY ( tskIDLE_PRIORITY + 3UL )
\r
152 #define mainUART_COMMAND_CONSOLE_STACK_SIZE ( configMINIMAL_STACK_SIZE * 3UL )
\r
153 #define mainCHECK_TASK_PRIORITY ( configMAX_PRIORITIES - 1 )
\r
154 #define mainQUEUE_OVERWRITE_PRIORITY ( tskIDLE_PRIORITY )
\r
156 /* The priority used by the UART command console task. */
\r
157 #define mainUART_COMMAND_CONSOLE_TASK_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
159 /* The period after which the check timer will expire, in ms, provided no errors
\r
160 have been reported by any of the standard demo tasks. ms are converted to the
\r
161 equivalent in ticks using the portTICK_PERIOD_MS constant. */
\r
162 #define mainNO_ERROR_CHECK_TASK_PERIOD pdMS_TO_TICKS( 3000UL )
\r
164 /* The period at which the check timer will expire, in ms, if an error has been
\r
165 reported in one of the standard demo tasks. ms are converted to the equivalent
\r
166 in ticks using the portTICK_PERIOD_MS constant. */
\r
167 #define mainERROR_CHECK_TASK_PERIOD pdMS_TO_TICKS( 200UL )
\r
169 /* Parameters that are passed into the register check tasks solely for the
\r
170 purpose of ensuring parameters are passed into tasks correctly. */
\r
171 #define mainREG_TEST_1_PARAMETER ( ( void * ) 0x12121212UL )
\r
172 #define mainREG_TEST_2_PARAMETER ( ( void * ) 0x12345678UL )
\r
174 /* The base period used by the timer test tasks. */
\r
175 #define mainTIMER_TEST_PERIOD ( 50 )
\r
177 /*-----------------------------------------------------------*/
\r
180 * Entry point for the comprehensive demo (as opposed to the simple blinky
\r
183 void main_full( void );
\r
186 * The full demo includes some functionality called from the tick hook.
\r
188 void vFullDemoTickHook( void );
\r
191 * The check task, as described at the top of this file.
\r
193 static void prvCheckTask( void *pvParameters );
\r
196 * Register check tasks, and the tasks used to write over and check the contents
\r
197 * of the registers, as described at the top of this file. The nature of these
\r
198 * files necessitates that they are written in assembly, but the entry points
\r
199 * are kept in the C file for the convenience of checking the task parameter.
\r
201 static void prvRegTest1Task( void *pvParameters );
\r
202 static void prvRegTest2Task( void *pvParameters );
\r
203 static void prvRegTest1Implementation( void );
\r
204 static void prvRegTest2Implementation( void );
\r
207 * A high priority task that does nothing other than execute at a pseudo random
\r
208 * time to ensure the other test tasks don't just execute in a repeating
\r
211 static void prvPseudoRandomiser( void *pvParameters );
\r
214 * Register commands that can be used with FreeRTOS+CLI. The commands are
\r
215 * defined in CLI-Commands.c and File-Related-CLI-Command.c respectively.
\r
217 extern void vRegisterSampleCLICommands( void );
\r
220 * The task that manages the FreeRTOS+CLI input and output.
\r
222 extern void vUARTCommandConsoleStart( uint16_t usStackSize, UBaseType_t uxPriority );
\r
224 /*-----------------------------------------------------------*/
\r
226 /* The following two variables are used to communicate the status of the
\r
227 register check tasks to the check task. If the variables keep incrementing,
\r
228 then the register check tasks have not discovered any errors. If a variable
\r
229 stops incrementing, then an error has been found. */
\r
230 volatile unsigned long ulRegTest1LoopCounter = 0UL, ulRegTest2LoopCounter = 0UL;
\r
232 /*-----------------------------------------------------------*/
\r
234 void main_full( void )
\r
236 /* Start all the other standard demo/test tasks. They have no particular
\r
237 functionality, but do demonstrate how to use the FreeRTOS API and test the
\r
239 vStartInterruptQueueTasks();
\r
240 vStartDynamicPriorityTasks();
\r
241 vStartBlockingQueueTasks( mainBLOCK_Q_PRIORITY );
\r
242 vCreateBlockTimeTasks();
\r
243 vStartCountingSemaphoreTasks();
\r
244 vStartGenericQueueTasks( tskIDLE_PRIORITY );
\r
245 vStartRecursiveMutexTasks();
\r
246 vStartSemaphoreTasks( mainSEM_TEST_PRIORITY );
\r
247 vStartQueueOverwriteTask( mainQUEUE_OVERWRITE_PRIORITY );
\r
248 vStartEventGroupTasks();
\r
249 vStartTaskNotifyTask();
\r
250 vStartInterruptSemaphoreTasks();
\r
252 /* Create the register check tasks, as described at the top of this file */
\r
253 xTaskCreate( prvRegTest1Task, "RegTst1", configMINIMAL_STACK_SIZE, mainREG_TEST_1_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
254 xTaskCreate( prvRegTest2Task, "RegTst2", configMINIMAL_STACK_SIZE, mainREG_TEST_2_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
256 /* Create the task that just adds a little random behaviour. */
\r
257 xTaskCreate( prvPseudoRandomiser, "Rnd", configMINIMAL_STACK_SIZE, NULL, configMAX_PRIORITIES - 1, NULL );
\r
259 /* Start the tasks that implements the command console on the UART, as
\r
260 described above. */
\r
261 vUARTCommandConsoleStart( mainUART_COMMAND_CONSOLE_STACK_SIZE, mainUART_COMMAND_CONSOLE_TASK_PRIORITY );
\r
263 /* Register the standard CLI commands. */
\r
264 vRegisterSampleCLICommands();
\r
266 /* Create the task that performs the 'check' functionality, as described at
\r
267 the top of this file. */
\r
268 xTaskCreate( prvCheckTask, "Check", configMINIMAL_STACK_SIZE, NULL, mainCHECK_TASK_PRIORITY, NULL );
\r
270 /* The set of tasks created by the following function call have to be
\r
271 created last as they keep account of the number of tasks they expect to see
\r
273 vCreateSuicidalTasks( mainCREATOR_TASK_PRIORITY );
\r
275 /* Start the scheduler. */
\r
276 vTaskStartScheduler();
\r
278 /* If all is well, the scheduler will now be running, and the following
\r
279 line will never be reached. If the following line does execute, then
\r
280 there was insufficient FreeRTOS heap memory available for the Idle and/or
\r
281 timer tasks to be created. See the memory management section on the
\r
282 FreeRTOS web site for more details on the FreeRTOS heap
\r
283 http://www.freertos.org/a00111.html. */
\r
286 /*-----------------------------------------------------------*/
\r
288 static void prvCheckTask( void *pvParameters )
\r
290 TickType_t xDelayPeriod = mainNO_ERROR_CHECK_TASK_PERIOD;
\r
291 TickType_t xLastExecutionTime;
\r
292 static unsigned long ulLastRegTest1Value = 0, ulLastRegTest2Value = 0;
\r
293 unsigned long ulErrorFound = pdFALSE;
\r
295 /* Just to stop compiler warnings. */
\r
296 ( void ) pvParameters;
\r
298 /* Initialise xLastExecutionTime so the first call to vTaskDelayUntil()
\r
299 works correctly. */
\r
300 xLastExecutionTime = xTaskGetTickCount();
\r
302 /* Cycle for ever, delaying then checking all the other tasks are still
\r
303 operating without error. The onboard LED is toggled on each iteration.
\r
304 If an error is detected then the delay period is decreased from
\r
305 mainNO_ERROR_CHECK_TASK_PERIOD to mainERROR_CHECK_TASK_PERIOD. This has the
\r
306 effect of increasing the rate at which the onboard LED toggles, and in so
\r
307 doing gives visual feedback of the system status. */
\r
310 /* Delay until it is time to execute again. */
\r
311 vTaskDelayUntil( &xLastExecutionTime, xDelayPeriod );
\r
313 /* Check all the demo tasks (other than the flash tasks) to ensure
\r
314 that they are all still running, and that none have detected an error. */
\r
315 if( xAreIntQueueTasksStillRunning() != pdTRUE )
\r
317 ulErrorFound |= 1UL << 0UL;
\r
320 if( xAreDynamicPriorityTasksStillRunning() != pdTRUE )
\r
322 ulErrorFound |= 1UL << 2UL;
\r
325 if( xAreBlockingQueuesStillRunning() != pdTRUE )
\r
327 ulErrorFound |= 1UL << 3UL;
\r
330 if ( xAreBlockTimeTestTasksStillRunning() != pdTRUE )
\r
332 ulErrorFound |= 1UL << 4UL;
\r
335 if ( xAreGenericQueueTasksStillRunning() != pdTRUE )
\r
337 ulErrorFound |= 1UL << 5UL;
\r
340 if ( xAreRecursiveMutexTasksStillRunning() != pdTRUE )
\r
342 ulErrorFound |= 1UL << 6UL;
\r
345 if( xIsCreateTaskStillRunning() != pdTRUE )
\r
347 ulErrorFound |= 1UL << 7UL;
\r
350 if( xAreSemaphoreTasksStillRunning() != pdTRUE )
\r
352 ulErrorFound |= 1UL << 8UL;
\r
355 if( xAreCountingSemaphoreTasksStillRunning() != pdTRUE )
\r
357 ulErrorFound |= 1UL << 10UL;
\r
360 if( xIsQueueOverwriteTaskStillRunning() != pdPASS )
\r
362 ulErrorFound |= 1UL << 11UL;
\r
365 if( xAreEventGroupTasksStillRunning() != pdPASS )
\r
367 ulErrorFound |= 1UL << 12UL;
\r
370 if( xAreTaskNotificationTasksStillRunning() != pdTRUE )
\r
372 ulErrorFound |= 1UL << 13UL;
\r
375 if( xAreInterruptSemaphoreTasksStillRunning() != pdTRUE )
\r
377 ulErrorFound |= 1UL << 14UL;
\r
380 /* Check that the register test 1 task is still running. */
\r
381 if( ulLastRegTest1Value == ulRegTest1LoopCounter )
\r
383 ulErrorFound |= 1UL << 15UL;
\r
385 ulLastRegTest1Value = ulRegTest1LoopCounter;
\r
387 /* Check that the register test 2 task is still running. */
\r
388 if( ulLastRegTest2Value == ulRegTest2LoopCounter )
\r
390 ulErrorFound |= 1UL << 16UL;
\r
392 ulLastRegTest2Value = ulRegTest2LoopCounter;
\r
394 /* Toggle the check LED to give an indication of the system status. If
\r
395 the LED toggles every mainNO_ERROR_CHECK_TASK_PERIOD milliseconds then
\r
396 everything is ok. A faster toggle indicates an error. */
\r
399 if( ulErrorFound != pdFALSE )
\r
401 /* An error has been detected in one of the tasks - flash the LED
\r
402 at a higher frequency to give visible feedback that something has
\r
403 gone wrong (it might just be that the loop back connector required
\r
404 by the comtest tasks has not been fitted). */
\r
405 xDelayPeriod = mainERROR_CHECK_TASK_PERIOD;
\r
409 /*-----------------------------------------------------------*/
\r
411 static void prvPseudoRandomiser( void *pvParameters )
\r
413 const uint32_t ulMultiplier = 0x015a4e35UL, ulIncrement = 1UL, ulMinDelay = ( 35 / portTICK_PERIOD_MS );
\r
414 volatile uint32_t ulNextRand = ( uint32_t ) &pvParameters, ulValue;
\r
416 /* This task does nothing other than ensure there is a little bit of
\r
417 disruption in the scheduling pattern of the other tasks. Normally this is
\r
418 done by generating interrupts at pseudo random times. */
\r
421 ulNextRand = ( ulMultiplier * ulNextRand ) + ulIncrement;
\r
422 ulValue = ( ulNextRand >> 16UL ) & 0xffUL;
\r
424 if( ulValue < ulMinDelay )
\r
426 ulValue = ulMinDelay;
\r
429 vTaskDelay( ulValue );
\r
431 while( ulValue > 0 )
\r
446 /*-----------------------------------------------------------*/
\r
448 void vFullDemoTickHook( void )
\r
450 /* Call the periodic queue overwrite from ISR demo. */
\r
451 vQueueOverwritePeriodicISRDemo();
\r
453 /* Call the periodic event group from ISR demo. */
\r
454 vPeriodicEventGroupsProcessing();
\r
456 /* Use task notifications from an interrupt. */
\r
457 xNotifyTaskFromISR();
\r
459 /* Use mutexes from interrupts. */
\r
460 vInterruptSemaphorePeriodicTest();
\r
462 /*-----------------------------------------------------------*/
\r
464 /* This function is explained in the comments at the top of this file. */
\r
465 static void prvRegTest1Task( void *pvParameters )
\r
467 if( pvParameters != mainREG_TEST_1_PARAMETER )
\r
469 /* The parameter did not contain the expected value. */
\r
472 /* Stop the tick interrupt so its obvious something has gone wrong. */
\r
473 taskDISABLE_INTERRUPTS();
\r
477 /* This is an inline asm function that never returns. */
\r
478 prvRegTest1Implementation();
\r
480 /*-----------------------------------------------------------*/
\r
482 /* This function is explained in the comments at the top of this file. */
\r
483 static void prvRegTest2Task( void *pvParameters )
\r
485 if( pvParameters != mainREG_TEST_2_PARAMETER )
\r
487 /* The parameter did not contain the expected value. */
\r
490 /* Stop the tick interrupt so its obvious something has gone wrong. */
\r
491 taskDISABLE_INTERRUPTS();
\r
495 /* This is an inline asm function that never returns. */
\r
496 prvRegTest2Implementation();
\r
498 /*-----------------------------------------------------------*/
\r
500 /* This function is explained in the comments at the top of this file. */
\r
501 #pragma inline_asm prvRegTest1Implementation
\r
502 static void prvRegTest1Implementation( void )
\r
504 ; Put a known value in each register.
\r
521 ; Loop, checking each iteration that each register still contains the
\r
525 ; Push the registers that are going to get clobbered.
\r
528 ; Increment the loop counter to show this task is still getting CPU time.
\r
529 MOV.L #_ulRegTest1LoopCounter, R14
\r
534 ; Yield to extend the text coverage. Set the bit in the ITU SWINTR register.
\r
536 MOV.L #0872E0H, R15
\r
541 ; Restore the clobbered registers.
\r
544 ; Now compare each register to ensure it still contains the value that was
\r
545 ; set before this loop was entered.
\r
577 ; All comparisons passed, start a new itteratio of this loop.
\r
581 ; A compare failed, just loop here so the loop counter stops incrementing
\r
582 ; causing the check task to indicate the error.
\r
585 /*-----------------------------------------------------------*/
\r
587 /* This function is explained in the comments at the top of this file. */
\r
588 #pragma inline_asm prvRegTest2Implementation
\r
589 static void prvRegTest2Implementation( void )
\r
591 ; Put a known value in each register.
\r
608 ; Loop, checking on each iteration that each register still contains the
\r
612 ; Push the registers that are going to get clobbered.
\r
615 ; Increment the loop counter to show this task is still getting CPU time.
\r
616 MOV.L #_ulRegTest2LoopCounter, R14
\r
621 ; Restore the clobbered registers.
\r
655 ; All comparisons passed, start a new itteratio of this loop.
\r
659 ; A compare failed, just loop here so the loop counter stops incrementing
\r
660 ; - causing the check task to indicate the error.
\r
663 /*-----------------------------------------------------------*/
\r