2 FreeRTOS V8.2.1 - Copyright (C) 2015 Real Time Engineers Ltd.
\r
5 VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.
\r
7 This file is part of the FreeRTOS distribution.
\r
9 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
10 the terms of the GNU General Public License (version 2) as published by the
\r
11 Free Software Foundation >>!AND MODIFIED BY!<< the FreeRTOS exception.
\r
13 ***************************************************************************
\r
14 >>! NOTE: The modification to the GPL is included to allow you to !<<
\r
15 >>! distribute a combined work that includes FreeRTOS without being !<<
\r
16 >>! obliged to provide the source code for proprietary components !<<
\r
17 >>! outside of the FreeRTOS kernel. !<<
\r
18 ***************************************************************************
\r
20 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
21 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
22 FOR A PARTICULAR PURPOSE. Full license text is available on the following
\r
23 link: http://www.freertos.org/a00114.html
\r
25 ***************************************************************************
\r
27 * FreeRTOS provides completely free yet professionally developed, *
\r
28 * robust, strictly quality controlled, supported, and cross *
\r
29 * platform software that is more than just the market leader, it *
\r
30 * is the industry's de facto standard. *
\r
32 * Help yourself get started quickly while simultaneously helping *
\r
33 * to support the FreeRTOS project by purchasing a FreeRTOS *
\r
34 * tutorial book, reference manual, or both: *
\r
35 * http://www.FreeRTOS.org/Documentation *
\r
37 ***************************************************************************
\r
39 http://www.FreeRTOS.org/FAQHelp.html - Having a problem? Start by reading
\r
40 the FAQ page "My application does not run, what could be wrong?". Have you
\r
41 defined configASSERT()?
\r
43 http://www.FreeRTOS.org/support - In return for receiving this top quality
\r
44 embedded software for free we request you assist our global community by
\r
45 participating in the support forum.
\r
47 http://www.FreeRTOS.org/training - Investing in training allows your team to
\r
48 be as productive as possible as early as possible. Now you can receive
\r
49 FreeRTOS training directly from Richard Barry, CEO of Real Time Engineers
\r
50 Ltd, and the world's leading authority on the world's leading RTOS.
\r
52 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
53 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
54 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
56 http://www.FreeRTOS.org/labs - Where new FreeRTOS products go to incubate.
\r
57 Come and try FreeRTOS+TCP, our new open source TCP/IP stack for FreeRTOS.
\r
59 http://www.OpenRTOS.com - Real Time Engineers ltd. license FreeRTOS to High
\r
60 Integrity Systems ltd. to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
61 licenses offer ticketed support, indemnification and commercial middleware.
\r
63 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
64 engineered and independently SIL3 certified version for use in safety and
\r
65 mission critical applications that require provable dependability.
\r
71 * main-blinky.c is included when the "Blinky" build configuration is used.
\r
72 * main-full.c is included when the "Full" build configuration is used.
\r
74 * main-full.c (this file) defines a comprehensive demo that creates many
\r
75 * tasks, queues, semaphores and timers. It also demonstrates how Cortex-M3
\r
76 * interrupts can interact with FreeRTOS tasks/timers.
\r
78 * This project runs on the SK-FM3-100PMC evaluation board, which is populated
\r
79 * with an MB9BF5006N Cortex-M3 based microcontroller.
\r
81 * The main() Function:
\r
82 * main() creates three demo specific software timers, one demo specific queue,
\r
83 * and two demo specific tasks. It then creates a whole host of 'standard
\r
84 * demo' tasks/queues/semaphores, before starting the scheduler. The demo
\r
85 * specific tasks and timers are described in the comments here. The standard
\r
86 * demo tasks are described on the FreeRTOS.org web site.
\r
88 * The standard demo tasks provide no specific functionality. They are
\r
89 * included to both test the FreeRTOS port, and provide examples of how the
\r
90 * various FreeRTOS API functions can be used.
\r
92 * This demo creates 43 tasks in total. If you want a simpler demo, use the
\r
93 * Blinky build configuration.
\r
95 * The Demo Specific Queue Send Task:
\r
96 * The queue send task is implemented by the prvQueueSendTask() function in
\r
97 * this file. prvQueueSendTask() sits in a loop that causes it to repeatedly
\r
98 * block for 200 milliseconds, before sending the value 100 to the queue that
\r
99 * was created within main(). Once the value is sent, the task loops back
\r
100 * around to block for another 200 milliseconds.
\r
102 * The Demo Specific Queue Receive Task:
\r
103 * The queue receive task is implemented by the prvQueueReceiveTask() function
\r
104 * in this file. prvQueueReceiveTask() sits in a loop that causes it to
\r
105 * repeatedly attempt to read data from the queue that was created within
\r
106 * main(). When data is received, the task checks the value of the data, and
\r
107 * if the value equals the expected 100, toggles an LED in the 7 segment display
\r
108 * (see the documentation page for this demo on the FreeRTOS.org site to see
\r
109 * which LED is used). The 'block time' parameter passed to the queue receive
\r
110 * function specifies that the task should be held in the Blocked state
\r
111 * indefinitely to wait for data to be available on the queue. The queue
\r
112 * receive task will only leave the Blocked state when the queue send task
\r
113 * writes to the queue. As the queue send task writes to the queue every 200
\r
114 * milliseconds, the queue receive task leaves the Blocked state every 200
\r
115 * milliseconds, and therefore toggles the LED every 200 milliseconds.
\r
117 * The Demo Specific LED Software Timer and the Button Interrupt:
\r
118 * The user button SW2 is configured to generate an interrupt each time it is
\r
119 * pressed. The interrupt service routine switches an LED on, and resets the
\r
120 * LED software timer. The LED timer has a 5000 millisecond (5 second) period,
\r
121 * and uses a callback function that is defined to just turn the LED off again.
\r
122 * Therefore, pressing the user button will turn the LED on, and the LED will
\r
123 * remain on until a full five seconds pass without the button being pressed.
\r
124 * See the documentation page for this demo on the FreeRTOS.org web site to see
\r
125 * which LED is used.
\r
127 * The Demo Specific "Check" Callback Function:
\r
128 * This is called each time the 'check' timer expires. The check timer
\r
129 * callback function inspects all the standard demo tasks to see if they are
\r
130 * all executing as expected. The check timer is initially configured to
\r
131 * expire every three seconds, but will shorted this to every 500ms if an error
\r
132 * is ever discovered. The check timer callback toggles the LED defined by
\r
133 * the mainCHECK_LED definition each time it executes. Therefore, if LED
\r
134 * mainCHECK_LED is toggling every three seconds, then no error have been found.
\r
135 * If LED mainCHECK_LED is toggling every 500ms, then at least one errors has
\r
136 * been found. The variable pcStatusMessage is set to a string that indicates
\r
137 * which task reported an error. See the documentation page for this demo on
\r
138 * the FreeRTOS.org web site to see which LED in the 7 segment display is used.
\r
140 * The Demo Specific "Digit Counter" Callback Function:
\r
141 * This is called each time the 'digit counter' timer expires. It causes the
\r
142 * digits 0 to 9 to be displayed in turn as the first character of the two
\r
143 * character display. The LEDs in the other digit of the two character
\r
144 * display are used as general purpose LEDs, as described in this comment block.
\r
146 * The Demo Specific Idle Hook Function:
\r
147 * The idle hook function demonstrates how to query the amount of FreeRTOS heap
\r
148 * space that is remaining (see vApplicationIdleHook() defined in this file).
\r
150 * The Demo Specific Tick Hook Function:
\r
151 * The tick hook function is used to test the interrupt safe software timer
\r
155 /* Kernel includes. */
\r
156 #include "FreeRTOS.h"
\r
159 #include "timers.h"
\r
161 /* Fujitsu drivers/libraries. */
\r
162 #include "mb9bf506n.h"
\r
163 #include "system_mb9bf50x.h"
\r
165 /* Common demo includes. */
\r
166 #include "partest.h"
\r
168 #include "BlockQ.h"
\r
170 #include "blocktim.h"
\r
171 #include "semtest.h"
\r
172 #include "GenQTest.h"
\r
174 #include "recmutex.h"
\r
175 #include "TimerDemo.h"
\r
176 #include "comtest2.h"
\r
178 #include "countsem.h"
\r
179 #include "dynamic.h"
\r
181 /* The rate at which data is sent to the queue, specified in milliseconds, and
\r
182 converted to ticks using the portTICK_PERIOD_MS constant. */
\r
183 #define mainQUEUE_SEND_FREQUENCY_MS ( 200 / portTICK_PERIOD_MS )
\r
185 /* The number of items the queue can hold. This is 1 as the receive task
\r
186 will remove items as they are added, meaning the send task should always find
\r
187 the queue empty. */
\r
188 #define mainQUEUE_LENGTH ( 1 )
\r
190 /* The LED toggled by the check timer callback function. This is an LED in the
\r
191 second digit of the two digit 7 segment display. See the documentation page
\r
192 for this demo on the FreeRTOS.org web site to see which LED this relates to. */
\r
193 #define mainCHECK_LED 0x07UL
\r
195 /* The LED toggle by the queue receive task. This is an LED in the second digit
\r
196 of the two digit 7 segment display. See the documentation page for this demo on
\r
197 the FreeRTOS.org web site to see which LED this relates to. */
\r
198 #define mainTASK_CONTROLLED_LED 0x06UL
\r
200 /* The LED turned on by the button interrupt, and turned off by the LED timer.
\r
201 This is an LED in the second digit of the two digit 7 segment display. See the
\r
202 documentation page for this demo on the FreeRTOS.org web site to see which LED
\r
203 this relates to. */
\r
204 #define mainTIMER_CONTROLLED_LED 0x05UL
\r
206 /* The LED used by the comtest tasks. See the comtest.c file for more
\r
207 information. The LEDs used by the comtest task are in the second digit of the
\r
208 two digit 7 segment display. See the documentation page for this demo on the
\r
209 FreeRTOS.org web site to see which LEDs this relates to. */
\r
210 #define mainCOM_TEST_LED ( 3 )
\r
212 /* Constant used by the standard timer test functions. */
\r
213 #define mainTIMER_TEST_PERIOD ( 50 )
\r
215 /* Priorities used by the various different standard demo tasks. */
\r
216 #define mainCHECK_TASK_PRIORITY ( configMAX_PRIORITIES - 1 )
\r
217 #define mainQUEUE_POLL_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
218 #define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
219 #define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
220 #define mainCREATOR_TASK_PRIORITY ( tskIDLE_PRIORITY + 3 )
\r
221 #define mainFLASH_TASK_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
222 #define mainINTEGER_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
223 #define mainGEN_QUEUE_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
224 #define mainCOM_TEST_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
226 /* Priorities defined in this main-full.c file. */
\r
227 #define mainQUEUE_RECEIVE_TASK_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
228 #define mainQUEUE_SEND_TASK_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
230 /* The period at which the check timer will expire, in ms, provided no errors
\r
231 have been reported by any of the standard demo tasks. ms are converted to the
\r
232 equivalent in ticks using the portTICK_PERIOD_MS constant. */
\r
233 #define mainCHECK_TIMER_PERIOD_MS ( 3000UL / portTICK_PERIOD_MS )
\r
235 /* The period at which the check timer will expire, in ms, if an error has been
\r
236 reported in one of the standard demo tasks. ms are converted to the equivalent
\r
237 in ticks using the portTICK_PERIOD_MS constant. */
\r
238 #define mainERROR_CHECK_TIMER_PERIOD_MS ( 500UL / portTICK_PERIOD_MS )
\r
240 /* The period at which the digit counter timer will expire, in ms, and converted
\r
241 to ticks using the portTICK_PERIOD_MS constant. */
\r
242 #define mainDIGIT_COUNTER_TIMER_PERIOD_MS ( 250UL / portTICK_PERIOD_MS )
\r
244 /* The LED will remain on until the button has not been pushed for a full
\r
246 #define mainLED_TIMER_PERIOD_MS ( 5000UL / portTICK_PERIOD_MS )
\r
248 /* A zero block time. */
\r
249 #define mainDONT_BLOCK ( 0UL )
\r
251 /* Baud rate used by the comtest tasks. */
\r
252 #define mainCOM_TEST_BAUD_RATE ( 115200UL )
\r
254 /*-----------------------------------------------------------*/
\r
257 * Setup the NVIC, LED outputs, and button inputs.
\r
259 static void prvSetupHardware( void );
\r
262 * The application specific (not common demo) tasks as described in the comments
\r
263 * at the top of this file.
\r
265 static void prvQueueReceiveTask( void *pvParameters );
\r
266 static void prvQueueSendTask( void *pvParameters );
\r
269 * The LED timer callback function. This does nothing but switch an LED off.
\r
271 static void prvLEDTimerCallback( TimerHandle_t xTimer );
\r
274 * The check timer callback function, as described at the top of this file.
\r
276 static void prvCheckTimerCallback( TimerHandle_t xTimer );
\r
279 * The digit counter callback function, as described at the top of this file.
\r
281 static void prvDigitCounterTimerCallback( TimerHandle_t xTimer );
\r
284 * This is not a 'standard' partest function, so the prototype is not in
\r
285 * partest.h, and is instead included here.
\r
287 void vParTestSetLEDFromISR( unsigned portBASE_TYPE uxLED, signed portBASE_TYPE xValue );
\r
289 /*-----------------------------------------------------------*/
\r
291 /* The queue used by both application specific demo tasks defined in this file. */
\r
292 static QueueHandle_t xQueue = NULL;
\r
294 /* The LED software timer. This uses prvLEDTimerCallback() as it's callback
\r
296 static TimerHandle_t xLEDTimer = NULL;
\r
298 /* The digit counter software timer. This displays a counting digit on one half
\r
299 of the seven segment displays. */
\r
300 static TimerHandle_t xDigitCounterTimer = NULL;
\r
302 /* The check timer. This uses prvCheckTimerCallback() as its callback
\r
304 static TimerHandle_t xCheckTimer = NULL;
\r
306 /* If an error is detected in a standard demo task, then pcStatusMessage will
\r
307 be set to point to a string that identifies the offending task. This is just
\r
308 to make debugging easier. */
\r
309 static const char *pcStatusMessage = NULL;
\r
311 /*-----------------------------------------------------------*/
\r
315 /* Configure the NVIC, LED outputs and button inputs. */
\r
316 prvSetupHardware();
\r
318 /* Create the queue. */
\r
319 xQueue = xQueueCreate( mainQUEUE_LENGTH, sizeof( unsigned long ) );
\r
321 if( xQueue != NULL )
\r
323 /* Start the two application specific demo tasks, as described in the
\r
324 comments at the top of this file. */
\r
325 xTaskCreate( prvQueueReceiveTask, "Rx", configMINIMAL_STACK_SIZE, NULL, mainQUEUE_RECEIVE_TASK_PRIORITY, NULL );
\r
326 xTaskCreate( prvQueueSendTask, "TX", configMINIMAL_STACK_SIZE, NULL, mainQUEUE_SEND_TASK_PRIORITY, NULL );
\r
328 /* Create the software timer that is responsible for turning off the LED
\r
329 if the button is not pushed within 5000ms, as described at the top of
\r
331 xLEDTimer = xTimerCreate( "LEDTimer", /* A text name, purely to help debugging. */
\r
332 ( mainLED_TIMER_PERIOD_MS ),/* The timer period, in this case 5000ms (5s). */
\r
333 pdFALSE, /* This is a one shot timer, so xAutoReload is set to pdFALSE. */
\r
334 ( void * ) 0, /* The ID is not used, so can be set to anything. */
\r
335 prvLEDTimerCallback /* The callback function that switches the LED off. */
\r
338 /* Create the software timer that performs the 'check' functionality,
\r
339 as described at the top of this file. */
\r
340 xCheckTimer = xTimerCreate( "CheckTimer", /* A text name, purely to help debugging. */
\r
341 ( mainCHECK_TIMER_PERIOD_MS ), /* The timer period, in this case 3000ms (3s). */
\r
342 pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */
\r
343 ( void * ) 0, /* The ID is not used, so can be set to anything. */
\r
344 prvCheckTimerCallback /* The callback function that inspects the status of all the other tasks. */
\r
347 /* Create the software timer that performs the 'digit counting'
\r
348 functionality, as described at the top of this file. */
\r
349 xDigitCounterTimer = xTimerCreate( "DigitCounter", /* A text name, purely to help debugging. */
\r
350 ( mainDIGIT_COUNTER_TIMER_PERIOD_MS ), /* The timer period, in this case 3000ms (3s). */
\r
351 pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */
\r
352 ( void * ) 0, /* The ID is not used, so can be set to anything. */
\r
353 prvDigitCounterTimerCallback /* The callback function that inspects the status of all the other tasks. */
\r
356 /* Create a lot of 'standard demo' tasks. Over 40 tasks are created in
\r
357 this demo. For a much simpler demo, select the 'blinky' build
\r
359 vStartBlockingQueueTasks( mainBLOCK_Q_PRIORITY );
\r
360 vCreateBlockTimeTasks();
\r
361 vStartSemaphoreTasks( mainSEM_TEST_PRIORITY );
\r
362 vStartGenericQueueTasks( mainGEN_QUEUE_TASK_PRIORITY );
\r
363 vStartLEDFlashTasks( mainFLASH_TASK_PRIORITY );
\r
364 vStartQueuePeekTasks();
\r
365 vStartRecursiveMutexTasks();
\r
366 vStartTimerDemoTask( mainTIMER_TEST_PERIOD );
\r
367 vAltStartComTestTasks( mainCOM_TEST_PRIORITY, mainCOM_TEST_BAUD_RATE, mainCOM_TEST_LED );
\r
368 vStartPolledQueueTasks( mainQUEUE_POLL_PRIORITY );
\r
369 vStartCountingSemaphoreTasks();
\r
370 vStartDynamicPriorityTasks();
\r
372 /* The suicide tasks must be created last, as they need to know how many
\r
373 tasks were running prior to their creation in order to ascertain whether
\r
374 or not the correct/expected number of tasks are running at any given
\r
376 vCreateSuicidalTasks( mainCREATOR_TASK_PRIORITY );
\r
378 /* Start the tasks and timer running. */
\r
379 vTaskStartScheduler();
\r
382 /* If all is well, the scheduler will now be running, and the following line
\r
383 will never be reached. If the following line does execute, then there was
\r
384 insufficient FreeRTOS heap memory available for the idle and/or timer tasks
\r
385 to be created. See the memory management section on the FreeRTOS web site
\r
386 for more details. */
\r
389 /*-----------------------------------------------------------*/
\r
391 static void prvCheckTimerCallback( TimerHandle_t xTimer )
\r
393 /* Check the standard demo tasks are running without error. Latch the
\r
394 latest reported error in the pcStatusMessage character pointer. */
\r
395 if( xAreGenericQueueTasksStillRunning() != pdTRUE )
\r
397 pcStatusMessage = "Error: GenQueue";
\r
400 if( xAreQueuePeekTasksStillRunning() != pdTRUE )
\r
402 pcStatusMessage = "Error: QueuePeek\r\n";
\r
405 if( xAreBlockingQueuesStillRunning() != pdTRUE )
\r
407 pcStatusMessage = "Error: BlockQueue\r\n";
\r
410 if( xAreBlockTimeTestTasksStillRunning() != pdTRUE )
\r
412 pcStatusMessage = "Error: BlockTime\r\n";
\r
415 if( xAreSemaphoreTasksStillRunning() != pdTRUE )
\r
417 pcStatusMessage = "Error: SemTest\r\n";
\r
420 if( xIsCreateTaskStillRunning() != pdTRUE )
\r
422 pcStatusMessage = "Error: Death\r\n";
\r
425 if( xAreRecursiveMutexTasksStillRunning() != pdTRUE )
\r
427 pcStatusMessage = "Error: RecMutex\r\n";
\r
430 if( xAreComTestTasksStillRunning() != pdPASS )
\r
432 pcStatusMessage = "Error: ComTest\r\n";
\r
435 if( xAreTimerDemoTasksStillRunning( ( mainCHECK_TIMER_PERIOD_MS ) ) != pdTRUE )
\r
437 pcStatusMessage = "Error: TimerDemo";
\r
440 if( xArePollingQueuesStillRunning() != pdTRUE )
\r
442 pcStatusMessage = "Error: PollQueue";
\r
445 if( xAreCountingSemaphoreTasksStillRunning() != pdTRUE )
\r
447 pcStatusMessage = "Error: CountSem";
\r
450 if( xAreDynamicPriorityTasksStillRunning() != pdTRUE )
\r
452 pcStatusMessage = "Error: DynamicPriority";
\r
455 /* Toggle the check LED to give an indication of the system status. If
\r
456 the LED toggles every mainCHECK_TIMER_PERIOD_MS milliseconds then
\r
457 everything is ok. A faster toggle indicates an error. */
\r
458 vParTestToggleLED( mainCHECK_LED );
\r
460 /* Have any errors been latch in pcStatusMessage? If so, shorten the
\r
461 period of the check timer to mainERROR_CHECK_TIMER_PERIOD_MS milliseconds.
\r
462 This will result in an increase in the rate at which mainCHECK_LED
\r
464 if( pcStatusMessage != NULL )
\r
466 /* This call to xTimerChangePeriod() uses a zero block time. Functions
\r
467 called from inside of a timer callback function must *never* attempt
\r
469 xTimerChangePeriod( xCheckTimer, ( mainERROR_CHECK_TIMER_PERIOD_MS ), mainDONT_BLOCK );
\r
472 /*-----------------------------------------------------------*/
\r
474 static void prvLEDTimerCallback( TimerHandle_t xTimer )
\r
476 /* The timer has expired - so no button pushes have occurred in the last
\r
477 five seconds - turn the LED off. */
\r
478 vParTestSetLED( mainTIMER_CONTROLLED_LED, pdFALSE );
\r
480 /*-----------------------------------------------------------*/
\r
482 static void prvDigitCounterTimerCallback( TimerHandle_t xTimer )
\r
484 /* Define the bit patterns that display numbers on the seven segment display. */
\r
485 static const unsigned short usNumbersPatterns[] = { 0xC000U, 0xF900U, 0xA400U, 0xB000U, 0x9900U, 0x9200U, 0x8200U, 0xF800U, 0x8000U, 0x9000U };
\r
486 static long lCounter = 0L;
\r
487 const long lNumberOfDigits = 10L;
\r
489 /* Display the next number, counting up. */
\r
490 FM3_GPIO->PDOR1 = usNumbersPatterns[ lCounter ];
\r
492 /* Move onto the next digit. */
\r
495 /* Ensure the counter does not go off the end of the array. */
\r
496 if( lCounter >= lNumberOfDigits )
\r
501 /*-----------------------------------------------------------*/
\r
503 /* The ISR executed when the user button is pushed. */
\r
504 void INT0_7_Handler( void )
\r
506 portBASE_TYPE xHigherPriorityTaskWoken = pdFALSE;
\r
508 /* The button was pushed, so ensure the LED is on before resetting the
\r
509 LED timer. The LED timer will turn the LED off if the button is not
\r
510 pushed within 5000ms. */
\r
511 vParTestSetLEDFromISR( mainTIMER_CONTROLLED_LED, pdTRUE );
\r
513 /* This interrupt safe FreeRTOS function can be called from this interrupt
\r
514 because the interrupt priority is below the
\r
515 configMAX_SYSCALL_INTERRUPT_PRIORITY setting in FreeRTOSConfig.h. */
\r
516 xTimerResetFromISR( xLEDTimer, &xHigherPriorityTaskWoken );
\r
518 /* Clear the interrupt before leaving. This just clears all the interrupts
\r
519 for simplicity, as only one is actually used in this simple demo anyway. */
\r
520 FM3_EXTI->EICL = 0x0000;
\r
522 /* If calling xTimerResetFromISR() caused a task (in this case the timer
\r
523 service/daemon task) to unblock, and the unblocked task has a priority
\r
524 higher than or equal to the task that was interrupted, then
\r
525 xHigherPriorityTaskWoken will now be set to pdTRUE, and calling
\r
526 portEND_SWITCHING_ISR() will ensure the unblocked task runs next. */
\r
527 portEND_SWITCHING_ISR( xHigherPriorityTaskWoken );
\r
529 /*-----------------------------------------------------------*/
\r
531 static void prvQueueSendTask( void *pvParameters )
\r
533 TickType_t xNextWakeTime;
\r
534 const unsigned long ulValueToSend = 100UL;
\r
536 /* The timer command queue will have been filled when the timer test tasks
\r
537 were created in main() (this is part of the test they perform). Therefore,
\r
538 while the check and digit counter timers can be created in main(), they
\r
539 cannot be started from main(). Once the scheduler has started, the timer
\r
540 service task will drain the command queue, and now the check and digit
\r
541 counter timers can be started successfully. */
\r
542 xTimerStart( xCheckTimer, portMAX_DELAY );
\r
543 xTimerStart( xDigitCounterTimer, portMAX_DELAY );
\r
545 /* Initialise xNextWakeTime - this only needs to be done once. */
\r
546 xNextWakeTime = xTaskGetTickCount();
\r
550 /* Place this task in the blocked state until it is time to run again.
\r
551 The block time is specified in ticks, the constant used converts ticks
\r
552 to ms. While in the Blocked state this task will not consume any CPU
\r
554 vTaskDelayUntil( &xNextWakeTime, mainQUEUE_SEND_FREQUENCY_MS );
\r
556 /* Send to the queue - causing the queue receive task to unblock and
\r
557 toggle an LED. 0 is used as the block time so the sending operation
\r
558 will not block - it shouldn't need to block as the queue should always
\r
559 be empty at this point in the code. */
\r
560 xQueueSend( xQueue, &ulValueToSend, mainDONT_BLOCK );
\r
563 /*-----------------------------------------------------------*/
\r
565 static void prvQueueReceiveTask( void *pvParameters )
\r
567 unsigned long ulReceivedValue;
\r
571 /* Wait until something arrives in the queue - this task will block
\r
572 indefinitely provided INCLUDE_vTaskSuspend is set to 1 in
\r
573 FreeRTOSConfig.h. */
\r
574 xQueueReceive( xQueue, &ulReceivedValue, portMAX_DELAY );
\r
576 /* To get here something must have been received from the queue, but
\r
577 is it the expected value? If it is, toggle the LED. */
\r
578 if( ulReceivedValue == 100UL )
\r
580 vParTestToggleLED( mainTASK_CONTROLLED_LED );
\r
584 /*-----------------------------------------------------------*/
\r
586 static void prvSetupHardware( void )
\r
588 const unsigned short usButtonInputBit = 0x01U;
\r
591 SystemCoreClockUpdate();
\r
593 /* Initialise the IO used for the LEDs on the 7 segment displays. */
\r
594 vParTestInitialise();
\r
596 /* Set the switches to input (P18->P1F). */
\r
597 FM3_GPIO->DDR5 = 0x0000;
\r
598 FM3_GPIO->PFR5 = 0x0000;
\r
600 /* Assign the button input as GPIO. */
\r
601 FM3_GPIO->PFR1 |= usButtonInputBit;
\r
603 /* Button interrupt on falling edge. */
\r
604 FM3_EXTI->ELVR = 0x0003;
\r
606 /* Clear all external interrupts. */
\r
607 FM3_EXTI->EICL = 0x0000;
\r
609 /* Enable the button interrupt. */
\r
610 FM3_EXTI->ENIR |= usButtonInputBit;
\r
612 /* Setup the GPIO and the NVIC for the switch used in this simple demo. */
\r
613 NVIC_SetPriority( EXINT0_7_IRQn, configLIBRARY_MAX_SYSCALL_INTERRUPT_PRIORITY );
\r
614 NVIC_EnableIRQ( EXINT0_7_IRQn );
\r
616 /*-----------------------------------------------------------*/
\r
618 void vApplicationMallocFailedHook( void )
\r
620 /* Called if a call to pvPortMalloc() fails because there is insufficient
\r
621 free memory available in the FreeRTOS heap. pvPortMalloc() is called
\r
622 internally by FreeRTOS API functions that create tasks, queues, software
\r
623 timers, and semaphores. The size of the FreeRTOS heap is set by the
\r
624 configTOTAL_HEAP_SIZE configuration constant in FreeRTOSConfig.h. */
\r
627 /*-----------------------------------------------------------*/
\r
629 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
631 ( void ) pcTaskName;
\r
634 /* Run time stack overflow checking is performed if
\r
635 configconfigCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
636 function is called if a stack overflow is detected. */
\r
637 taskDISABLE_INTERRUPTS();
\r
640 /*-----------------------------------------------------------*/
\r
642 void vApplicationIdleHook( void )
\r
644 volatile size_t xFreeStackSpace;
\r
646 /* This function is called on each cycle of the idle task. In this case it
\r
647 does nothing useful, other than report the amount of FreeRTOS heap that
\r
648 remains unallocated. */
\r
649 xFreeStackSpace = xPortGetFreeHeapSize();
\r
651 if( xFreeStackSpace > 100 )
\r
653 /* By now, the kernel has allocated everything it is going to, so
\r
654 if there is a lot of heap remaining unallocated then
\r
655 the value of configTOTAL_HEAP_SIZE in FreeRTOSConfig.h can be
\r
656 reduced accordingly. */
\r
659 /*-----------------------------------------------------------*/
\r
661 void vApplicationTickHook( void )
\r
663 /* Call the periodic timer test, which tests the timer API functions that
\r
664 can be called from an ISR. */
\r
665 vTimerPeriodicISRTests();
\r
667 /*-----------------------------------------------------------*/
\r