2 FreeRTOS V6.1.0 - Copyright (C) 2010 Real Time Engineers Ltd.
\r
4 ***************************************************************************
\r
8 * + New to FreeRTOS, *
\r
9 * + Wanting to learn FreeRTOS or multitasking in general quickly *
\r
10 * + Looking for basic training, *
\r
11 * + Wanting to improve your FreeRTOS skills and productivity *
\r
13 * then take a look at the FreeRTOS books - available as PDF or paperback *
\r
15 * "Using the FreeRTOS Real Time Kernel - a Practical Guide" *
\r
16 * http://www.FreeRTOS.org/Documentation *
\r
18 * A pdf reference manual is also available. Both are usually delivered *
\r
19 * to your inbox within 20 minutes to two hours when purchased between 8am *
\r
20 * and 8pm GMT (although please allow up to 24 hours in case of *
\r
21 * exceptional circumstances). Thank you for your support! *
\r
23 ***************************************************************************
\r
25 This file is part of the FreeRTOS distribution.
\r
27 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
28 the terms of the GNU General Public License (version 2) as published by the
\r
29 Free Software Foundation AND MODIFIED BY the FreeRTOS exception.
\r
30 ***NOTE*** The exception to the GPL is included to allow you to distribute
\r
31 a combined work that includes FreeRTOS without being obliged to provide the
\r
32 source code for proprietary components outside of the FreeRTOS kernel.
\r
33 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT
\r
34 ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
\r
35 FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
\r
36 more details. You should have received a copy of the GNU General Public
\r
37 License and the FreeRTOS license exception along with FreeRTOS; if not it
\r
38 can be viewed here: http://www.freertos.org/a00114.html and also obtained
\r
39 by writing to Richard Barry, contact details for whom are available on the
\r
44 http://www.FreeRTOS.org - Documentation, latest information, license and
\r
47 http://www.SafeRTOS.com - A version that is certified for use in safety
\r
50 http://www.OpenRTOS.com - Commercial support, development, porting,
\r
51 licensing and training services.
\r
55 * The documentation page for this demo available on http://www.FreeRTOS.org
\r
56 * documents the hardware configuration required to run this demo. It also
\r
57 * provides more information on the expected demo application behaviour.
\r
59 * main() creates all the demo application tasks, then starts the scheduler.
\r
60 * A lot of the created tasks are from the pool of "standard demo" tasks. The
\r
61 * web documentation provides more details of the standard demo application
\r
62 * tasks, which provide no particular functionality but do provide a good
\r
63 * example of how to use the FreeRTOS API.
\r
65 * In addition to the standard demo tasks, the following tasks, interrupts and
\r
66 * tests are defined and/or created within this file:
\r
68 * "LCD" task - The LCD task is a 'gatekeeper' task. It is the only task that
\r
69 * is permitted to access the LCD and therefore ensures access to the LCD is
\r
70 * always serialised and there are no mutual exclusion issues. When a task or
\r
71 * an interrupt wants to write to the LCD, it does not access the LCD directly
\r
72 * but instead sends the message to the LCD task. The LCD task then performs
\r
73 * the actual LCD output. This mechanism also allows interrupts to, in effect,
\r
74 * write to the LCD by sending messages to the LCD task.
\r
76 * The LCD task is also a demonstration of a controller task design pattern.
\r
77 * Some tasks do not actually send a string to the LCD task directly, but
\r
78 * instead send a command that is interpreted by the LCD task. In a normal
\r
79 * application these commands can be control values or set points, in this
\r
80 * simple example the commands just result in messages being displayed on the
\r
83 * "Button Poll" task - This task polls the state of the 'up' key on the
\r
84 * joystick input device. It uses the vTaskDelay() API function to control
\r
85 * the poll rate to ensure debouncing is not necessary and that the task does
\r
86 * not use all the available CPU processing time.
\r
88 * Button Interrupt and run time stats display - The select button on the
\r
89 * joystick input device is configured to generate an external interrupt. The
\r
90 * handler for this interrupt sends a message to LCD task, which interprets the
\r
91 * message to mean, firstly write a message to the LCD, and secondly, generate
\r
92 * a table of run time statistics. The run time statistics are displayed as a
\r
93 * table that contains information on how much processing time each task has
\r
94 * been allocated since the application started to execute. This information
\r
95 * is provided both as an absolute time, and as a percentage of the total run
\r
96 * time. The information is displayed in the terminal IO window of the IAR
\r
97 * embedded workbench. The online documentation for this demo shows a screen
\r
98 * shot demonstrating where the run time stats can be viewed.
\r
100 * Idle Hook - The idle hook is a function that is called on each iteration of
\r
101 * the idle task. In this case it is used to place the processor into a low
\r
102 * power mode. Note however that this application is implemented using standard
\r
103 * components, and is therefore not optimised for low power operation. Lower
\r
104 * power consumption would be achieved by converting polling tasks into event
\r
105 * driven tasks, and slowing the tick interrupt frequency.
\r
107 * "Check" function called from the tick hook - The tick hook is called during
\r
108 * each tick interrupt. It is called from an interrupt context so must execute
\r
109 * quickly, not attempt to block, and not call any FreeRTOS API functions that
\r
110 * do not end in "FromISR". In this case the tick hook executes a 'check'
\r
111 * function. This only executes every five seconds. Its main function is to
\r
112 * check that all the standard demo tasks are still operational. Each time it
\r
113 * executes it sends a status code to the LCD task. The LCD task interprets the
\r
114 * code and displays an appropriate message - which will be PASS if no tasks
\r
115 * have reported any errors, or a message stating which task has reported an
\r
119 /* Standard includes. */
\r
122 /* Kernel includes. */
\r
123 #include "FreeRTOS.h"
\r
127 /* Demo application includes. */
\r
128 #include "partest.h"
\r
130 #include "dynamic.h"
\r
131 #include "comtest2.h"
\r
132 #include "GenQTest.h"
\r
134 /* Eval board includes. */
\r
135 #include "stm32_eval.h"
\r
136 #include "stm32l152_eval_lcd.h"
\r
138 /* The priorities assigned to the tasks. */
\r
139 #define mainFLASH_TASK_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
140 #define mainLCD_TASK_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
141 #define mainCOM_TEST_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
142 #define mainGENERIC_QUEUE_TEST_PRIORITY ( tskIDLE_PRIORITY )
\r
144 /* The length of the queue (the number of items the queue can hold) that is used
\r
145 to send messages from tasks and interrupts the the LCD task. */
\r
146 #define mainQUEUE_LENGTH ( 5 )
\r
148 /* Codes sent within message to the LCD task so the LCD task can interrupt
\r
149 exactly what the message it just received was. These are sent in the
\r
150 cMessageID member of the message structure (defined below). */
\r
151 #define mainMESSAGE_BUTTON_UP ( 1 )
\r
152 #define mainMESSAGE_BUTTON_SEL ( 2 )
\r
153 #define mainMESSAGE_STATUS ( 3 )
\r
155 /* When cMessageID member of the message sent to the LCD task is
\r
156 mainMESSAGE_STATUS then these definitions are sent in the lMessageValue member
\r
157 of the same message to indicate what the status actually is. The value 1 is not
\r
158 used as this is globally defined as pdPASS, and indicates that no errors have
\r
159 been reported (the system is running as expected). */
\r
160 #define mainERROR_DYNAMIC_TASKS ( pdPASS + 1 )
\r
161 #define mainERROR_COM_TEST ( pdPASS + 2 )
\r
162 #define mainERROR_GEN_QUEUE_TEST ( pdPASS + 3 )
\r
164 /* Baud rate used by the comtest tasks. */
\r
165 #define mainCOM_TEST_BAUD_RATE ( 115200 )
\r
167 /* The LED used by the comtest tasks. See the comtest.c file for more
\r
169 #define mainCOM_TEST_LED ( 3 )
\r
171 /*-----------------------------------------------------------*/
\r
174 * System configuration is performed prior to main() being called, this function
\r
175 * configures the peripherals used by the demo application.
\r
177 static void prvSetupHardware( void );
\r
180 * Definition of the LCD/controller task described in the comments at the top
\r
183 static void prvLCDTask( void *pvParameters );
\r
186 * Definition of the button poll task described in the comments at the top of
\r
189 static void vButtonPollTask( void *pvParameters );
\r
192 * Converts a status message value into an appropriate string for display on
\r
193 * the LCD. The string is written to pcBuffer.
\r
195 static void prvGenerateStatusMessage( char *pcBuffer, long lStatusValue );
\r
197 /*-----------------------------------------------------------*/
\r
199 /* The time base for the run time stats is generated by the 16 bit timer 6.
\r
200 Each time the timer overflows ulTIM6_OverflowCount is incremented. Therefore,
\r
201 when converting the total run time to a 32 bit number, the most significant two
\r
202 bytes are given by ulTIM6_OverflowCount and the least significant two bytes are
\r
203 given by the current TIM6 counter value. Care must be taken with data
\r
204 consistency when combining the two in case a timer overflow occurs as the
\r
205 value is being read. */
\r
206 unsigned long ulTIM6_OverflowCount = 0UL;
\r
208 /* The handle of the queue used to send messages from tasks and interrupts to
\r
210 static xQueueHandle xLCDQueue = NULL;
\r
212 /* The definition of each message sent from tasks and interrupts to the LCD
\r
216 char cMessageID; /* << States what the message is. */
\r
217 long lMessageValue; /* << States the message value (can be an integer, string pointer, etc. depending on the value of cMessageID. */
\r
220 /*-----------------------------------------------------------*/
\r
224 /* Configure the peripherals used by this demo application. This includes
\r
225 configuring the joystick input select button to generate interrupts. */
\r
226 prvSetupHardware();
\r
228 /* Create the queue used by tasks and interrupts to send strings to the LCD
\r
230 xLCDQueue = xQueueCreate( mainQUEUE_LENGTH, sizeof( xQueueMessage ) );
\r
232 /* If the queue could not be created then don't create any tasks that might
\r
233 attempt to use the queue. */
\r
234 if( xLCDQueue != NULL )
\r
236 /* Add the created queue to the queue registry so it can be viewed in
\r
237 the IAR FreeRTOS state viewer plug-in. */
\r
238 vQueueAddToRegistry( xLCDQueue, "LCDQueue" );
\r
240 /* Create the LCD and button poll tasks, as described at the top of this
\r
242 xTaskCreate( prvLCDTask, ( signed char * ) "LCD", configMINIMAL_STACK_SIZE, NULL, mainLCD_TASK_PRIORITY, NULL );
\r
243 xTaskCreate( vButtonPollTask, ( signed char * ) "Temp", configMINIMAL_STACK_SIZE, NULL, tskIDLE_PRIORITY, NULL );
\r
245 /* Create a subset of the standard demo tasks. */
\r
246 vStartDynamicPriorityTasks();
\r
247 vStartLEDFlashTasks( mainFLASH_TASK_PRIORITY );
\r
248 vAltStartComTestTasks( mainCOM_TEST_PRIORITY, mainCOM_TEST_BAUD_RATE, mainCOM_TEST_LED );
\r
249 vStartGenericQueueTasks( mainGENERIC_QUEUE_TEST_PRIORITY );
\r
251 /* Start the scheduler. */
\r
252 vTaskStartScheduler();
\r
255 /* If all is well then this line will never be reached. If it is reached
\r
256 then it is likely that there was insufficient (FreeRTOS) heap memory space
\r
257 to create the idle task. This may have been trapped by the malloc() failed
\r
258 hook function, if one is configured. */
\r
261 /*-----------------------------------------------------------*/
\r
263 static void prvLCDTask( void *pvParameters )
\r
265 xQueueMessage xReceivedMessage;
\r
266 long lLine = Line1;
\r
267 const long lFontHeight = (((sFONT *)LCD_GetFont())->Height);
\r
269 /* Buffer into which strings are formatted and placed ready for display on the
\r
270 LCD. Note this is a static variable to prevent it being allocated on the task
\r
271 stack, which is too small to hold such a variable. The stack size is configured
\r
272 when the task is created. */
\r
273 static char cBuffer[ 512 ];
\r
275 /* This function is the only function that uses printf(). If printf() is
\r
276 used from any other function then some sort of mutual exclusion on stdout
\r
279 This is also the only function that is permitted to access the LCD.
\r
281 First print out the number of bytes that remain in the FreeRTOS heap. This
\r
282 can be viewed in the terminal IO window within the IAR Embedded Workbench. */
\r
283 printf( "%d bytes of heap space remain unallocated\n", xPortGetFreeHeapSize() );
\r
287 /* Wait for a message to be received. This will wait indefinitely if
\r
288 INCLUDE_vTaskSuspend is set to 1 in FreeRTOSConfig.h, therefore there
\r
289 is no need to check the function return value. */
\r
290 xQueueReceive( xLCDQueue, &xReceivedMessage, portMAX_DELAY );
\r
292 /* Clear the LCD if the last LCD message was output to the last
\r
293 available line on the LCD. */
\r
294 if( lLine > Line9 )
\r
300 /* What is this message? What does it contain? */
\r
301 switch( xReceivedMessage.cMessageID )
\r
303 case mainMESSAGE_BUTTON_UP : /* The button poll task has just
\r
304 informed this task that the up
\r
305 button on the joystick input has
\r
306 been pressed or released. */
\r
307 sprintf( cBuffer, "Button up = %d", xReceivedMessage.lMessageValue );
\r
310 case mainMESSAGE_BUTTON_SEL : /* The select button interrupt
\r
311 just informed this task that the
\r
312 select button was pressed.
\r
313 Generate a table of task run time
\r
314 statistics and output this to
\r
315 the terminal IO window in the IAR
\r
316 embedded workbench. */
\r
317 printf( "\nTask\t Abs Time\t %%Time\n*****************************************" );
\r
318 vTaskGetRunTimeStats( ( signed char * ) cBuffer );
\r
321 /* Also print out a message to
\r
322 the LCD - in this case the
\r
323 pointer to the string to print
\r
324 is sent directly in the
\r
325 lMessageValue member of the
\r
326 message. This just demonstrates
\r
327 a different communication
\r
329 sprintf( cBuffer, "%s", ( char * ) xReceivedMessage.lMessageValue );
\r
332 case mainMESSAGE_STATUS : /* The tick interrupt hook
\r
333 function has just informed this
\r
334 task of the system status.
\r
335 Generate a string in accordance
\r
336 with the status value. */
\r
337 prvGenerateStatusMessage( cBuffer, xReceivedMessage.lMessageValue );
\r
340 default : sprintf( cBuffer, "Unknown message" );
\r
344 /* Output the message that was placed into the cBuffer array within the
\r
345 switch statement above. */
\r
346 LCD_DisplayStringLine( lLine, ( uint8_t * ) cBuffer );
\r
348 /* Move onto the next LCD line, ready for the next iteration of this
\r
350 lLine += lFontHeight;
\r
353 /*-----------------------------------------------------------*/
\r
355 static void prvGenerateStatusMessage( char *pcBuffer, long lStatusValue )
\r
357 /* Just a utility function to convert a status value into a meaningful
\r
358 string for output onto the LCD. */
\r
359 switch( lStatusValue )
\r
361 case pdPASS : sprintf( pcBuffer, "Task status = PASS" );
\r
363 case mainERROR_DYNAMIC_TASKS : sprintf( pcBuffer, "Error: Dynamic tasks" );
\r
365 case mainERROR_COM_TEST : sprintf( pcBuffer, "Err: loop connected?" ); /* Error in COM test - is the Loopback connector connected? */
\r
367 case mainERROR_GEN_QUEUE_TEST : sprintf( pcBuffer, "Error: Gen Q test" );
\r
369 default : sprintf( pcBuffer, "Unknown status" );
\r
373 /*-----------------------------------------------------------*/
\r
375 void EXTI9_5_IRQHandler( void )
\r
377 /* Define the message sent to the LCD task from this interrupt. */
\r
378 const xQueueMessage xMessage = { mainMESSAGE_BUTTON_SEL, ( unsigned long ) "Select Interrupt!" };
\r
379 long lHigherPriorityTaskWoken = pdFALSE;
\r
381 /* This is the interrupt handler for the joystick select button input.
\r
382 The button has been pushed, write a message to the LCD via the LCD task. */
\r
383 xQueueSendFromISR( xLCDQueue, &xMessage, &lHigherPriorityTaskWoken );
\r
385 EXTI_ClearITPendingBit( SEL_BUTTON_EXTI_LINE );
\r
387 /* If writing to xLCDQueue caused a task to unblock, and the unblocked task
\r
388 has a priority equal to or above the task that this interrupt interrupted,
\r
389 then lHigherPriorityTaskWoken will have been set to pdTRUE internally within
\r
390 xQueuesendFromISR(), and portEND_SWITCHING_ISR() will ensure that this
\r
391 interrupt returns directly to the higher priority unblocked task. */
\r
392 portEND_SWITCHING_ISR( lHigherPriorityTaskWoken );
\r
394 /*-----------------------------------------------------------*/
\r
396 void vApplicationTickHook( void )
\r
398 static unsigned long ulCounter = 0;
\r
399 static const unsigned long ulCheckFrequency = 5000UL / portTICK_RATE_MS;
\r
400 long lHigherPriorityTaskWoken = pdFALSE;
\r
402 /* Define the status message that is sent to the LCD task. By default the
\r
404 static xQueueMessage xStatusMessage = { mainMESSAGE_STATUS, pdPASS };
\r
406 /* This is called from within the tick interrupt and performs the 'check'
\r
407 functionality as described in the comments at the top of this file.
\r
409 Is it time to perform the 'check' functionality again? */
\r
411 if( ulCounter >= ulCheckFrequency )
\r
413 /* See if the standard demo tasks are executing as expected, changing
\r
414 the message that is sent to the LCD task from PASS to an error code if
\r
415 any tasks set reports an error. */
\r
416 if( xAreDynamicPriorityTasksStillRunning() != pdPASS )
\r
418 xStatusMessage.lMessageValue = mainERROR_DYNAMIC_TASKS;
\r
421 if( xAreComTestTasksStillRunning() != pdPASS )
\r
423 xStatusMessage.lMessageValue = mainERROR_COM_TEST;
\r
426 if( xAreGenericQueueTasksStillRunning() != pdPASS )
\r
428 xStatusMessage.lMessageValue = mainERROR_GEN_QUEUE_TEST;
\r
431 /* As this is the tick hook the lHigherPriorityTaskWoken parameter is not
\r
432 needed (a context switch is going to be performed anyway), but it must
\r
433 still be provided. */
\r
434 xQueueSendFromISR( xLCDQueue, &xStatusMessage, &lHigherPriorityTaskWoken );
\r
438 /*-----------------------------------------------------------*/
\r
440 static void vButtonPollTask( void *pvParameters )
\r
442 long lLastState = pdTRUE;
\r
444 xQueueMessage xMessage;
\r
446 /* This tasks performs the button polling functionality as described at the
\r
447 top of this file. */
\r
450 /* Check the button state. */
\r
451 lState = STM_EVAL_PBGetState( BUTTON_UP );
\r
452 if( lState != lLastState )
\r
454 /* The state has changed, send a message to the LCD task. */
\r
455 xMessage.cMessageID = mainMESSAGE_BUTTON_UP;
\r
456 xMessage.lMessageValue = lState;
\r
457 lLastState = lState;
\r
458 xQueueSend( xLCDQueue, &xMessage, portMAX_DELAY );
\r
461 /* Block for 10 milliseconds so this task does not utilise all the CPU
\r
462 time and debouncing of the button is not necessary. */
\r
463 vTaskDelay( 10 / portTICK_RATE_MS );
\r
466 /*-----------------------------------------------------------*/
\r
468 static void prvSetupHardware( void )
\r
470 /* Ensure that all 4 interrupt priority bits are used as the pre-emption
\r
472 NVIC_PriorityGroupConfig( NVIC_PriorityGroup_4 );
\r
474 /* Initialise the LEDs. */
\r
475 vParTestInitialise();
\r
477 /* Initialise the joystick inputs. */
\r
478 STM_EVAL_PBInit( BUTTON_UP, BUTTON_MODE_GPIO );
\r
479 STM_EVAL_PBInit( BUTTON_DOWN, BUTTON_MODE_GPIO );
\r
480 STM_EVAL_PBInit( BUTTON_LEFT, BUTTON_MODE_GPIO );
\r
481 STM_EVAL_PBInit( BUTTON_RIGHT, BUTTON_MODE_GPIO );
\r
483 /* The select button in the middle of the joystick is configured to generate
\r
484 an interrupt. The Eval board library will configure the interrupt
\r
485 priority to be the lowest priority available so the priority need not be
\r
486 set here explicitly. It is important that the priority is equal to or
\r
487 below that set by the configMAX_SYSCALL_INTERRUPT_PRIORITY value set in
\r
488 FreeRTOSConfig.h. */
\r
489 STM_EVAL_PBInit( BUTTON_SEL, BUTTON_MODE_EXTI );
\r
491 /* Initialize the LCD */
\r
492 STM32L152_LCD_Init();
\r
494 LCD_SetBackColor( Blue );
\r
495 LCD_SetTextColor( White );
\r
496 LCD_DisplayStringLine( Line0, " www.FreeRTOS.org" );
\r
498 /*-----------------------------------------------------------*/
\r
500 void vConfigureTimerForRunTimeStats( void )
\r
502 TIM_TimeBaseInitTypeDef TIM_TimeBaseStructure;
\r
503 NVIC_InitTypeDef NVIC_InitStructure;
\r
505 /* The time base for the run time stats is generated by the 16 bit timer 6.
\r
506 Each time the timer overflows ulTIM6_OverflowCount is incremented.
\r
507 Therefore, when converting the total run time to a 32 bit number, the most
\r
508 significant two bytes are given by ulTIM6_OverflowCount and the least
\r
509 significant two bytes are given by the current TIM6 counter value. Care
\r
510 must be taken with data consistency when combining the two in case a timer
\r
511 overflow occurs as the value is being read.
\r
513 The portCONFIGURE_TIMER_FOR_RUN_TIME_STATS() macro (in FreeRTOSConfig.h) is
\r
514 defined to call this function, so the kernel will call this function
\r
515 automatically at the appropriate time. */
\r
517 /* TIM6 clock enable */
\r
518 RCC_APB1PeriphClockCmd(RCC_APB1Periph_TIM6, ENABLE);
\r
520 /* The 32MHz clock divided by 5000 should tick (very) approximately every
\r
521 150uS and overflow a 16bit timer (very) approximately every 10 seconds. */
\r
522 TIM_TimeBaseStructure.TIM_Period = 65535;
\r
523 TIM_TimeBaseStructure.TIM_Prescaler = 5000;
\r
524 TIM_TimeBaseStructure.TIM_ClockDivision = TIM_CKD_DIV1;
\r
525 TIM_TimeBaseStructure.TIM_CounterMode = TIM_CounterMode_Up;
\r
527 TIM_TimeBaseInit( TIM6, &TIM_TimeBaseStructure );
\r
529 /* Only interrupt on overflow events. */
\r
530 TIM6->CR1 |= TIM_CR1_URS;
\r
532 /* Enable the interrupt. */
\r
533 TIM_ITConfig( TIM6, TIM_IT_Update, ENABLE );
\r
535 /* Enable the TIM6 global Interrupt */
\r
536 NVIC_InitStructure.NVIC_IRQChannel = TIM6_IRQn;
\r
537 NVIC_InitStructure.NVIC_IRQChannelPreemptionPriority = configLIBRARY_LOWEST_INTERRUPT_PRIORITY;
\r
538 NVIC_InitStructure.NVIC_IRQChannelSubPriority = 0x00; /* Not used as 4 bits are used for the pre-emption priority. */
\r
539 NVIC_InitStructure.NVIC_IRQChannelCmd = ENABLE;
\r
540 NVIC_Init(&NVIC_InitStructure);
\r
542 TIM_ClearITPendingBit( TIM6, TIM_IT_Update );
\r
543 TIM_Cmd( TIM6, ENABLE );
\r
545 /*-----------------------------------------------------------*/
\r
547 void TIM6_IRQHandler( void )
\r
549 /* Interrupt handler for TIM 6
\r
551 The time base for the run time stats is generated by the 16 bit timer 6.
\r
552 Each time the timer overflows ulTIM6_OverflowCount is incremented.
\r
553 Therefore, when converting the total run time to a 32 bit number, the most
\r
554 significant two bytes are given by ulTIM6_OverflowCount and the least
\r
555 significant two bytes are given by the current TIM6 counter value. Care
\r
556 must be taken with data consistency when combining the two in case a timer
\r
557 overflow occurs as the value is being read. */
\r
558 if( TIM_GetITStatus( TIM6, TIM_IT_Update) != RESET)
\r
560 ulTIM6_OverflowCount++;
\r
561 TIM_ClearITPendingBit( TIM6, TIM_IT_Update );
\r
564 /*-----------------------------------------------------------*/
\r
566 void vApplicationStackOverflowHook( xTaskHandle *pxTask, signed char *pcTaskName )
\r
568 ( void ) pcTaskName;
\r
571 /* Run time stack overflow checking is performed if
\r
572 configconfigCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
573 function is called if a stack overflow is detected. */
\r
576 /*-----------------------------------------------------------*/
\r
578 void vApplicationMallocFailedHook( void )
\r
580 /* Called if a call to pvPortMalloc() fails because there is insufficient
\r
581 free memory available in the FreeRTOS heap. pvPortMalloc() is called
\r
582 internally by FreeRTOS API functions that create tasks, queues or
\r
586 /*-----------------------------------------------------------*/
\r
588 void vApplicationIdleHook( void )
\r
590 /* Called on each itteration of the idle task. In this case the idle task
\r
591 just enters a low(ish) power mode. */
\r
592 PWR_EnterSleepMode( PWR_Regulator_ON, PWR_SLEEPEntry_WFI );
\r
projects / freertos / blob