2 FreeRTOS V7.0.1 - Copyright (C) 2011 Real Time Engineers Ltd.
\r
5 FreeRTOS supports many tools and architectures. V7.0.0 is sponsored by:
\r
6 Atollic AB - Atollic provides professional embedded systems development
\r
7 tools for C/C++ development, code analysis and test automation.
\r
8 See http://www.atollic.com
\r
11 ***************************************************************************
\r
13 * FreeRTOS tutorial books are available in pdf and paperback. *
\r
14 * Complete, revised, and edited pdf reference manuals are also *
\r
17 * Purchasing FreeRTOS documentation will not only help you, by *
\r
18 * ensuring you get running as quickly as possible and with an *
\r
19 * in-depth knowledge of how to use FreeRTOS, it will also help *
\r
20 * the FreeRTOS project to continue with its mission of providing *
\r
21 * professional grade, cross platform, de facto standard solutions *
\r
22 * for microcontrollers - completely free of charge! *
\r
24 * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *
\r
26 * Thank you for using FreeRTOS, and thank you for your support! *
\r
28 ***************************************************************************
\r
31 This file is part of the FreeRTOS distribution.
\r
33 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
34 the terms of the GNU General Public License (version 2) as published by the
\r
35 Free Software Foundation AND MODIFIED BY the FreeRTOS exception.
\r
36 >>>NOTE<<< The modification to the GPL is included to allow you to
\r
37 distribute a combined work that includes FreeRTOS without being obliged to
\r
38 provide the source code for proprietary components outside of the FreeRTOS
\r
39 kernel. FreeRTOS is distributed in the hope that it will be useful, but
\r
40 WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
\r
41 or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
\r
42 more details. You should have received a copy of the GNU General Public
\r
43 License and the FreeRTOS license exception along with FreeRTOS; if not it
\r
44 can be viewed here: http://www.freertos.org/a00114.html and also obtained
\r
45 by writing to Richard Barry, contact details for whom are available on the
\r
50 http://www.FreeRTOS.org - Documentation, latest information, license and
\r
53 http://www.SafeRTOS.com - A version that is certified for use in safety
\r
56 http://www.OpenRTOS.com - Commercial support, development, porting,
\r
57 licensing and training services.
\r
61 * main-blinky.c is included when the "Blinky" build configuration is used.
\r
62 * main-full.c is included when the "Full" build configuration is used.
\r
64 * main-full.c (this file) defines a comprehensive demo that creates many
\r
65 * tasks, queues, semaphores and timers. It also demonstrates how Cortex-M3
\r
66 * interrupts can interact with FreeRTOS tasks/timers, a simple web server, and
\r
67 * run time statistics gathering functionality. ***IF YOU ARE LOOKING FOR A
\r
68 * SIMPLER STARTING POINT THEN USE THE "BLINKY" BUILD CONFIGURATION FIRST.***
\r
70 * If the Ethernet functionality is excluded, then this demo will run 'stand
\r
71 * alone' (without the rest of the tower system) on the TWR-K60N512 tower
\r
72 * module. If the Ethernet functionality is included, then the full Freescale
\r
73 * K60 tower kit, including both the TWR-K60N512 and TWR-SER modules, is
\r
74 * required (as the Ethernet connector is on the TWR-SER). The TWR-K60N512 is
\r
75 * populated with a K60N512 Cortex-M4 microcontroller.
\r
77 * The main() Function:
\r
78 * main() creates four demo specific software timers, and one demo specific
\r
79 * task (the web server task). It also creates a whole host of 'standard
\r
80 * demo' tasks/queues/semaphores/timers, before starting the scheduler. The
\r
81 * demo specific tasks and timers are described in the comments here. The
\r
82 * standard demo tasks are described on the FreeRTOS.org web site.
\r
84 * The standard demo tasks provide no specific functionality. They are
\r
85 * included to both test the FreeRTOS port, and provide examples of how the
\r
86 * various FreeRTOS API functions can be used.
\r
88 * This demo creates 37 persistent tasks, then dynamically creates and destroys
\r
89 * another two tasks as the demo executes.
\r
92 * The Demo Specific "LED" Timers and Callback Function:
\r
93 * Two very simple LED timers are created. All they do is toggle an LED each
\r
94 * when the timer callback function is executed. The two timers share a
\r
95 * callback function, so the callback function parameter is used to determine
\r
96 * which timer actually expired, and therefore, which LED to toggle. Both
\r
97 * timers use a different frequency, one toggles the blue LED and the other the
\r
100 * The LED/Button Software Timer and the Button Interrupt:
\r
101 * The user button SW2 is configured to generate an interrupt each time it is
\r
102 * pressed. The interrupt service routine switches the orange/yellow LED on,
\r
103 * and resets the LED software timer. The LED timer has a 5000 millisecond (5
\r
104 * second) period, and uses a callback function that is defined to just turn the
\r
105 * LED off again. Therefore, pressing the user button will turn the LED on, and
\r
106 * the LED will remain on until a full five seconds pass without the button
\r
109 * The Demo Specific "Check" Timer and Callback Function:
\r
110 * The check timer period is initially set to three seconds. The check timer
\r
111 * callback function checks that all the standard demo tasks are not only still
\r
112 * executing, but are executing without reporting any errors. If the check
\r
113 * timer discovers that a task has either stalled, or reported an error, then it
\r
114 * changes its own period from the initial three seconds, to just 200ms. The
\r
115 * check timer callback function also toggles the orange/red LED each time it is
\r
116 * called. This provides a visual indication of the system status: If the LED
\r
117 * toggles every three seconds, then no issues have been discovered. If the LED
\r
118 * toggles every 200ms, then an issue has been discovered with at least one
\r
119 * task. The last reported issue is latched into the pcStatusMessage variable,
\r
120 * and displayed at the bottom of the "task stats" web page served by the
\r
121 * embedded web server task.
\r
123 * The web server task:
\r
124 * The web server task implements a simple embedded web server that includes
\r
125 * CGI scripting. Pages are provided that allow task statistics, network
\r
126 * statistics and run time statistics to be viewed. In addition, an IO page is
\r
127 * served that allows the orange/yellow LED to be turned on and off. Finally,
\r
128 * a page is included that serves a large jpg file. See the documentation page
\r
129 * for this demo on the http://www.FreeRTOS.org web site for web server
\r
130 * configuration and usage instructions.
\r
132 * The Demo Specific Idle Hook Function:
\r
133 * The idle hook function demonstrates how to query the amount of FreeRTOS heap
\r
134 * space that is remaining (see vApplicationIdleHook() defined in this file).
\r
136 * The Demo Specific Tick Hook Function:
\r
137 * The tick hook function is used to test the interrupt safe software timer
\r
142 /* Kernel includes. */
\r
143 #include "FreeRTOS.h"
\r
146 #include "timers.h"
\r
148 /* Freescale includes. */
\r
149 #include "common.h"
\r
151 /* Common demo includes. */
\r
152 #include "partest.h"
\r
154 #include "BlockQ.h"
\r
156 #include "blocktim.h"
\r
157 #include "semtest.h"
\r
158 #include "GenQTest.h"
\r
160 #include "recmutex.h"
\r
161 #include "TimerDemo.h"
\r
163 #include "countsem.h"
\r
164 #include "dynamic.h"
\r
166 /* The LED toggled by the check timer callback function. */
\r
167 #define mainCHECK_LED 3UL
\r
169 /* The LED turned on by the button interrupt, and turned off by the LED timer. */
\r
170 #define mainTIMER_CONTROLLED_LED 2UL
\r
172 /* The LEDs toggled by the two simple flash LED timers. */
\r
173 #define mainLED0 0UL
\r
174 #define mainLED1 1UL
\r
176 /* Constant used by the standard timer test functions. */
\r
177 #define mainTIMER_TEST_PERIOD ( 50 )
\r
179 /* Priorities used by the various different standard demo tasks. */
\r
180 #define mainQUEUE_POLL_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
181 #define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
182 #define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
183 #define mainCREATOR_TASK_PRIORITY ( tskIDLE_PRIORITY + 3 )
\r
184 #define mainGEN_QUEUE_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
185 #define mainuIP_TASK_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
187 /* The WEB server uses string handling functions, which in turn use a bit more
\r
188 stack than most of the other tasks. */
\r
189 #define mainuIP_STACK_SIZE ( configMINIMAL_STACK_SIZE * 3 )
\r
191 /* The period at which the check timer will expire, in ms, provided no errors
\r
192 have been reported by any of the standard demo tasks. ms are converted to the
\r
193 equivalent in ticks using the portTICK_RATE_MS constant. */
\r
194 #define mainCHECK_TIMER_PERIOD_MS ( 3000UL / portTICK_RATE_MS )
\r
196 /* The period at which the check timer will expire, in ms, if an error has been
\r
197 reported in one of the standard demo tasks. ms are converted to the equivalent
\r
198 in ticks using the portTICK_RATE_MS constant. */
\r
199 #define mainERROR_CHECK_TIMER_PERIOD_MS ( 200UL / portTICK_RATE_MS )
\r
201 /* The LED that is turned on by pressing SW2 remains on until the button has not
\r
202 been pushed for a full 5000ms. */
\r
203 #define mainBUTTON_LED_TIMER_PERIOD_MS ( 5000UL / portTICK_RATE_MS )
\r
205 /* The period at which the two simple LED flash timers will execute their
\r
206 callback functions. */
\r
207 #define mainLED1_TIMER_PERIOD_MS ( 200UL / portTICK_RATE_MS )
\r
208 #define mainLED2_TIMER_PERIOD_MS ( 600UL / portTICK_RATE_MS )
\r
210 /* A block time of zero simply means "don't block". */
\r
211 #define mainDONT_BLOCK ( 0UL )
\r
213 /* The vector used by the GPIO port E. Button SW2 is configured to generate
\r
214 an interrupt on this port. */
\r
215 #define mainGPIO_E_VECTOR ( 91 )
\r
217 /*-----------------------------------------------------------*/
\r
220 * Setup the NVIC, LED outputs, and button inputs.
\r
222 static void prvSetupHardware( void );
\r
225 * Creates the timers that are specific to this demo - namely, the check timer
\r
226 * the button LED timer, and the two simple LED flash timers.
\r
228 static void prvCreateDemoSpecificTimers( void );
\r
231 * The LED/button timer callback function. This does nothing but switch an LED
\r
234 static void prvButtonLEDTimerCallback( xTimerHandle xTimer );
\r
237 * The callback function used by both simple LED flash timers. Both timers use
\r
238 * the same callback, so the function parameter is used to determine which LED
\r
239 * should be flashed (effectively to determine which timer has expired).
\r
241 static void prvLEDTimerCallback( xTimerHandle xTimer );
\r
244 * The check timer callback function, as described at the top of this file.
\r
246 static void prvCheckTimerCallback( xTimerHandle xTimer );
\r
249 * Contains the implementation of the web server.
\r
251 extern void vuIP_Task( void *pvParameters );
\r
253 /*-----------------------------------------------------------*/
\r
255 /* The LED/Button software timer. This uses prvButtonLEDTimerCallback() as it's
\r
256 callback function. */
\r
257 static xTimerHandle xLEDButtonTimer = NULL;
\r
259 /* The check timer. This uses prvCheckTimerCallback() as its callback
\r
261 static xTimerHandle xCheckTimer = NULL;
\r
263 /* LED timers - these simply flash LEDs, each using a different frequency. Both
\r
264 use the same prvLEDTimerCallback() callback function. */
\r
265 static xTimerHandle xLED1Timer = NULL, xLED2Timer = NULL;
\r
267 /* If an error is detected in a standard demo task, then pcStatusMessage will
\r
268 be set to point to a string that identifies the offending task. This is just
\r
269 to make debugging easier. */
\r
270 static const char *pcStatusMessage = NULL;
\r
272 /* Used in the run time stats calculations. */
\r
273 static unsigned long ulClocksPer10thOfAMilliSecond = 0UL;
\r
275 /*-----------------------------------------------------------*/
\r
279 /* Configure the NVIC, LED outputs and button inputs. */
\r
280 prvSetupHardware();
\r
282 /* Create the timers that are specific to this demo - other timers are
\r
283 created as part of the standard demo within vStartTimerDemoTask. */
\r
284 prvCreateDemoSpecificTimers();
\r
286 /* Create a lot of 'standard demo' tasks. Nearly 40 tasks are created in
\r
287 this demo. For a much simpler demo, select the 'blinky' build
\r
289 vStartBlockingQueueTasks( mainBLOCK_Q_PRIORITY );
\r
290 vCreateBlockTimeTasks();
\r
291 vStartSemaphoreTasks( mainSEM_TEST_PRIORITY );
\r
292 vStartGenericQueueTasks( mainGEN_QUEUE_TASK_PRIORITY );
\r
293 vStartQueuePeekTasks();
\r
294 vStartRecursiveMutexTasks();
\r
295 vStartTimerDemoTask( mainTIMER_TEST_PERIOD );
\r
296 vStartPolledQueueTasks( mainQUEUE_POLL_PRIORITY );
\r
297 vStartCountingSemaphoreTasks();
\r
298 vStartDynamicPriorityTasks();
\r
300 /* The web server task. */
\r
301 xTaskCreate( vuIP_Task, "uIP", mainuIP_STACK_SIZE, NULL, mainuIP_TASK_PRIORITY, NULL );
\r
303 /* The suicide tasks must be created last, as they need to know how many
\r
304 tasks were running prior to their creation in order to ascertain whether
\r
305 or not the correct/expected number of tasks are running at any given
\r
307 vCreateSuicidalTasks( mainCREATOR_TASK_PRIORITY );
\r
309 /* Start the tasks and timers running. */
\r
310 vTaskStartScheduler();
\r
312 /* If all is well, the scheduler will now be running, and the following line
\r
313 will never be reached. If the following line does execute, then there was
\r
314 insufficient FreeRTOS heap memory available for the idle and/or timer tasks
\r
315 to be created. See the memory management section on the FreeRTOS web site
\r
316 for more details. */
\r
319 /*-----------------------------------------------------------*/
\r
321 static void prvCheckTimerCallback( xTimerHandle xTimer )
\r
323 static long lChangedTimerPeriodAlready = pdFALSE;
\r
325 /* Check the standard demo tasks are running without error. Latch the
\r
326 latest reported error in the pcStatusMessage character pointer. The latched
\r
327 string can be viewed using the embedded web server - it is displayed at
\r
328 the bottom of the served "task stats" page. */
\r
329 if( xAreGenericQueueTasksStillRunning() != pdTRUE )
\r
331 pcStatusMessage = "Error: GenQueue";
\r
334 if( xAreQueuePeekTasksStillRunning() != pdTRUE )
\r
336 pcStatusMessage = "Error: QueuePeek\n";
\r
339 if( xAreBlockingQueuesStillRunning() != pdTRUE )
\r
341 pcStatusMessage = "Error: BlockQueue\n";
\r
344 if( xAreBlockTimeTestTasksStillRunning() != pdTRUE )
\r
346 pcStatusMessage = "Error: BlockTime\n";
\r
349 if( xAreSemaphoreTasksStillRunning() != pdTRUE )
\r
351 pcStatusMessage = "Error: SemTest\n";
\r
354 if( xIsCreateTaskStillRunning() != pdTRUE )
\r
356 pcStatusMessage = "Error: Death\n";
\r
359 if( xAreRecursiveMutexTasksStillRunning() != pdTRUE )
\r
361 pcStatusMessage = "Error: RecMutex\n";
\r
364 if( xAreTimerDemoTasksStillRunning( ( mainCHECK_TIMER_PERIOD_MS ) ) != pdTRUE )
\r
366 pcStatusMessage = "Error: TimerDemo\n";
\r
369 if( xArePollingQueuesStillRunning() != pdTRUE )
\r
371 pcStatusMessage = "Error: PollQueue\n";
\r
374 if( xAreCountingSemaphoreTasksStillRunning() != pdTRUE )
\r
376 pcStatusMessage = "Error: CountSem\n";
\r
379 if( xAreDynamicPriorityTasksStillRunning() != pdTRUE )
\r
381 pcStatusMessage = "Error: DynamicPriority\n";
\r
384 /* Toggle the check LED to give an indication of the system status. If
\r
385 the LED toggles every mainCHECK_TIMER_PERIOD_MS milliseconds then
\r
386 everything is ok. A faster toggle indicates an error. */
\r
387 vParTestToggleLED( mainCHECK_LED );
\r
389 /* Have any errors been latch in pcStatusMessage? If so, shorten the
\r
390 period of the check timer to mainERROR_CHECK_TIMER_PERIOD_MS milliseconds.
\r
391 This will result in an increase in the rate at which mainCHECK_LED
\r
393 if( pcStatusMessage != NULL )
\r
395 if( lChangedTimerPeriodAlready == pdFALSE )
\r
397 lChangedTimerPeriodAlready = pdTRUE;
\r
398 printf( "%s", pcStatusMessage );
\r
400 /* This call to xTimerChangePeriod() uses a zero block time.
\r
401 Functions called from inside of a timer callback function must
\r
402 *never* attempt to block. */
\r
403 xTimerChangePeriod( xCheckTimer, ( mainERROR_CHECK_TIMER_PERIOD_MS ), mainDONT_BLOCK );
\r
407 /*-----------------------------------------------------------*/
\r
409 static void prvButtonLEDTimerCallback( xTimerHandle xTimer )
\r
411 /* The timer has expired - so no button pushes have occurred in the last
\r
412 five seconds - turn the LED off. */
\r
413 vParTestSetLED( mainTIMER_CONTROLLED_LED, pdFALSE );
\r
415 /*-----------------------------------------------------------*/
\r
417 static void prvLEDTimerCallback( xTimerHandle xTimer )
\r
419 unsigned long ulLED;
\r
421 /* This callback is shared by two timers, so the parameter is used to
\r
422 determine which LED to toggle. The LED number is stored in the ID of the
\r
424 ulLED = ( unsigned long ) pvTimerGetTimerID( xTimer );
\r
425 vParTestToggleLED( ulLED );
\r
427 /*-----------------------------------------------------------*/
\r
429 /* The ISR executed when the user button is pushed. */
\r
430 void vPort_E_ISRHandler( void )
\r
432 portBASE_TYPE xHigherPriorityTaskWoken = pdFALSE;
\r
434 /* The button was pushed, so ensure the LED is on before resetting the
\r
435 LED timer. The LED timer will turn the LED off if the button is not
\r
436 pushed within 5000ms. */
\r
437 vParTestSetLED( mainTIMER_CONTROLLED_LED, pdTRUE );
\r
439 /* This interrupt safe FreeRTOS function can be called from this interrupt
\r
440 because the interrupt priority is equal to or below the
\r
441 configLIBRARY_MAX_SYSCALL_INTERRUPT_PRIORITY setting in FreeRTOSConfig.h. */
\r
442 xTimerResetFromISR( xLEDButtonTimer, &xHigherPriorityTaskWoken );
\r
444 /* Clear the interrupt before leaving. */
\r
445 PORTE_ISFR = 0xFFFFFFFFUL;
\r
447 /* If calling xTimerResetFromISR() caused a task (in this case the timer
\r
448 service/daemon task) to unblock, and the unblocked task has a priority
\r
449 higher than or equal to the task that was interrupted, then
\r
450 xHigherPriorityTaskWoken will now be set to pdTRUE, and calling
\r
451 portEND_SWITCHING_ISR() will ensure the unblocked task runs next. */
\r
452 portEND_SWITCHING_ISR( xHigherPriorityTaskWoken );
\r
454 /*-----------------------------------------------------------*/
\r
456 static void prvSetupHardware( void )
\r
458 /* Enable the interrupt on SW1. */
\r
459 taskDISABLE_INTERRUPTS();
\r
460 PORTE_PCR26 = PORT_PCR_MUX( 1 ) | PORT_PCR_IRQC( 0xA ) | PORT_PCR_PE_MASK | PORT_PCR_PS_MASK;
\r
461 enable_irq( mainGPIO_E_VECTOR );
\r
463 /* The interrupt calls an interrupt safe API function - so its priority must
\r
464 be equal to or lower than configLIBRARY_MAX_SYSCALL_INTERRUPT_PRIORITY. */
\r
465 set_irq_priority( mainGPIO_E_VECTOR, configLIBRARY_MAX_SYSCALL_INTERRUPT_PRIORITY );
\r
467 /* Configure the LED outputs. */
\r
468 vParTestInitialise();
\r
470 /*-----------------------------------------------------------*/
\r
472 static void prvCreateDemoSpecificTimers( void )
\r
474 /* This function creates the timers, but does not start them. This is
\r
475 because the standard demo timer test is started from main(), after this
\r
476 function is called. The standard demo timer test will deliberately fill the
\r
477 timer command queue - and will fail the test if the command queue already
\r
478 holds start commands for the timers created here. Instead, the timers
\r
479 created in this function are started from the idle task, at which time, the
\r
480 timer service/daemon task will be running, and will have drained the timer
\r
483 /* Create the software timer that is responsible for turning off the LED
\r
484 if the button is not pushed within 5000ms, as described at the top of
\r
486 xLEDButtonTimer = xTimerCreate( ( const signed char * ) "ButtonLEDTimer", /* A text name, purely to help debugging. */
\r
487 ( mainBUTTON_LED_TIMER_PERIOD_MS ), /* The timer period, in this case 5000ms (5s). */
\r
488 pdFALSE, /* This is a one shot timer, so xAutoReload is set to pdFALSE. */
\r
489 ( void * ) 0, /* The ID is not used, so can be set to anything. */
\r
490 prvButtonLEDTimerCallback /* The callback function that switches the LED off. */
\r
493 /* Create the software timer that performs the 'check' functionality,
\r
494 as described at the top of this file. */
\r
495 xCheckTimer = xTimerCreate( ( const signed char * ) "CheckTimer",/* A text name, purely to help debugging. */
\r
496 ( mainCHECK_TIMER_PERIOD_MS ), /* The timer period, in this case 3000ms (3s). */
\r
497 pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */
\r
498 ( void * ) 0, /* The ID is not used, so can be set to anything. */
\r
499 prvCheckTimerCallback /* The callback function that inspects the status of all the other tasks. */
\r
502 /* Create the software timers used to simply flash LEDs. These two timers
\r
503 share a callback function, so the callback parameter is used to pass in the
\r
504 LED that should be toggled. */
\r
505 xLED1Timer = xTimerCreate( ( const signed char * ) "LED1Timer",/* A text name, purely to help debugging. */
\r
506 ( mainLED1_TIMER_PERIOD_MS ), /* The timer period, in this case 3000ms (3s). */
\r
507 pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */
\r
508 ( void * ) mainLED0, /* The ID is used to pass in the number of the LED to be toggled. */
\r
509 prvLEDTimerCallback /* The callback function simply toggles the LED specified by its parameter. */
\r
512 xLED2Timer = xTimerCreate( ( const signed char * ) "LED2Timer",/* A text name, purely to help debugging. */
\r
513 ( mainLED2_TIMER_PERIOD_MS ), /* The timer period, in this case 3000ms (3s). */
\r
514 pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */
\r
515 ( void * ) mainLED1, /* The ID is used to pass in the number of the LED to be toggled. */
\r
516 prvLEDTimerCallback /* The callback function simply toggles the LED specified by its parameter. */
\r
519 /*-----------------------------------------------------------*/
\r
521 void vApplicationMallocFailedHook( void )
\r
523 /* Called if a call to pvPortMalloc() fails because there is insufficient
\r
524 free memory available in the FreeRTOS heap. pvPortMalloc() is called
\r
525 internally by FreeRTOS API functions that create tasks, queues, software
\r
526 timers, and semaphores. The size of the FreeRTOS heap is set by the
\r
527 configTOTAL_HEAP_SIZE configuration constant in FreeRTOSConfig.h. */
\r
528 taskDISABLE_INTERRUPTS();
\r
531 /*-----------------------------------------------------------*/
\r
533 void vApplicationStackOverflowHook( xTaskHandle *pxTask, signed char *pcTaskName )
\r
535 ( void ) pcTaskName;
\r
538 /* Run time stack overflow checking is performed if
\r
539 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
540 function is called if a stack overflow is detected. */
\r
541 taskDISABLE_INTERRUPTS();
\r
544 /*-----------------------------------------------------------*/
\r
546 void vApplicationIdleHook( void )
\r
548 static long lPrintedOut = pdFALSE;
\r
549 volatile size_t xFreeHeapSpace;
\r
551 if( lPrintedOut == pdFALSE )
\r
553 lPrintedOut = pdTRUE;
\r
555 /* The timer command queue will have been filled when the timer test
\r
556 tasks were created in main() (this is part of the test they perform).
\r
557 Therefore, while the check and LED timers can be created in main(), they
\r
558 cannot be started from main(). Once the scheduler has started, the timer
\r
559 service task will drain the command queue, and now the check and LED
\r
560 timers can be started successfully. Normally the idle task must not
\r
561 call a function that could cause it to block in case there are no tasks
\r
562 that are able to run. In this case, however, it is ok as posting to the
\r
563 timer command queue guarantees that at least the timer service/daemon
\r
564 task will be able to execute. */
\r
565 xTimerStart( xCheckTimer, portMAX_DELAY );
\r
566 xTimerStart( xLED1Timer, portMAX_DELAY );
\r
567 xTimerStart( xLED2Timer, portMAX_DELAY );
\r
569 xFreeHeapSpace = xPortGetFreeHeapSize();
\r
570 printf( "%d bytes of FreeRTOS heap remain unused\nconfigTOTAL_HEAP_SIZE can be reduced\n", xFreeHeapSpace );
\r
572 if( xFreeHeapSpace > 100 )
\r
574 /* By now, the kernel has allocated everything it is going to, so
\r
575 if there is a lot of heap remaining unallocated then
\r
576 the value of configTOTAL_HEAP_SIZE in FreeRTOSConfig.h can be
\r
577 reduced accordingly. */
\r
581 /*-----------------------------------------------------------*/
\r
583 void vApplicationTickHook( void )
\r
585 /* Call the periodic timer test, which tests the timer API functions that
\r
586 can be called from an ISR. */
\r
587 vTimerPeriodicISRTests();
\r
589 /*-----------------------------------------------------------*/
\r
591 char *pcGetTaskStatusMessage( void )
\r
593 /* A simple GET function used by a CGI script so it can display the
\r
594 execution status at the bottom of the task stats web page served by the
\r
595 embedded web server. */
\r
596 if( pcStatusMessage == NULL )
\r
598 return "All tasks running without error";
\r
602 return ( char * ) pcStatusMessage;
\r
605 /*-----------------------------------------------------------*/
\r
607 void vMainConfigureTimerForRunTimeStats( void )
\r
609 /* How many clocks are there per tenth of a millisecond? */
\r
610 ulClocksPer10thOfAMilliSecond = configCPU_CLOCK_HZ / 10000UL;
\r
612 /*-----------------------------------------------------------*/
\r
614 unsigned long ulMainGetRunTimeCounterValue( void )
\r
616 unsigned long ulSysTickCounts, ulTickCount, ulReturn;
\r
617 const unsigned long ulSysTickReloadValue = ( configCPU_CLOCK_HZ / configTICK_RATE_HZ ) - 1UL;
\r
618 volatile unsigned long * const pulCurrentSysTickCount = ( ( volatile unsigned long *) 0xe000e018 );
\r
619 volatile unsigned long * const pulInterruptCTRLState = ( ( volatile unsigned long *) 0xe000ed04 );
\r
620 const unsigned long ulSysTickPendingBit = 0x04000000UL;
\r
622 /* NOTE: There are potentially race conditions here. However, it is used
\r
623 anyway to keep the examples simple, and to avoid reliance on a separate
\r
624 timer peripheral. */
\r
627 /* The SysTick is a down counter. How many clocks have passed since it was
\r
629 ulSysTickCounts = ulSysTickReloadValue - *pulCurrentSysTickCount;
\r
631 /* How many times has it overflowed? */
\r
632 ulTickCount = xTaskGetTickCountFromISR();
\r
634 /* Is there a SysTick interrupt pending? */
\r
635 if( ( *pulInterruptCTRLState & ulSysTickPendingBit ) != 0UL )
\r
637 /* There is a SysTick interrupt pending, so the SysTick has overflowed
\r
638 but the tick count not yet incremented. */
\r
641 /* Read the SysTick again, as the overflow might have occurred since
\r
642 it was read last. */
\r
643 ulSysTickCounts = ulSysTickReloadValue - *pulCurrentSysTickCount;
\r
646 /* Convert the tick count into tenths of a millisecond. THIS ASSUMES
\r
647 configTICK_RATE_HZ is 1000! */
\r
648 ulReturn = ( ulTickCount * 10UL ) ;
\r
650 /* Add on the number of tenths of a millisecond that have passed since the
\r
651 tick count last got updated. */
\r
652 ulReturn += ( ulSysTickCounts / ulClocksPer10thOfAMilliSecond );
\r
656 /*-----------------------------------------------------------*/
\r