2 FreeRTOS V8.1.2 - 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 !<<
\r
28 >>! distribute a combined work that includes FreeRTOS without being !<<
\r
29 >>! obliged to provide the source code for proprietary components !<<
\r
30 >>! outside of the FreeRTOS kernel. !<<
\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 includes a lot of tasks and tests and is therefore complex.
\r
68 * If you would prefer a much simpler project to get started with then select
\r
69 * the 'Blinky' build configuration within the HEW IDE. The Blinky build
\r
70 * configuration uses main-blinky.c instead of main-full.c.
\r
71 * ****************************************************************************
\r
73 * Creates all the demo application tasks, then starts the scheduler. The web
\r
74 * documentation provides more details of the standard demo application tasks,
\r
75 * which provide no particular functionality but do provide a good example of
\r
76 * how to use the FreeRTOS API.
\r
78 * In addition to the standard demo tasks, the following tasks and tests are
\r
79 * defined and/or created within this file:
\r
81 * "Reg test" tasks - These fill the registers with known values, then
\r
82 * repeatedly check that each register still contains its expected value for
\r
83 * the lifetime of the tasks. Each task uses different values. The tasks run
\r
84 * with very low priority so get preempted very frequently. A check variable
\r
85 * is incremented on each iteration of the test loop. A register containing an
\r
86 * unexpected value is indicative of an error in the context switching
\r
87 * mechanism and will result in a branch to a null loop - which in turn will
\r
88 * prevent the check variable from incrementing any further and allow the check
\r
89 * timer (described below) to determine that an error has occurred. The nature
\r
90 * of the reg test tasks necessitates that they are written in assembly code.
\r
92 * "Check Timer" and Callback Function - The check timer period is initially
\r
93 * set to five seconds. The check timer callback function checks that all the
\r
94 * standard demo tasks are not only still executing, but are executing without
\r
95 * reporting any errors. If the check timer discovers that a task has either
\r
96 * stalled, or reported an error, then it changes its own period from the
\r
97 * initial five seconds, to just 200ms. The check timer callback function
\r
98 * also toggles LED 3 each time it is called. This provides a visual
\r
99 * indication of the system status: If the LED toggles every five seconds,
\r
100 * then no issues have been discovered. If the LED toggles every 200ms, then
\r
101 * an issue has been discovered with at least one task.
\r
103 * "High frequency timer test" - A high frequency periodic interrupt is
\r
104 * generated using a timer - the interrupt is assigned a priority above
\r
105 * configMAX_SYSCALL_INTERRUPT_PRIORITY, so will not be effected by anything
\r
106 * the kernel is doing. The frequency and priority of the interrupt, in
\r
107 * combination with other standard tests executed in this demo, will result
\r
108 * in interrupts nesting at least 3 and probably 4 deep. This test is only
\r
109 * included in build configurations that have the optimiser switched on.
\r
111 * "Button and LCD test" - This creates two tasks. The first simply scrolls
\r
112 * a message back and forth along the top line of the LCD display. If no
\r
113 * buttons are pushed, the second also scrolls a message back and forth, but
\r
114 * along the bottom line of the display. The automatic scrolling of the second
\r
115 * line of the display can be started and stopped using button SW2. Once
\r
116 * stopped it can then be manually nudged left using button SW3, and manually
\r
117 * nudged right using button SW1. Button pushes generate an interrupt, and the
\r
118 * interrupt communicates with the task using a queue.
\r
120 * *NOTE 1* vApplicationSetupTimerInterrupt() is called by the kernel to let
\r
121 * the application set up a timer to generate the tick interrupt. In this
\r
122 * example a compare match timer is used for this purpose.
\r
124 * *NOTE 2* The CPU must be in Supervisor mode when the scheduler is started.
\r
125 * The PowerON_Reset_PC() supplied in resetprg.c with this demo has
\r
126 * Change_PSW_PM_to_UserMode() commented out to ensure this is the case.
\r
128 * *NOTE 3* The IntQueue common demo tasks test interrupt nesting and make use
\r
129 * of all the 8bit timers (as two cascaded 16bit units).
\r
132 /* Standard includes. */
\r
133 #include <string.h>
\r
135 /* Hardware specific includes. */
\r
136 #include "iodefine.h"
\r
138 /* Kernel includes. */
\r
139 #include "FreeRTOS.h"
\r
141 #include "timers.h"
\r
142 #include "semphr.h"
\r
144 /* Standard demo includes. */
\r
145 #include "partest.h"
\r
147 #include "IntQueue.h"
\r
148 #include "BlockQ.h"
\r
150 #include "integer.h"
\r
151 #include "blocktim.h"
\r
152 #include "semtest.h"
\r
154 #include "GenQTest.h"
\r
156 #include "recmutex.h"
\r
158 /* Demo specific tasks. */
\r
159 #include "ButtonAndLCD.h"
\r
161 /* Peripheral includes. */
\r
164 /* Values that are passed into the reg test tasks using the task parameter.
\r
165 The tasks check that the values are passed in correctly. */
\r
166 #define mainREG_TEST_1_PARAMETER ( 0x12121212UL )
\r
167 #define mainREG_TEST_2_PARAMETER ( 0x12345678UL )
\r
169 /* Priorities at which the tasks are created. */
\r
170 #define mainQUEUE_POLL_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
171 #define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
172 #define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
173 #define mainCREATOR_TASK_PRIORITY ( tskIDLE_PRIORITY + 3 )
\r
174 #define mainFLASH_TASK_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
175 #define mainINTEGER_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
176 #define mainGEN_QUEUE_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
177 #define mainFLOP_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
179 /* The LED toggled by the check timer. */
\r
180 #define mainCHECK_LED ( 3 )
\r
182 /* The period at which the check timer will expire, in ms, provided no errors
\r
183 have been reported by any of the standard demo tasks. ms are converted to the
\r
184 equivalent in ticks using the portTICK_PERIOD_MS constant. */
\r
185 #define mainCHECK_TIMER_PERIOD_MS ( 5000UL / portTICK_PERIOD_MS )
\r
187 /* The period at which the check timer will expire, in ms, if an error has been
\r
188 reported in one of the standard demo tasks. ms are converted to the equivalent
\r
189 in ticks using the portTICK_PERIOD_MS constant. */
\r
190 #define mainERROR_CHECK_TIMER_PERIOD_MS ( 200UL / portTICK_PERIOD_MS )
\r
192 /* A block time of zero simple means "Don't Block". */
\r
193 #define mainDONT_BLOCK ( 0UL )
\r
196 * vApplicationMallocFailedHook() will only be called if
\r
197 * configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
198 * function that will execute if a call to pvPortMalloc() fails.
\r
199 * pvPortMalloc() is called internally by the kernel whenever a task, queue or
\r
200 * semaphore is created. It is also called by various parts of the demo
\r
203 void vApplicationMallocFailedHook( void );
\r
206 * vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set to 1
\r
207 * in FreeRTOSConfig.h. It is a hook function that is called on each iteration
\r
208 * of the idle task. It is essential that code added to this hook function
\r
209 * never attempts to block in any way (for example, call xQueueReceive() with
\r
210 * a block time specified). If the application makes use of the vTaskDelete()
\r
211 * API function (as this demo application does) then it is also important that
\r
212 * vApplicationIdleHook() is permitted to return to its calling function because
\r
213 * it is the responsibility of the idle task to clean up memory allocated by the
\r
214 * kernel to any task that has since been deleted.
\r
216 void vApplicationIdleHook( void );
\r
219 * vApplicationStackOverflowHook() will only be called if
\r
220 * configCHECK_FOR_STACK_OVERFLOW is set to a non-zero value. The handle and
\r
221 * name of the offending task should be passed in the function parameters, but
\r
222 * it is possible that the stack overflow will have corrupted these - in which
\r
223 * case pxCurrentTCB can be inspected to find the same information.
\r
225 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName );
\r
228 * The reg test tasks as described at the top of this file.
\r
230 static void prvRegTest1Task( void *pvParameters );
\r
231 static void prvRegTest2Task( void *pvParameters );
\r
234 * The actual implementation of the reg test functionality, which, because of
\r
235 * the direct register access, have to be in assembly.
\r
237 static void prvRegTest1Implementation( void );
\r
238 static void prvRegTest2Implementation( void );
\r
241 * The check timer callback function, as described at the top of this file.
\r
243 static void prvCheckTimerCallback( TimerHandle_t xTimer );
\r
246 /*-----------------------------------------------------------*/
\r
248 /* Variables that are incremented on each iteration of the reg test tasks -
\r
249 provided the tasks have not reported any errors. The check timer inspects these
\r
250 variables to ensure they are still incrementing as expected. If a variable
\r
251 stops incrementing then it is likely that its associate task has stalled. */
\r
252 unsigned long ulRegTest1CycleCount = 0UL, ulRegTest2CycleCount = 0UL;
\r
254 /* The check timer. This uses prvCheckTimerCallback() as its callback
\r
256 static TimerHandle_t xCheckTimer = NULL;
\r
258 /*-----------------------------------------------------------*/
\r
262 extern void HardwareSetup( void );
\r
264 /* Renesas provided CPU configuration routine. The clocks are configured in
\r
268 /* Turn all LEDs off. */
\r
269 vParTestInitialise();
\r
271 /* Start the reg test tasks which test the context switching mechanism. */
\r
272 xTaskCreate( prvRegTest1Task, "RegTst1", configMINIMAL_STACK_SIZE, ( void * ) mainREG_TEST_1_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
273 xTaskCreate( prvRegTest2Task, "RegTst2", configMINIMAL_STACK_SIZE, ( void * ) mainREG_TEST_2_PARAMETER, tskIDLE_PRIORITY, NULL );
\r
275 /* The button and LCD tasks, as described at the top of this file. */
\r
276 vStartButtonAndLCDDemo();
\r
278 /* Create the standard demo tasks. */
\r
279 vStartBlockingQueueTasks( mainBLOCK_Q_PRIORITY );
\r
280 vCreateBlockTimeTasks();
\r
281 vStartSemaphoreTasks( mainSEM_TEST_PRIORITY );
\r
282 vStartPolledQueueTasks( mainQUEUE_POLL_PRIORITY );
\r
283 vStartIntegerMathTasks( mainINTEGER_TASK_PRIORITY );
\r
284 vStartGenericQueueTasks( mainGEN_QUEUE_TASK_PRIORITY );
\r
285 vStartLEDFlashTasks( mainFLASH_TASK_PRIORITY );
\r
286 vStartQueuePeekTasks();
\r
287 vStartRecursiveMutexTasks();
\r
288 vStartInterruptQueueTasks();
\r
290 /* The suicide tasks must be created last as they need to know how many
\r
291 tasks were running prior to their creation in order to ascertain whether
\r
292 or not the correct/expected number of tasks are running at any given time. */
\r
293 vCreateSuicidalTasks( mainCREATOR_TASK_PRIORITY );
\r
295 /* Create the software timer that performs the 'check' functionality,
\r
296 as described at the top of this file. */
\r
297 xCheckTimer = xTimerCreate( "CheckTimer",/* A text name, purely to help debugging. */
\r
298 ( mainCHECK_TIMER_PERIOD_MS ), /* The timer period, in this case 5000ms (5s). */
\r
299 pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */
\r
300 ( void * ) 0, /* The ID is not used, so can be set to anything. */
\r
301 prvCheckTimerCallback /* The callback function that inspects the status of all the other tasks. */
\r
304 configASSERT( xCheckTimer );
\r
306 /* Start the check timer. It will actually start when the scheduler is
\r
308 xTimerStart( xCheckTimer, mainDONT_BLOCK );
\r
310 /* Start the tasks running. */
\r
311 vTaskStartScheduler();
\r
313 /* If all is well we will never reach here as the scheduler will now be
\r
314 running. If we do reach here then it is likely that there was insufficient
\r
315 heap available for the idle task to be created. */
\r
318 /*-----------------------------------------------------------*/
\r
320 static void prvCheckTimerCallback( TimerHandle_t xTimer )
\r
322 static long lChangedTimerPeriodAlready = pdFALSE, lErrorStatus = pdPASS;
\r
323 static volatile unsigned long ulLastRegTest1CycleCount = 0UL, ulLastRegTest2CycleCount = 0UL;
\r
325 /* Check the standard demo tasks are running without error. */
\r
326 if( xAreGenericQueueTasksStillRunning() != pdTRUE )
\r
328 lErrorStatus = pdFAIL;
\r
330 else if( xAreQueuePeekTasksStillRunning() != pdTRUE )
\r
332 lErrorStatus = pdFAIL;
\r
334 else if( xAreBlockingQueuesStillRunning() != pdTRUE )
\r
336 lErrorStatus = pdFAIL;
\r
338 else if( xAreBlockTimeTestTasksStillRunning() != pdTRUE )
\r
340 lErrorStatus = pdFAIL;
\r
342 else if( xAreSemaphoreTasksStillRunning() != pdTRUE )
\r
344 lErrorStatus = pdFAIL;
\r
346 else if( xArePollingQueuesStillRunning() != pdTRUE )
\r
348 lErrorStatus = pdFAIL;
\r
350 else if( xIsCreateTaskStillRunning() != pdTRUE )
\r
352 lErrorStatus = pdFAIL;
\r
354 else if( xAreIntegerMathsTaskStillRunning() != pdTRUE )
\r
356 lErrorStatus = pdFAIL;
\r
358 else if( xAreRecursiveMutexTasksStillRunning() != pdTRUE )
\r
360 lErrorStatus = pdFAIL;
\r
362 else if( xAreIntQueueTasksStillRunning() != pdPASS )
\r
364 lErrorStatus = pdFAIL;
\r
367 /* Check the reg test tasks are still cycling. They will stop incrementing
\r
368 their loop counters if they encounter an error. */
\r
369 if( ulRegTest1CycleCount == ulLastRegTest1CycleCount )
\r
371 lErrorStatus = pdFAIL;
\r
374 if( ulRegTest2CycleCount == ulLastRegTest2CycleCount )
\r
376 lErrorStatus = pdFAIL;
\r
379 ulLastRegTest1CycleCount = ulRegTest1CycleCount;
\r
380 ulLastRegTest2CycleCount = ulRegTest2CycleCount;
\r
382 /* Toggle the check LED to give an indication of the system status. If
\r
383 the LED toggles every 5 seconds then everything is ok. A faster toggle
\r
384 indicates an error. */
\r
385 vParTestToggleLED( mainCHECK_LED );
\r
387 /* Was an error detected this time through the callback execution? */
\r
388 if( lErrorStatus != pdPASS )
\r
390 if( lChangedTimerPeriodAlready == pdFALSE )
\r
392 lChangedTimerPeriodAlready = pdTRUE;
\r
394 /* This call to xTimerChangePeriod() uses a zero block time.
\r
395 Functions called from inside of a timer callback function must
\r
396 *never* attempt to block. */
\r
397 xTimerChangePeriod( xCheckTimer, ( mainERROR_CHECK_TIMER_PERIOD_MS ), mainDONT_BLOCK );
\r
401 /*-----------------------------------------------------------*/
\r
403 /* The RX port uses this callback function to configure its tick interrupt.
\r
404 This allows the application to choose the tick interrupt source. */
\r
405 void vApplicationSetupTimerInterrupt( void )
\r
407 /* Enable compare match timer 0. */
\r
410 /* Interrupt on compare match. */
\r
411 CMT0.CMCR.BIT.CMIE = 1;
\r
413 /* Set the compare match value. */
\r
414 CMT0.CMCOR = ( unsigned short ) ( ( ( configPERIPHERAL_CLOCK_HZ / configTICK_RATE_HZ ) -1 ) / 8 );
\r
416 /* Divide the PCLK by 8. */
\r
417 CMT0.CMCR.BIT.CKS = 0;
\r
419 /* Enable the interrupt... */
\r
420 _IEN( _CMT0_CMI0 ) = 1;
\r
422 /* ...and set its priority to the application defined kernel priority. */
\r
423 _IPR( _CMT0_CMI0 ) = configKERNEL_INTERRUPT_PRIORITY;
\r
425 /* Start the timer. */
\r
426 CMT.CMSTR0.BIT.STR0 = 1;
\r
428 /*-----------------------------------------------------------*/
\r
430 /* This function is explained by the comments above its prototype at the top
\r
432 void vApplicationMallocFailedHook( void )
\r
436 /*-----------------------------------------------------------*/
\r
438 /* This function is explained by the comments above its prototype at the top
\r
440 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
444 /*-----------------------------------------------------------*/
\r
446 /* This function is explained by the comments above its prototype at the top
\r
448 void vApplicationIdleHook( void )
\r
450 /* If this is being executed then the kernel has been started. Start the high
\r
451 frequency timer test as described at the top of this file. This is only
\r
452 included in the optimised build configuration - otherwise it takes up too much
\r
453 CPU time and can disrupt other tests. */
\r
454 #ifdef INCLUDE_HIGH_FREQUENCY_TIMER_TEST
\r
455 static portBASE_TYPE xTimerTestStarted = pdFALSE;
\r
456 extern void vSetupHighFrequencyTimer( void );
\r
457 if( xTimerTestStarted == pdFALSE )
\r
459 vSetupHighFrequencyTimer();
\r
460 xTimerTestStarted = pdTRUE;
\r
464 /*-----------------------------------------------------------*/
\r
466 /* This function is explained in the comments at the top of this file. */
\r
467 static void prvRegTest1Task( void *pvParameters )
\r
469 if( ( ( unsigned long ) pvParameters ) != mainREG_TEST_1_PARAMETER )
\r
471 /* The parameter did not contain the expected value. */
\r
474 /* Stop the tick interrupt so its obvious something has gone wrong. */
\r
475 taskDISABLE_INTERRUPTS();
\r
479 /* This is an inline asm function that never returns. */
\r
480 prvRegTest1Implementation();
\r
482 /*-----------------------------------------------------------*/
\r
484 /* This function is explained in the comments at the top of this file. */
\r
485 static void prvRegTest2Task( void *pvParameters )
\r
487 if( ( ( unsigned long ) pvParameters ) != mainREG_TEST_2_PARAMETER )
\r
489 /* The parameter did not contain the expected value. */
\r
492 /* Stop the tick interrupt so its obvious something has gone wrong. */
\r
493 taskDISABLE_INTERRUPTS();
\r
497 /* This is an inline asm function that never returns. */
\r
498 prvRegTest2Implementation();
\r
500 /*-----------------------------------------------------------*/
\r
502 /* This function is explained in the comments at the top of this file. */
\r
503 #pragma inline_asm prvRegTest1Implementation
\r
504 static void prvRegTest1Implementation( void )
\r
506 ; Put a known value in each register.
\r
523 ; Loop, checking each itteration that each register still contains the
\r
527 ; Push the registers that are going to get clobbered.
\r
530 ; Increment the loop counter to show this task is still getting CPU time.
\r
531 MOV.L #_ulRegTest1CycleCount, R14
\r
536 ; Yield to extend the text coverage. Set the bit in the ITU SWINTR register.
\r
538 MOV.L #0872E0H, R15
\r
543 ; Restore the clobbered registers.
\r
546 ; Now compare each register to ensure it still contains the value that was
\r
547 ; set before this loop was entered.
\r
579 ; All comparisons passed, start a new itteratio of this loop.
\r
583 ; A compare failed, just loop here so the loop counter stops incrementing
\r
584 ; causing the check timer to indicate the error.
\r
587 /*-----------------------------------------------------------*/
\r
589 /* This function is explained in the comments at the top of this file. */
\r
590 #pragma inline_asm prvRegTest2Implementation
\r
591 static void prvRegTest2Implementation( void )
\r
593 ; Put a known value in each register.
\r
610 ; Loop, checking on each itteration that each register still contains the
\r
614 ; Push the registers that are going to get clobbered.
\r
617 ; Increment the loop counter to show this task is still getting CPU time.
\r
618 MOV.L #_ulRegTest2CycleCount, R14
\r
623 ; Restore the clobbered registers.
\r
657 ; All comparisons passed, start a new itteratio of this loop.
\r
661 ; A compare failed, just loop here so the loop counter stops incrementing
\r
662 ; - causing the check timer to indicate the error.
\r
665 /*-----------------------------------------------------------*/
\r