2 FreeRTOS V7.4.2 - Copyright (C) 2013 Real Time Engineers Ltd.
\r
4 FEATURES AND PORTS ARE ADDED TO FREERTOS ALL THE TIME. PLEASE VISIT
\r
5 http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.
\r
7 ***************************************************************************
\r
9 * FreeRTOS tutorial books are available in pdf and paperback. *
\r
10 * Complete, revised, and edited pdf reference manuals are also *
\r
13 * Purchasing FreeRTOS documentation will not only help you, by *
\r
14 * ensuring you get running as quickly as possible and with an *
\r
15 * in-depth knowledge of how to use FreeRTOS, it will also help *
\r
16 * the FreeRTOS project to continue with its mission of providing *
\r
17 * professional grade, cross platform, de facto standard solutions *
\r
18 * for microcontrollers - completely free of charge! *
\r
20 * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *
\r
22 * Thank you for using FreeRTOS, and thank you for your support! *
\r
24 ***************************************************************************
\r
27 This file is part of the FreeRTOS distribution.
\r
29 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
30 the terms of the GNU General Public License (version 2) as published by the
\r
31 Free Software Foundation AND MODIFIED BY the FreeRTOS exception.
\r
33 >>>>>>NOTE<<<<<< The modification to the GPL is included to allow you to
\r
34 distribute a combined work that includes FreeRTOS without being obliged to
\r
35 provide the source code for proprietary components outside of the FreeRTOS
\r
38 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
39 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
40 FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
\r
41 details. You should have received a copy of the GNU General Public License
\r
42 and the FreeRTOS license exception along with FreeRTOS; if not it can be
\r
43 viewed here: http://www.freertos.org/a00114.html and also obtained by
\r
44 writing to Real Time Engineers Ltd., contact details for whom are available
\r
45 on the FreeRTOS WEB site.
\r
49 ***************************************************************************
\r
51 * Having a problem? Start by reading the FAQ "My application does *
\r
52 * not run, what could be wrong?" *
\r
54 * http://www.FreeRTOS.org/FAQHelp.html *
\r
56 ***************************************************************************
\r
59 http://www.FreeRTOS.org - Documentation, books, training, latest versions,
\r
60 license and Real Time Engineers Ltd. contact details.
\r
62 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
63 including FreeRTOS+Trace - an indispensable productivity tool, and our new
\r
64 fully thread aware and reentrant UDP/IP stack.
\r
66 http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High
\r
67 Integrity Systems, who sell the code with commercial support,
\r
68 indemnification and middleware, under the OpenRTOS brand.
\r
70 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
71 engineered and independently SIL3 certified version for use in safety and
\r
72 mission critical applications that require provable dependability.
\r
76 * main-blinky.c is included when the "Blinky" build configuration is used.
\r
77 * main-full.c is included when the "Full" build configuration is used.
\r
79 * main-full.c (this file) defines a comprehensive demo that creates many
\r
80 * tasks, queues, semaphores and timers. It also demonstrates how Cortex-M3
\r
81 * interrupts can interact with FreeRTOS tasks/timers, a simple web server, and
\r
82 * run time statistics gathering functionality. ***IF YOU ARE LOOKING FOR A
\r
83 * SIMPLER STARTING POINT THEN USE THE "BLINKY" BUILD CONFIGURATION FIRST.***
\r
85 * If the Ethernet functionality is excluded, then this demo will run 'stand
\r
86 * alone' (without the rest of the tower system) on the TWR-K60N512 tower
\r
87 * module. If the Ethernet functionality is included, then the full Freescale
\r
88 * K60 tower kit, including both the TWR-K60N512 and TWR-SER modules, is
\r
89 * required (as the Ethernet connector is on the TWR-SER). The TWR-K60N512 is
\r
90 * populated with a K60N512 Cortex-M4 microcontroller.
\r
92 * The main() Function:
\r
93 * main() creates four demo specific software timers, and one demo specific
\r
94 * task (the web server task). It also creates a whole host of 'standard
\r
95 * demo' tasks/queues/semaphores/timers, before starting the scheduler. The
\r
96 * demo specific tasks and timers are described in the comments here. The
\r
97 * standard demo tasks are described on the FreeRTOS.org web site.
\r
99 * The standard demo tasks provide no specific functionality. They are
\r
100 * included to both test the FreeRTOS port, and provide examples of how the
\r
101 * various FreeRTOS API functions can be used.
\r
103 * This demo creates 37 persistent tasks, then dynamically creates and destroys
\r
104 * another two tasks as the demo executes.
\r
107 * The Demo Specific "LED" Timers and Callback Function:
\r
108 * Two very simple LED timers are created. All they do is toggle an LED each
\r
109 * when the timer callback function is executed. The two timers share a
\r
110 * callback function, so the callback function parameter is used to determine
\r
111 * which timer actually expired, and therefore, which LED to toggle. Both
\r
112 * timers use a different frequency, one toggles the blue LED and the other the
\r
115 * The LED/Button Software Timer and the Button Interrupt:
\r
116 * The user button SW2 is configured to generate an interrupt each time it is
\r
117 * pressed. The interrupt service routine switches the orange/yellow LED on,
\r
118 * and resets the LED software timer. The LED timer has a 5000 millisecond (5
\r
119 * second) period, and uses a callback function that is defined to just turn the
\r
120 * LED off again. Therefore, pressing the user button will turn the LED on, and
\r
121 * the LED will remain on until a full five seconds pass without the button
\r
124 * The Demo Specific "Check" Timer and Callback Function:
\r
125 * The check timer period is initially set to three seconds. The check timer
\r
126 * callback function checks that all the standard demo tasks are not only still
\r
127 * executing, but are executing without reporting any errors. If the check
\r
128 * timer discovers that a task has either stalled, or reported an error, then it
\r
129 * changes its own period from the initial three seconds, to just 200ms. The
\r
130 * check timer callback function also toggles the orange/red LED each time it is
\r
131 * called. This provides a visual indication of the system status: If the LED
\r
132 * toggles every three seconds, then no issues have been discovered. If the LED
\r
133 * toggles every 200ms, then an issue has been discovered with at least one
\r
134 * task. The last reported issue is latched into the pcStatusMessage variable,
\r
135 * and displayed at the bottom of the "task stats" web page served by the
\r
136 * embedded web server task.
\r
138 * The web server task:
\r
139 * The web server task implements a simple embedded web server that includes
\r
140 * CGI scripting. Pages are provided that allow task statistics, network
\r
141 * statistics and run time statistics to be viewed. In addition, an IO page is
\r
142 * served that allows the orange/yellow LED to be turned on and off. Finally,
\r
143 * a page is included that serves a large jpg file. See the documentation page
\r
144 * for this demo on the http://www.FreeRTOS.org web site for web server
\r
145 * configuration and usage instructions.
\r
147 * The Demo Specific Idle Hook Function:
\r
148 * The idle hook function demonstrates how to query the amount of FreeRTOS heap
\r
149 * space that is remaining (see vApplicationIdleHook() defined in this file).
\r
151 * The Demo Specific Tick Hook Function:
\r
152 * The tick hook function is used to test the interrupt safe software timer
\r
157 /* Kernel includes. */
\r
158 #include "FreeRTOS.h"
\r
161 #include "timers.h"
\r
163 /* Freescale includes. */
\r
164 #include "common.h"
\r
166 /* Common demo includes. */
\r
167 #include "partest.h"
\r
169 #include "BlockQ.h"
\r
171 #include "blocktim.h"
\r
172 #include "semtest.h"
\r
173 #include "GenQTest.h"
\r
175 #include "recmutex.h"
\r
176 #include "TimerDemo.h"
\r
178 #include "countsem.h"
\r
179 #include "dynamic.h"
\r
181 /* The LED toggled by the check timer callback function. */
\r
182 #define mainCHECK_LED 3UL
\r
184 /* The LED turned on by the button interrupt, and turned off by the LED timer. */
\r
185 #define mainTIMER_CONTROLLED_LED 2UL
\r
187 /* The LEDs toggled by the two simple flash LED timers. */
\r
188 #define mainLED0 0UL
\r
189 #define mainLED1 1UL
\r
191 /* Constant used by the standard timer test functions. */
\r
192 #define mainTIMER_TEST_PERIOD ( 50 )
\r
194 /* Priorities used by the various different standard demo tasks. */
\r
195 #define mainQUEUE_POLL_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
196 #define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
197 #define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
198 #define mainCREATOR_TASK_PRIORITY ( tskIDLE_PRIORITY + 3 )
\r
199 #define mainGEN_QUEUE_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
200 #define mainuIP_TASK_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
202 /* The WEB server uses string handling functions, which in turn use a bit more
\r
203 stack than most of the other tasks. */
\r
204 #define mainuIP_STACK_SIZE ( configMINIMAL_STACK_SIZE * 3 )
\r
206 /* The period at which the check timer will expire, in ms, provided no errors
\r
207 have been reported by any of the standard demo tasks. ms are converted to the
\r
208 equivalent in ticks using the portTICK_RATE_MS constant. */
\r
209 #define mainCHECK_TIMER_PERIOD_MS ( 3000UL / portTICK_RATE_MS )
\r
211 /* The period at which the check timer will expire, in ms, if an error has been
\r
212 reported in one of the standard demo tasks. ms are converted to the equivalent
\r
213 in ticks using the portTICK_RATE_MS constant. */
\r
214 #define mainERROR_CHECK_TIMER_PERIOD_MS ( 200UL / portTICK_RATE_MS )
\r
216 /* The LED that is turned on by pressing SW2 remains on until the button has not
\r
217 been pushed for a full 5000ms. */
\r
218 #define mainBUTTON_LED_TIMER_PERIOD_MS ( 5000UL / portTICK_RATE_MS )
\r
220 /* The period at which the two simple LED flash timers will execute their
\r
221 callback functions. */
\r
222 #define mainLED1_TIMER_PERIOD_MS ( 200UL / portTICK_RATE_MS )
\r
223 #define mainLED2_TIMER_PERIOD_MS ( 600UL / portTICK_RATE_MS )
\r
225 /* A block time of zero simply means "don't block". */
\r
226 #define mainDONT_BLOCK ( 0UL )
\r
228 /* The vector used by the GPIO port E. Button SW2 is configured to generate
\r
229 an interrupt on this port. */
\r
230 #define mainGPIO_E_VECTOR ( 91 )
\r
232 /*-----------------------------------------------------------*/
\r
235 * Setup the NVIC, LED outputs, and button inputs.
\r
237 static void prvSetupHardware( void );
\r
240 * Creates the timers that are specific to this demo - namely, the check timer
\r
241 * the button LED timer, and the two simple LED flash timers.
\r
243 static void prvCreateDemoSpecificTimers( void );
\r
246 * The LED/button timer callback function. This does nothing but switch an LED
\r
249 static void prvButtonLEDTimerCallback( xTimerHandle xTimer );
\r
252 * The callback function used by both simple LED flash timers. Both timers use
\r
253 * the same callback, so the function parameter is used to determine which LED
\r
254 * should be flashed (effectively to determine which timer has expired).
\r
256 static void prvLEDTimerCallback( xTimerHandle xTimer );
\r
259 * The check timer callback function, as described at the top of this file.
\r
261 static void prvCheckTimerCallback( xTimerHandle xTimer );
\r
264 * Contains the implementation of the web server.
\r
266 extern void vuIP_Task( void *pvParameters );
\r
268 /*-----------------------------------------------------------*/
\r
270 /* The LED/Button software timer. This uses prvButtonLEDTimerCallback() as it's
\r
271 callback function. */
\r
272 static xTimerHandle xLEDButtonTimer = NULL;
\r
274 /* The check timer. This uses prvCheckTimerCallback() as its callback
\r
276 static xTimerHandle xCheckTimer = NULL;
\r
278 /* LED timers - these simply flash LEDs, each using a different frequency. Both
\r
279 use the same prvLEDTimerCallback() callback function. */
\r
280 static xTimerHandle xLED1Timer = NULL, xLED2Timer = NULL;
\r
282 /* If an error is detected in a standard demo task, then pcStatusMessage will
\r
283 be set to point to a string that identifies the offending task. This is just
\r
284 to make debugging easier. */
\r
285 static const char *pcStatusMessage = NULL;
\r
287 /* Used in the run time stats calculations. */
\r
288 static unsigned long ulClocksPer10thOfAMilliSecond = 0UL;
\r
290 /*-----------------------------------------------------------*/
\r
294 /* Configure the NVIC, LED outputs and button inputs. */
\r
295 prvSetupHardware();
\r
297 /* Create the timers that are specific to this demo - other timers are
\r
298 created as part of the standard demo within vStartTimerDemoTask. */
\r
299 prvCreateDemoSpecificTimers();
\r
301 /* Create a lot of 'standard demo' tasks. Nearly 40 tasks are created in
\r
302 this demo. For a much simpler demo, select the 'blinky' build
\r
304 vStartBlockingQueueTasks( mainBLOCK_Q_PRIORITY );
\r
305 vCreateBlockTimeTasks();
\r
306 vStartSemaphoreTasks( mainSEM_TEST_PRIORITY );
\r
307 vStartGenericQueueTasks( mainGEN_QUEUE_TASK_PRIORITY );
\r
308 vStartQueuePeekTasks();
\r
309 vStartRecursiveMutexTasks();
\r
310 vStartTimerDemoTask( mainTIMER_TEST_PERIOD );
\r
311 vStartPolledQueueTasks( mainQUEUE_POLL_PRIORITY );
\r
312 vStartCountingSemaphoreTasks();
\r
313 vStartDynamicPriorityTasks();
\r
315 /* The web server task. */
\r
316 xTaskCreate( vuIP_Task, "uIP", mainuIP_STACK_SIZE, NULL, mainuIP_TASK_PRIORITY, NULL );
\r
318 /* The suicide tasks must be created last, as they need to know how many
\r
319 tasks were running prior to their creation in order to ascertain whether
\r
320 or not the correct/expected number of tasks are running at any given
\r
322 vCreateSuicidalTasks( mainCREATOR_TASK_PRIORITY );
\r
324 /* Start the tasks and timers running. */
\r
325 vTaskStartScheduler();
\r
327 /* If all is well, the scheduler will now be running, and the following line
\r
328 will never be reached. If the following line does execute, then there was
\r
329 insufficient FreeRTOS heap memory available for the idle and/or timer tasks
\r
330 to be created. See the memory management section on the FreeRTOS web site
\r
331 for more details. */
\r
334 /*-----------------------------------------------------------*/
\r
336 static void prvCheckTimerCallback( xTimerHandle xTimer )
\r
338 static long lChangedTimerPeriodAlready = pdFALSE;
\r
340 /* Check the standard demo tasks are running without error. Latch the
\r
341 latest reported error in the pcStatusMessage character pointer. The latched
\r
342 string can be viewed using the embedded web server - it is displayed at
\r
343 the bottom of the served "task stats" page. */
\r
344 if( xAreGenericQueueTasksStillRunning() != pdTRUE )
\r
346 pcStatusMessage = "Error: GenQueue";
\r
349 if( xAreQueuePeekTasksStillRunning() != pdTRUE )
\r
351 pcStatusMessage = "Error: QueuePeek\n";
\r
354 if( xAreBlockingQueuesStillRunning() != pdTRUE )
\r
356 pcStatusMessage = "Error: BlockQueue\n";
\r
359 if( xAreBlockTimeTestTasksStillRunning() != pdTRUE )
\r
361 pcStatusMessage = "Error: BlockTime\n";
\r
364 if( xAreSemaphoreTasksStillRunning() != pdTRUE )
\r
366 pcStatusMessage = "Error: SemTest\n";
\r
369 if( xIsCreateTaskStillRunning() != pdTRUE )
\r
371 pcStatusMessage = "Error: Death\n";
\r
374 if( xAreRecursiveMutexTasksStillRunning() != pdTRUE )
\r
376 pcStatusMessage = "Error: RecMutex\n";
\r
379 if( xAreTimerDemoTasksStillRunning( ( mainCHECK_TIMER_PERIOD_MS ) ) != pdTRUE )
\r
381 pcStatusMessage = "Error: TimerDemo\n";
\r
384 if( xArePollingQueuesStillRunning() != pdTRUE )
\r
386 pcStatusMessage = "Error: PollQueue\n";
\r
389 if( xAreCountingSemaphoreTasksStillRunning() != pdTRUE )
\r
391 pcStatusMessage = "Error: CountSem\n";
\r
394 if( xAreDynamicPriorityTasksStillRunning() != pdTRUE )
\r
396 pcStatusMessage = "Error: DynamicPriority\n";
\r
399 /* Toggle the check LED to give an indication of the system status. If
\r
400 the LED toggles every mainCHECK_TIMER_PERIOD_MS milliseconds then
\r
401 everything is ok. A faster toggle indicates an error. */
\r
402 vParTestToggleLED( mainCHECK_LED );
\r
404 /* Have any errors been latch in pcStatusMessage? If so, shorten the
\r
405 period of the check timer to mainERROR_CHECK_TIMER_PERIOD_MS milliseconds.
\r
406 This will result in an increase in the rate at which mainCHECK_LED
\r
408 if( pcStatusMessage != NULL )
\r
410 if( lChangedTimerPeriodAlready == pdFALSE )
\r
412 lChangedTimerPeriodAlready = pdTRUE;
\r
414 /* This call to xTimerChangePeriod() uses a zero block time.
\r
415 Functions called from inside of a timer callback function must
\r
416 *never* attempt to block. */
\r
417 xTimerChangePeriod( xCheckTimer, ( mainERROR_CHECK_TIMER_PERIOD_MS ), mainDONT_BLOCK );
\r
421 /*-----------------------------------------------------------*/
\r
423 static void prvButtonLEDTimerCallback( xTimerHandle xTimer )
\r
425 /* The timer has expired - so no button pushes have occurred in the last
\r
426 five seconds - turn the LED off. */
\r
427 vParTestSetLED( mainTIMER_CONTROLLED_LED, pdFALSE );
\r
429 /*-----------------------------------------------------------*/
\r
431 static void prvLEDTimerCallback( xTimerHandle xTimer )
\r
433 unsigned long ulLED;
\r
435 /* This callback is shared by two timers, so the parameter is used to
\r
436 determine which LED to toggle. The LED number is stored in the ID of the
\r
438 ulLED = ( unsigned long ) pvTimerGetTimerID( xTimer );
\r
439 vParTestToggleLED( ulLED );
\r
441 /*-----------------------------------------------------------*/
\r
443 /* The ISR executed when the user button is pushed. */
\r
444 void vPort_E_ISRHandler( void )
\r
446 portBASE_TYPE xHigherPriorityTaskWoken = pdFALSE;
\r
448 /* The button was pushed, so ensure the LED is on before resetting the
\r
449 LED timer. The LED timer will turn the LED off if the button is not
\r
450 pushed within 5000ms. */
\r
451 vParTestSetLED( mainTIMER_CONTROLLED_LED, pdTRUE );
\r
453 /* This interrupt safe FreeRTOS function can be called from this interrupt
\r
454 because the interrupt priority is equal to or below the
\r
455 configLIBRARY_MAX_SYSCALL_INTERRUPT_PRIORITY setting in FreeRTOSConfig.h. */
\r
456 xTimerResetFromISR( xLEDButtonTimer, &xHigherPriorityTaskWoken );
\r
458 /* Clear the interrupt before leaving. */
\r
459 PORTE_ISFR = 0xFFFFFFFFUL;
\r
461 /* If calling xTimerResetFromISR() caused a task (in this case the timer
\r
462 service/daemon task) to unblock, and the unblocked task has a priority
\r
463 higher than or equal to the task that was interrupted, then
\r
464 xHigherPriorityTaskWoken will now be set to pdTRUE, and calling
\r
465 portEND_SWITCHING_ISR() will ensure the unblocked task runs next. */
\r
466 portEND_SWITCHING_ISR( xHigherPriorityTaskWoken );
\r
468 /*-----------------------------------------------------------*/
\r
470 static void prvSetupHardware( void )
\r
472 /* Enable the interrupt on SW1. */
\r
473 taskDISABLE_INTERRUPTS();
\r
474 PORTE_PCR26 = PORT_PCR_MUX( 1 ) | PORT_PCR_IRQC( 0xA ) | PORT_PCR_PE_MASK | PORT_PCR_PS_MASK;
\r
475 enable_irq( mainGPIO_E_VECTOR );
\r
477 /* The interrupt calls an interrupt safe API function - so its priority must
\r
478 be equal to or lower than configLIBRARY_MAX_SYSCALL_INTERRUPT_PRIORITY. */
\r
479 set_irq_priority( mainGPIO_E_VECTOR, configLIBRARY_MAX_SYSCALL_INTERRUPT_PRIORITY );
\r
481 /* Configure the LED outputs. */
\r
482 vParTestInitialise();
\r
484 /*-----------------------------------------------------------*/
\r
486 static void prvCreateDemoSpecificTimers( void )
\r
488 /* This function creates the timers, but does not start them. This is
\r
489 because the standard demo timer test is started from main(), after this
\r
490 function is called. The standard demo timer test will deliberately fill the
\r
491 timer command queue - and will fail the test if the command queue already
\r
492 holds start commands for the timers created here. Instead, the timers
\r
493 created in this function are started from the idle task, at which time, the
\r
494 timer service/daemon task will be running, and will have drained the timer
\r
497 /* Create the software timer that is responsible for turning off the LED
\r
498 if the button is not pushed within 5000ms, as described at the top of
\r
500 xLEDButtonTimer = xTimerCreate( ( const signed char * ) "ButtonLEDTimer", /* A text name, purely to help debugging. */
\r
501 ( mainBUTTON_LED_TIMER_PERIOD_MS ), /* The timer period, in this case 5000ms (5s). */
\r
502 pdFALSE, /* This is a one shot timer, so xAutoReload is set to pdFALSE. */
\r
503 ( void * ) 0, /* The ID is not used, so can be set to anything. */
\r
504 prvButtonLEDTimerCallback /* The callback function that switches the LED off. */
\r
507 /* Create the software timer that performs the 'check' functionality,
\r
508 as described at the top of this file. */
\r
509 xCheckTimer = xTimerCreate( ( const signed char * ) "CheckTimer",/* A text name, purely to help debugging. */
\r
510 ( mainCHECK_TIMER_PERIOD_MS ), /* The timer period, in this case 3000ms (3s). */
\r
511 pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */
\r
512 ( void * ) 0, /* The ID is not used, so can be set to anything. */
\r
513 prvCheckTimerCallback /* The callback function that inspects the status of all the other tasks. */
\r
516 /* Create the software timers used to simply flash LEDs. These two timers
\r
517 share a callback function, so the callback parameter is used to pass in the
\r
518 LED that should be toggled. */
\r
519 xLED1Timer = xTimerCreate( ( const signed char * ) "LED1Timer",/* A text name, purely to help debugging. */
\r
520 ( mainLED1_TIMER_PERIOD_MS ), /* The timer period, in this case 3000ms (3s). */
\r
521 pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */
\r
522 ( void * ) mainLED0, /* The ID is used to pass in the number of the LED to be toggled. */
\r
523 prvLEDTimerCallback /* The callback function simply toggles the LED specified by its parameter. */
\r
526 xLED2Timer = xTimerCreate( ( const signed char * ) "LED2Timer",/* A text name, purely to help debugging. */
\r
527 ( mainLED2_TIMER_PERIOD_MS ), /* The timer period, in this case 3000ms (3s). */
\r
528 pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */
\r
529 ( void * ) mainLED1, /* The ID is used to pass in the number of the LED to be toggled. */
\r
530 prvLEDTimerCallback /* The callback function simply toggles the LED specified by its parameter. */
\r
533 /*-----------------------------------------------------------*/
\r
535 void vApplicationMallocFailedHook( void )
\r
537 /* Called if a call to pvPortMalloc() fails because there is insufficient
\r
538 free memory available in the FreeRTOS heap. pvPortMalloc() is called
\r
539 internally by FreeRTOS API functions that create tasks, queues, software
\r
540 timers, and semaphores. The size of the FreeRTOS heap is set by the
\r
541 configTOTAL_HEAP_SIZE configuration constant in FreeRTOSConfig.h. */
\r
542 taskDISABLE_INTERRUPTS();
\r
545 /*-----------------------------------------------------------*/
\r
547 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName )
\r
549 ( void ) pcTaskName;
\r
552 /* Run time stack overflow checking is performed if
\r
553 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
554 function is called if a stack overflow is detected. */
\r
555 taskDISABLE_INTERRUPTS();
\r
558 /*-----------------------------------------------------------*/
\r
560 void vApplicationIdleHook( void )
\r
562 static long lPrintedOut = pdFALSE;
\r
563 volatile size_t xFreeHeapSpace;
\r
565 if( lPrintedOut == pdFALSE )
\r
567 lPrintedOut = pdTRUE;
\r
569 /* The timer command queue will have been filled when the timer test
\r
570 tasks were created in main() (this is part of the test they perform).
\r
571 Therefore, while the check and LED timers can be created in main(), they
\r
572 cannot be started from main(). Once the scheduler has started, the timer
\r
573 service task will drain the command queue, and now the check and LED
\r
574 timers can be started successfully. Normally the idle task must not
\r
575 call a function that could cause it to block in case there are no tasks
\r
576 that are able to run. In this case, however, it is ok as posting to the
\r
577 timer command queue guarantees that at least the timer service/daemon
\r
578 task will be able to execute. */
\r
579 xTimerStart( xCheckTimer, portMAX_DELAY );
\r
580 xTimerStart( xLED1Timer, portMAX_DELAY );
\r
581 xTimerStart( xLED2Timer, portMAX_DELAY );
\r
583 xFreeHeapSpace = xPortGetFreeHeapSize();
\r
585 if( xFreeHeapSpace > 100 )
\r
587 /* By now, the kernel has allocated everything it is going to, so
\r
588 if there is a lot of heap remaining unallocated then
\r
589 the value of configTOTAL_HEAP_SIZE in FreeRTOSConfig.h can be
\r
590 reduced accordingly. */
\r
594 /*-----------------------------------------------------------*/
\r
596 void vApplicationTickHook( void )
\r
598 /* Call the periodic timer test, which tests the timer API functions that
\r
599 can be called from an ISR. */
\r
600 vTimerPeriodicISRTests();
\r
602 /*-----------------------------------------------------------*/
\r
604 char *pcGetTaskStatusMessage( void )
\r
606 /* A simple GET function used by a CGI script so it can display the
\r
607 execution status at the bottom of the task stats web page served by the
\r
608 embedded web server. */
\r
609 if( pcStatusMessage == NULL )
\r
611 return "All tasks running without error";
\r
615 return ( char * ) pcStatusMessage;
\r
618 /*-----------------------------------------------------------*/
\r
620 void vMainConfigureTimerForRunTimeStats( void )
\r
622 /* How many clocks are there per tenth of a millisecond? */
\r
623 ulClocksPer10thOfAMilliSecond = configCPU_CLOCK_HZ / 10000UL;
\r
625 /*-----------------------------------------------------------*/
\r
627 unsigned long ulMainGetRunTimeCounterValue( void )
\r
629 unsigned long ulSysTickCounts, ulTickCount, ulReturn;
\r
630 const unsigned long ulSysTickReloadValue = ( configCPU_CLOCK_HZ / configTICK_RATE_HZ ) - 1UL;
\r
631 volatile unsigned long * const pulCurrentSysTickCount = ( ( volatile unsigned long *) 0xe000e018 );
\r
632 volatile unsigned long * const pulInterruptCTRLState = ( ( volatile unsigned long *) 0xe000ed04 );
\r
633 const unsigned long ulSysTickPendingBit = 0x04000000UL;
\r
635 /* NOTE: There are potentially race conditions here. However, it is used
\r
636 anyway to keep the examples simple, and to avoid reliance on a separate
\r
637 timer peripheral. */
\r
640 /* The SysTick is a down counter. How many clocks have passed since it was
\r
642 ulSysTickCounts = ulSysTickReloadValue - *pulCurrentSysTickCount;
\r
644 /* How many times has it overflowed? */
\r
645 ulTickCount = xTaskGetTickCountFromISR();
\r
647 /* This is called from the context switch, so will be called from a
\r
648 critical section. xTaskGetTickCountFromISR() contains its own critical
\r
649 section, and the ISR safe critical sections are not designed to nest,
\r
650 so reset the critical section. */
\r
651 portSET_INTERRUPT_MASK_FROM_ISR();
\r
653 /* Is there a SysTick interrupt pending? */
\r
654 if( ( *pulInterruptCTRLState & ulSysTickPendingBit ) != 0UL )
\r
656 /* There is a SysTick interrupt pending, so the SysTick has overflowed
\r
657 but the tick count not yet incremented. */
\r
660 /* Read the SysTick again, as the overflow might have occurred since
\r
661 it was read last. */
\r
662 ulSysTickCounts = ulSysTickReloadValue - *pulCurrentSysTickCount;
\r
665 /* Convert the tick count into tenths of a millisecond. THIS ASSUMES
\r
666 configTICK_RATE_HZ is 1000! */
\r
667 ulReturn = ( ulTickCount * 10UL ) ;
\r
669 /* Add on the number of tenths of a millisecond that have passed since the
\r
670 tick count last got updated. */
\r
671 ulReturn += ( ulSysTickCounts / ulClocksPer10thOfAMilliSecond );
\r
675 /*-----------------------------------------------------------*/
\r