2 FreeRTOS V8.2.0rc1 - Copyright (C) 2014 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 >>! NOTE: The modification to the GPL is included to allow you to !<<
\r
14 >>! distribute a combined work that includes FreeRTOS without being !<<
\r
15 >>! obliged to provide the source code for proprietary components !<<
\r
16 >>! outside of the FreeRTOS kernel. !<<
\r
18 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
19 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
20 FOR A PARTICULAR PURPOSE. Full license text is available on the following
\r
21 link: http://www.freertos.org/a00114.html
\r
25 ***************************************************************************
\r
27 * Having a problem? Start by reading the FAQ "My application does *
\r
28 * not run, what could be wrong?". Have you defined configASSERT()? *
\r
30 * http://www.FreeRTOS.org/FAQHelp.html *
\r
32 ***************************************************************************
\r
34 ***************************************************************************
\r
36 * FreeRTOS provides completely free yet professionally developed, *
\r
37 * robust, strictly quality controlled, supported, and cross *
\r
38 * platform software that is more than just the market leader, it *
\r
39 * is the industry's de facto standard. *
\r
41 * Help yourself get started quickly while simultaneously helping *
\r
42 * to support the FreeRTOS project by purchasing a FreeRTOS *
\r
43 * tutorial book, reference manual, or both: *
\r
44 * http://www.FreeRTOS.org/Documentation *
\r
46 ***************************************************************************
\r
48 ***************************************************************************
\r
50 * Investing in training allows your team to be as productive as *
\r
51 * possible as early as possible, lowering your overall development *
\r
52 * cost, and enabling you to bring a more robust product to market *
\r
53 * earlier than would otherwise be possible. Richard Barry is both *
\r
54 * the architect and key author of FreeRTOS, and so also the world's *
\r
55 * leading authority on what is the world's most popular real time *
\r
56 * kernel for deeply embedded MCU designs. Obtaining your training *
\r
57 * from Richard ensures your team will gain directly from his in-depth *
\r
58 * product knowledge and years of usage experience. Contact Real Time *
\r
59 * Engineers Ltd to enquire about the FreeRTOS Masterclass, presented *
\r
60 * by Richard Barry: http://www.FreeRTOS.org/contact
\r
62 ***************************************************************************
\r
64 ***************************************************************************
\r
66 * You are receiving this top quality software for free. Please play *
\r
67 * fair and reciprocate by reporting any suspected issues and *
\r
68 * participating in the community forum: *
\r
69 * http://www.FreeRTOS.org/support *
\r
73 ***************************************************************************
\r
75 http://www.FreeRTOS.org - Documentation, books, training, latest versions,
\r
76 license and Real Time Engineers Ltd. contact details.
\r
78 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
79 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
80 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
82 http://www.FreeRTOS.org/labs - Where new FreeRTOS products go to incubate.
\r
83 Come and try FreeRTOS+TCP, our new open source TCP/IP stack for FreeRTOS.
\r
85 http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High
\r
86 Integrity Systems ltd. to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
87 licenses offer ticketed support, indemnification and commercial middleware.
\r
89 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
90 engineered and independently SIL3 certified version for use in safety and
\r
91 mission critical applications that require provable dependability.
\r
97 * main-blinky.c is included when the "Blinky" build configuration is used.
\r
98 * main-full.c is included when the "Full" build configuration is used.
\r
100 * main-blinky.c (this file) defines a very simple demo that creates two tasks,
\r
101 * one queue, and one timer. It also demonstrates how Cortex-M3 interrupts can
\r
102 * interact with FreeRTOS tasks/timers.
\r
104 * This simple demo project runs on the SK-FM3-100PMC evaluation board, which
\r
105 * is populated with an MB9B500 microcontroller.
\r
107 * The idle hook function:
\r
108 * The idle hook function demonstrates how to query the amount of FreeRTOS heap
\r
109 * space that is remaining (see vApplicationIdleHook() defined in this file).
\r
111 * The main() Function:
\r
112 * main() creates one software timer, one queue, and two tasks. It then starts
\r
115 * The Queue Send Task:
\r
116 * The queue send task is implemented by the prvQueueSendTask() function in
\r
117 * this file. prvQueueSendTask() sits in a loop that causes it to repeatedly
\r
118 * block for 200 milliseconds, before sending the value 100 to the queue that
\r
119 * was created within main(). Once the value is sent, the task loops back
\r
120 * around to block for another 200 milliseconds.
\r
122 * The Queue Receive Task:
\r
123 * The queue receive task is implemented by the prvQueueReceiveTask() function
\r
124 * in this file. prvQueueReceiveTask() sits in a loop that causes it to
\r
125 * repeatedly attempt to read data from the queue that was created within
\r
126 * main(). When data is received, the task checks the value of the data, and
\r
127 * if the value equals the expected 100, toggles an LED on the 7 segment
\r
128 * display. The 'block time' parameter passed to the queue receive function
\r
129 * specifies that the task should be held in the Blocked state indefinitely to
\r
130 * wait for data to be available on the queue. The queue receive task will only
\r
131 * leave the Blocked state when the queue send task writes to the queue. As the
\r
132 * queue send task writes to the queue every 200 milliseconds, the queue receive
\r
133 * task leaves the Blocked state every 200 milliseconds, and therefore toggles
\r
134 * the LED every 200 milliseconds.
\r
136 * The LED Software Timer and the Button Interrupt:
\r
137 * The user button SW2 is configured to generate an interrupt each time it is
\r
138 * pressed. The interrupt service routine switches an LED in the 7 segment
\r
139 * display on, and resets the LED software timer. The LED timer has a 5000
\r
140 * millisecond (5 second) period, and uses a callback function that is defined
\r
141 * to just turn the LED off again. Therefore, pressing the user button will
\r
142 * turn the LED on, and the LED will remain on until a full five seconds pass
\r
143 * without the button being pressed.
\r
146 /* Kernel includes. */
\r
147 #include "FreeRTOS.h"
\r
150 #include "timers.h"
\r
152 /* Fujitsu drivers/libraries. */
\r
153 #include "mb9bf506n.h"
\r
154 #include "system_mb9bf50x.h"
\r
156 /* Priorities at which the tasks are created. */
\r
157 #define mainQUEUE_RECEIVE_TASK_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
158 #define mainQUEUE_SEND_TASK_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
160 /* The rate at which data is sent to the queue, specified in milliseconds, and
\r
161 converted to ticks using the portTICK_PERIOD_MS constant. */
\r
162 #define mainQUEUE_SEND_FREQUENCY_MS ( 200 / portTICK_PERIOD_MS )
\r
164 /* The number of items the queue can hold. This is 1 as the receive task
\r
165 will remove items as they are added, meaning the send task should always find
\r
166 the queue empty. */
\r
167 #define mainQUEUE_LENGTH ( 1 )
\r
169 /* The LED toggle by the queue receive task. */
\r
170 #define mainTASK_CONTROLLED_LED 0x8000UL
\r
172 /* The LED turned on by the button interrupt, and turned off by the LED timer. */
\r
173 #define mainTIMER_CONTROLLED_LED 0x8000UL
\r
175 /*-----------------------------------------------------------*/
\r
178 * Setup the NVIC, LED outputs, and button inputs.
\r
180 static void prvSetupHardware( void );
\r
183 * The tasks as described in the comments at the top of this file.
\r
185 static void prvQueueReceiveTask( void *pvParameters );
\r
186 static void prvQueueSendTask( void *pvParameters );
\r
189 * The LED timer callback function. This does nothing but switch off the
\r
190 * LED defined by the mainTIMER_CONTROLLED_LED constant.
\r
192 static void vLEDTimerCallback( TimerHandle_t xTimer );
\r
194 /*-----------------------------------------------------------*/
\r
196 /* The queue used by both tasks. */
\r
197 static QueueHandle_t xQueue = NULL;
\r
199 /* The LED software timer. This uses vLEDTimerCallback() as its callback
\r
201 static TimerHandle_t xLEDTimer = NULL;
\r
203 /*-----------------------------------------------------------*/
\r
207 /* Configure the NVIC, LED outputs and button inputs. */
\r
208 prvSetupHardware();
\r
210 /* Create the queue. */
\r
211 xQueue = xQueueCreate( mainQUEUE_LENGTH, sizeof( unsigned long ) );
\r
213 if( xQueue != NULL )
\r
215 /* Start the two tasks as described in the comments at the top of this
\r
217 xTaskCreate( prvQueueReceiveTask, "Rx", configMINIMAL_STACK_SIZE, NULL, mainQUEUE_RECEIVE_TASK_PRIORITY, NULL );
\r
218 xTaskCreate( prvQueueSendTask, "TX", configMINIMAL_STACK_SIZE, NULL, mainQUEUE_SEND_TASK_PRIORITY, NULL );
\r
220 /* Create the software timer that is responsible for turning off the LED
\r
221 if the button is not pushed within 5000ms, as described at the top of
\r
223 xLEDTimer = xTimerCreate( "LEDTimer", /* A text name, purely to help debugging. */
\r
224 ( 5000 / portTICK_PERIOD_MS ),/* The timer period, in this case 5000ms (5s). */
\r
225 pdFALSE, /* This is a one shot timer, so xAutoReload is set to pdFALSE. */
\r
226 ( void * ) 0, /* The ID is not used, so can be set to anything. */
\r
227 vLEDTimerCallback /* The callback function that switches the LED off. */
\r
230 /* Start the tasks and timer running. */
\r
231 vTaskStartScheduler();
\r
234 /* If all is well, the scheduler will now be running, and the following line
\r
235 will never be reached. If the following line does execute, then there was
\r
236 insufficient FreeRTOS heap memory available for the idle and/or timer tasks
\r
237 to be created. See the memory management section on the FreeRTOS web site
\r
238 for more details. */
\r
241 /*-----------------------------------------------------------*/
\r
243 static void vLEDTimerCallback( TimerHandle_t xTimer )
\r
245 /* The timer has expired - so no button pushes have occurred in the last
\r
246 five seconds - turn the LED off. NOTE - accessing the LED port should use
\r
247 a critical section because it is accessed from multiple tasks, and the
\r
248 button interrupt - in this trivial case, for simplicity, the critical
\r
249 section is omitted. */
\r
250 FM3_GPIO->PDOR1 |= mainTIMER_CONTROLLED_LED;
\r
252 /*-----------------------------------------------------------*/
\r
254 /* The ISR executed when the user button is pushed. */
\r
255 void INT0_7_Handler( void )
\r
257 portBASE_TYPE xHigherPriorityTaskWoken = pdFALSE;
\r
259 /* The button was pushed, so ensure the LED is on before resetting the
\r
260 LED timer. The LED timer will turn the LED off if the button is not
\r
261 pushed within 5000ms. */
\r
262 FM3_GPIO->PDOR1 &= ~mainTIMER_CONTROLLED_LED;
\r
264 /* This interrupt safe FreeRTOS function can be called from this interrupt
\r
265 because the interrupt priority is below the
\r
266 configMAX_SYSCALL_INTERRUPT_PRIORITY setting in FreeRTOSConfig.h. */
\r
267 xTimerResetFromISR( xLEDTimer, &xHigherPriorityTaskWoken );
\r
269 /* Clear the interrupt before leaving. This just clears all the interrupts
\r
270 for simplicity, as only one is actually used in this simple demo anyway. */
\r
271 FM3_EXTI->EICL = 0x0000;
\r
273 /* If calling xTimerResetFromISR() caused a task (in this case the timer
\r
274 service/daemon task) to unblock, and the unblocked task has a priority
\r
275 higher than or equal to the task that was interrupted, then
\r
276 xHigherPriorityTaskWoken will now be set to pdTRUE, and calling
\r
277 portEND_SWITCHING_ISR() will ensure the unblocked task runs next. */
\r
278 portEND_SWITCHING_ISR( xHigherPriorityTaskWoken );
\r
280 /*-----------------------------------------------------------*/
\r
282 static void prvQueueSendTask( void *pvParameters )
\r
284 TickType_t xNextWakeTime;
\r
285 const unsigned long ulValueToSend = 100UL;
\r
287 /* Initialise xNextWakeTime - this only needs to be done once. */
\r
288 xNextWakeTime = xTaskGetTickCount();
\r
292 /* Place this task in the blocked state until it is time to run again.
\r
293 The block time is specified in ticks, the constant used converts ticks
\r
294 to ms. While in the Blocked state this task will not consume any CPU
\r
296 vTaskDelayUntil( &xNextWakeTime, mainQUEUE_SEND_FREQUENCY_MS );
\r
298 /* Send to the queue - causing the queue receive task to unblock and
\r
299 toggle an LED. 0 is used as the block time so the sending operation
\r
300 will not block - it shouldn't need to block as the queue should always
\r
301 be empty at this point in the code. */
\r
302 xQueueSend( xQueue, &ulValueToSend, 0 );
\r
305 /*-----------------------------------------------------------*/
\r
307 static void prvQueueReceiveTask( void *pvParameters )
\r
309 unsigned long ulReceivedValue;
\r
313 /* Wait until something arrives in the queue - this task will block
\r
314 indefinitely provided INCLUDE_vTaskSuspend is set to 1 in
\r
315 FreeRTOSConfig.h. */
\r
316 xQueueReceive( xQueue, &ulReceivedValue, portMAX_DELAY );
\r
318 /* To get here something must have been received from the queue, but
\r
319 is it the expected value? If it is, toggle the LED. */
\r
320 if( ulReceivedValue == 100UL )
\r
322 /* NOTE - accessing the LED port should use a critical section
\r
323 because it is accessed from multiple tasks, and the button interrupt
\r
324 - in this trivial case, for simplicity, the critical section is
\r
326 if( ( FM3_GPIO->PDOR3 & mainTASK_CONTROLLED_LED ) != 0 )
\r
328 FM3_GPIO->PDOR3 &= ~mainTASK_CONTROLLED_LED;
\r
332 FM3_GPIO->PDOR3 |= mainTASK_CONTROLLED_LED;
\r
337 /*-----------------------------------------------------------*/
\r
339 static void prvSetupHardware( void )
\r
341 const unsigned short usButtonInputBit = 0x01U;
\r
342 const unsigned short usGPIOState = 0xFF00U;
\r
345 SystemCoreClockUpdate();
\r
347 /* Analog inputs are not used on the LED outputs. */
\r
348 FM3_GPIO->ADE = 0x00FF;
\r
350 /* LED seg1 to GPIO output (P18->P1F). */
\r
351 FM3_GPIO->DDR1 = 0xFF00;
\r
352 FM3_GPIO->PFR1 = 0x0000;
\r
354 /* LED seg2 to GPIO output (P30->P3F). */
\r
355 FM3_GPIO->DDR3 = 0xFF00;
\r
356 FM3_GPIO->PFR3 = 0x0000;
\r
358 /* Start with all LEDs off. */
\r
359 FM3_GPIO->PDOR3 = usGPIOState;
\r
360 FM3_GPIO->PDOR1 = usGPIOState;
\r
362 /* Set the switches to input (P18->P1F). */
\r
363 FM3_GPIO->DDR5 = 0x0000;
\r
364 FM3_GPIO->PFR5 = 0x0000;
\r
366 /* Assign the button input as GPIO. */
\r
367 FM3_GPIO->PFR1 |= usButtonInputBit;
\r
369 /* Button interrupt on falling edge. */
\r
370 FM3_EXTI->ELVR = 0x0003;
\r
372 /* Clear all external interrupts. */
\r
373 FM3_EXTI->EICL = 0x0000;
\r
375 /* Enable the button interrupt. */
\r
376 FM3_EXTI->ENIR |= usButtonInputBit;
\r
378 /* Setup the GPIO and the NVIC for the switch used in this simple demo. */
\r
379 NVIC_SetPriority( EXINT0_7_IRQn, configLIBRARY_MAX_SYSCALL_INTERRUPT_PRIORITY );
\r
380 NVIC_EnableIRQ( EXINT0_7_IRQn );
\r
382 /*-----------------------------------------------------------*/
\r
384 void vApplicationMallocFailedHook( void )
\r
386 /* Called if a call to pvPortMalloc() fails because there is insufficient
\r
387 free memory available in the FreeRTOS heap. pvPortMalloc() is called
\r
388 internally by FreeRTOS API functions that create tasks, queues, software
\r
389 timers, and semaphores. The size of the FreeRTOS heap is set by the
\r
390 configTOTAL_HEAP_SIZE configuration constant in FreeRTOSConfig.h. */
\r
393 /*-----------------------------------------------------------*/
\r
395 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
397 ( void ) pcTaskName;
\r
400 /* Run time stack overflow checking is performed if
\r
401 configconfigCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
402 function is called if a stack overflow is detected. */
\r
405 /*-----------------------------------------------------------*/
\r
407 void vApplicationTickHook( void )
\r
409 /* A tick hook is used by the "Full" build configuration. The Full and
\r
410 blinky build configurations share a FreeRTOSConfig.h header file, so this
\r
411 simple build configuration also has to define a tick hook - even though it
\r
412 does not actually use it for anything. */
\r
414 /*-----------------------------------------------------------*/
\r
416 void vApplicationIdleHook( void )
\r
418 volatile size_t xFreeHeapSpace;
\r
420 /* This function is called on each cycle of the idle task. In this case it
\r
421 does nothing useful, other than report the amount of FreeRTOS heap that
\r
422 remains unallocated. */
\r
423 xFreeHeapSpace = xPortGetFreeHeapSize();
\r
425 if( xFreeHeapSpace > 100 )
\r
427 /* By now, the kernel has allocated everything it is going to, so
\r
428 if there is a lot of heap remaining unallocated then
\r
429 the value of configTOTAL_HEAP_SIZE in FreeRTOSConfig.h can be
\r
430 reduced accordingly. */
\r
433 /*-----------------------------------------------------------*/
\r