2 FreeRTOS V7.0.1 - Copyright (C) 2011 Real Time Engineers Ltd.
\r
5 ***************************************************************************
\r
7 * FreeRTOS tutorial books are available in pdf and paperback. *
\r
8 * Complete, revised, and edited pdf reference manuals are also *
\r
11 * Purchasing FreeRTOS documentation will not only help you, by *
\r
12 * ensuring you get running as quickly as possible and with an *
\r
13 * in-depth knowledge of how to use FreeRTOS, it will also help *
\r
14 * the FreeRTOS project to continue with its mission of providing *
\r
15 * professional grade, cross platform, de facto standard solutions *
\r
16 * for microcontrollers - completely free of charge! *
\r
18 * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *
\r
20 * Thank you for using FreeRTOS, and thank you for your support! *
\r
22 ***************************************************************************
\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 modification to the GPL is included to allow you to
\r
31 distribute a combined work that includes FreeRTOS without being obliged to
\r
32 provide the source code for proprietary components outside of the FreeRTOS
\r
33 kernel. FreeRTOS is distributed in the hope that it will be useful, but
\r
34 WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
\r
35 or 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 tasks, which
\r
62 * provide no particular functionality but do provide good examples of how to
\r
63 * 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
118 * "Reg test" tasks - These fill the registers with known values, then check
\r
119 * that each register still contains its expected value. Each task uses
\r
120 * different values. The tasks run with very low priority so get preempted
\r
121 * very frequently. A check variable is incremented on each iteration of the
\r
122 * test loop. A register containing an unexpected value is indicative of an
\r
123 * error in the context switching mechanism and will result in a branch to a
\r
124 * null loop - which in turn will prevent the check variable from incrementing
\r
125 * any further and allow the check task (described a above) to determine that an
\r
126 * error has occurred. The nature of the reg test tasks necessitates that they
\r
127 * are written in assembly code.
\r
129 * *NOTE 1* vApplicationSetupTimerInterrupt() is called by the kernel to let
\r
130 * the application set up a timer to generate the tick interrupt. In this
\r
131 * example a timer A0 is used for this purpose.
\r
135 /* Standard includes. */
\r
138 /* FreeRTOS includes. */
\r
139 #include "FreeRTOS.h"
\r
143 /* Hardware includes. */
\r
144 #include "msp430.h"
\r
145 #include "hal_MSP-EXP430F5438.h"
\r
147 /* Standard demo includes. */
\r
148 #include "ParTest.h"
\r
149 #include "dynamic.h"
\r
150 #include "comtest2.h"
\r
151 #include "GenQTest.h"
\r
153 /* Codes sent within messages to the LCD task so the LCD task can interpret
\r
154 exactly what the message it just received was. These are sent in the
\r
155 cMessageID member of the message structure (defined below). */
\r
156 #define mainMESSAGE_BUTTON_UP ( 1 )
\r
157 #define mainMESSAGE_BUTTON_SEL ( 2 )
\r
158 #define mainMESSAGE_STATUS ( 3 )
\r
160 /* When the cMessageID member of the message sent to the LCD task is
\r
161 mainMESSAGE_STATUS then these definitions are sent in the ulMessageValue member
\r
162 of the same message and indicate what the status actually is. */
\r
163 #define mainERROR_DYNAMIC_TASKS ( pdPASS + 1 )
\r
164 #define mainERROR_COM_TEST ( pdPASS + 2 )
\r
165 #define mainERROR_GEN_QUEUE_TEST ( pdPASS + 3 )
\r
166 #define mainERROR_REG_TEST ( pdPASS + 4 )
\r
168 /* The length of the queue (the number of items the queue can hold) that is used
\r
169 to send messages from tasks and interrupts the the LCD task. */
\r
170 #define mainQUEUE_LENGTH ( 5 )
\r
172 /* Priorities used by the test and demo tasks. */
\r
173 #define mainLCD_TASK_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
174 #define mainCOM_TEST_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
175 #define mainGENERIC_QUEUE_TEST_PRIORITY ( tskIDLE_PRIORITY )
\r
177 /* The LED used by the comtest tasks. See the comtest.c file for more
\r
179 #define mainCOM_TEST_LED ( 1 )
\r
181 /* The baud rate used by the comtest tasks described at the top of this file. */
\r
182 #define mainCOM_TEST_BAUD_RATE ( 38400 )
\r
184 /* The maximum number of lines of text that can be displayed on the LCD. */
\r
185 #define mainMAX_LCD_LINES ( 8 )
\r
187 /* Just used to ensure parameters are passed into tasks correctly. */
\r
188 #define mainTASK_PARAMETER_CHECK_VALUE ( ( void * ) 0xDEAD )
\r
189 /*-----------------------------------------------------------*/
\r
192 * The reg test tasks as described at the top of this file.
\r
194 extern void vRegTest1Task( void *pvParameters );
\r
195 extern void vRegTest2Task( void *pvParameters );
\r
198 * Configures clocks, LCD, port pints, etc. necessary to execute this demo.
\r
200 static void prvSetupHardware( void );
\r
203 * Definition of the LCD/controller task described in the comments at the top
\r
206 static void prvLCDTask( void *pvParameters );
\r
209 * Definition of the button poll task described in the comments at the top of
\r
212 static void prvButtonPollTask( void *pvParameters );
\r
215 * Converts a status message value into an appropriate string for display on
\r
216 * the LCD. The string is written to pcBuffer.
\r
218 static void prvGenerateStatusMessage( char *pcBuffer, long lStatusValue );
\r
220 /*-----------------------------------------------------------*/
\r
222 /* Variables that are incremented on each iteration of the reg test tasks -
\r
223 provided the tasks have not reported any errors. The check task inspects these
\r
224 variables to ensure they are still incrementing as expected. If a variable
\r
225 stops incrementing then it is likely that its associate task has stalled. */
\r
226 volatile unsigned short usRegTest1Counter = 0, usRegTest2Counter = 0;
\r
228 /* The handle of the queue used to send messages from tasks and interrupts to
\r
230 static xQueueHandle xLCDQueue = NULL;
\r
232 /* The definition of each message sent from tasks and interrupts to the LCD
\r
236 char cMessageID; /* << States what the message is. */
\r
237 unsigned long ulMessageValue; /* << States the message value (can be an integer, string pointer, etc. depending on the value of cMessageID). */
\r
240 /*-----------------------------------------------------------*/
\r
242 /* The linker script can be used to test the FreeRTOS ports use of 20bit
\r
243 addresses by locating all code in high memory. The following pragma ensures
\r
244 that main remains in low memory when that is done. The ISR_CODE segment is used
\r
245 for convenience as ISR functions are always placed in low memory. */
\r
246 #pragma location="ISR_CODE"
\r
249 /* Configure the peripherals used by this demo application. This includes
\r
250 configuring the joystick input select button to generate interrupts. */
\r
251 prvSetupHardware();
\r
253 /* Create the queue used by tasks and interrupts to send strings to the LCD
\r
255 xLCDQueue = xQueueCreate( mainQUEUE_LENGTH, sizeof( xQueueMessage ) );
\r
257 /* If the queue could not be created then don't create any tasks that might
\r
258 attempt to use the queue. */
\r
259 if( xLCDQueue != NULL )
\r
261 /* Add the created queue to the queue registry so it can be viewed in
\r
262 the IAR FreeRTOS state viewer plug-in. */
\r
263 vQueueAddToRegistry( xLCDQueue, "LCDQueue" );
\r
265 /* Create the standard demo tasks. */
\r
266 vAltStartComTestTasks( mainCOM_TEST_PRIORITY, mainCOM_TEST_BAUD_RATE, mainCOM_TEST_LED );
\r
267 vStartDynamicPriorityTasks();
\r
268 vStartGenericQueueTasks( mainGENERIC_QUEUE_TEST_PRIORITY );
\r
270 /* Create the LCD, button poll and register test tasks, as described at
\r
271 the top of this file. */
\r
272 xTaskCreate( prvLCDTask, ( signed char * ) "LCD", configMINIMAL_STACK_SIZE * 2, mainTASK_PARAMETER_CHECK_VALUE, mainLCD_TASK_PRIORITY, NULL );
\r
273 xTaskCreate( prvButtonPollTask, ( signed char * ) "BPoll", configMINIMAL_STACK_SIZE, NULL, tskIDLE_PRIORITY, NULL );
\r
274 xTaskCreate( vRegTest1Task, ( signed char * ) "Reg1", configMINIMAL_STACK_SIZE, NULL, 0, NULL );
\r
275 xTaskCreate( vRegTest2Task, ( signed char * ) "Reg2", configMINIMAL_STACK_SIZE, NULL, 0, NULL );
\r
277 /* Start the scheduler. */
\r
278 vTaskStartScheduler();
\r
281 /* If all is well then this line will never be reached. If it is reached
\r
282 then it is likely that there was insufficient (FreeRTOS) heap memory space
\r
283 to create the idle task. This may have been trapped by the malloc() failed
\r
284 hook function, if one is configured. */
\r
287 /*-----------------------------------------------------------*/
\r
289 static void prvLCDTask( void *pvParameters )
\r
291 xQueueMessage xReceivedMessage;
\r
293 /* Buffer into which strings are formatted and placed ready for display on the
\r
294 LCD. Note this is a static variable to prevent it being allocated on the task
\r
295 stack, which is too small to hold such a variable. The stack size is configured
\r
296 when the task is created. */
\r
297 static char cBuffer[ 512 ];
\r
298 unsigned char ucLine = 1;
\r
301 /* This function is the only function that uses printf(). If printf() is
\r
302 used from any other function then some sort of mutual exclusion on stdout
\r
305 This is also the only function that is permitted to access the LCD.
\r
307 First print out the number of bytes that remain in the FreeRTOS heap. This
\r
308 can be viewed in the terminal IO window within the IAR Embedded Workbench. */
\r
309 printf( "%d bytes of heap space remain unallocated\n", ( int ) xPortGetFreeHeapSize() );
\r
311 /* Just as a test of the port, and for no functional reason, check the task
\r
312 parameter contains its expected value. */
\r
313 if( pvParameters != mainTASK_PARAMETER_CHECK_VALUE )
\r
315 halLcdPrintLine( "Invalid parameter", ucLine, OVERWRITE_TEXT );
\r
321 /* Wait for a message to be received. Using portMAX_DELAY as the block
\r
322 time will result in an indefinite wait provided INCLUDE_vTaskSuspend is
\r
323 set to 1 in FreeRTOSConfig.h, therefore there is no need to check the
\r
324 function return value and the function will only return when a value
\r
325 has been received. */
\r
326 xQueueReceive( xLCDQueue, &xReceivedMessage, portMAX_DELAY );
\r
328 /* Clear the LCD if no room remains for any more text output. */
\r
329 if( ucLine > mainMAX_LCD_LINES )
\r
331 halLcdClearScreen();
\r
335 /* What is this message? What does it contain? */
\r
336 switch( xReceivedMessage.cMessageID )
\r
338 case mainMESSAGE_BUTTON_UP : /* The button poll task has just
\r
339 informed this task that the up
\r
340 button on the joystick input has
\r
341 been pressed or released. */
\r
342 sprintf( cBuffer, "Button up = %d", ( int ) xReceivedMessage.ulMessageValue );
\r
345 case mainMESSAGE_BUTTON_SEL : /* The select button interrupt
\r
346 just informed this task that the
\r
347 select button was pressed.
\r
348 Generate a table of task run time
\r
349 statistics and output this to
\r
350 the terminal IO window in the IAR
\r
351 embedded workbench. */
\r
352 printf( "\nTask\t Abs Time\t %%Time\n*****************************************" );
\r
353 vTaskGetRunTimeStats( ( signed char * ) cBuffer );
\r
356 /* Also print out a message to
\r
357 the LCD - in this case the
\r
358 pointer to the string to print
\r
359 is sent directly in the
\r
360 ulMessageValue member of the
\r
361 message. This just demonstrates
\r
362 a different communication
\r
364 sprintf( cBuffer, "%s", ( char * ) xReceivedMessage.ulMessageValue );
\r
367 case mainMESSAGE_STATUS : /* The tick interrupt hook
\r
368 function has just informed this
\r
369 task of the system status.
\r
370 Generate a string in accordance
\r
371 with the status value. */
\r
372 prvGenerateStatusMessage( cBuffer, xReceivedMessage.ulMessageValue );
\r
375 default : sprintf( cBuffer, "Unknown message" );
\r
379 /* Output the message that was placed into the cBuffer array within the
\r
380 switch statement above, then move onto the next line ready for the next
\r
381 message to arrive on the queue. */
\r
382 halLcdPrintLine( cBuffer, ucLine, OVERWRITE_TEXT );
\r
386 /*-----------------------------------------------------------*/
\r
388 static void prvGenerateStatusMessage( char *pcBuffer, long lStatusValue )
\r
390 /* Just a utility function to convert a status value into a meaningful
\r
391 string for output onto the LCD. */
\r
392 switch( lStatusValue )
\r
394 case pdPASS : sprintf( pcBuffer, "Status = PASS" );
\r
396 case mainERROR_DYNAMIC_TASKS : sprintf( pcBuffer, "Err: Dynamic tsks" );
\r
398 case mainERROR_COM_TEST : sprintf( pcBuffer, "Err: COM test" );
\r
400 case mainERROR_GEN_QUEUE_TEST : sprintf( pcBuffer, "Error: Gen Q test" );
\r
402 case mainERROR_REG_TEST : sprintf( pcBuffer, "Error: Reg test" );
\r
404 default : sprintf( pcBuffer, "Unknown status" );
\r
408 /*-----------------------------------------------------------*/
\r
410 static void prvButtonPollTask( void *pvParameters )
\r
412 unsigned char ucLastState = pdFALSE, ucState;
\r
413 xQueueMessage xMessage;
\r
415 /* This tasks performs the button polling functionality as described at the
\r
416 top of this file. */
\r
419 /* Check the button state. */
\r
420 ucState = ( halButtonsPressed() & BUTTON_UP );
\r
424 /* The button was pressed. */
\r
428 if( ucState != ucLastState )
\r
430 /* The state has changed, send a message to the LCD task. */
\r
431 xMessage.cMessageID = mainMESSAGE_BUTTON_UP;
\r
432 xMessage.ulMessageValue = ( unsigned long ) ucState;
\r
433 ucLastState = ucState;
\r
434 xQueueSend( xLCDQueue, &xMessage, portMAX_DELAY );
\r
437 /* Block for 10 milliseconds so this task does not utilise all the CPU
\r
438 time and debouncing of the button is not necessary. */
\r
439 vTaskDelay( 10 / portTICK_RATE_MS );
\r
442 /*-----------------------------------------------------------*/
\r
444 static void prvSetupHardware( void )
\r
446 /* Convert a Hz value to a KHz value, as required by the Init_FLL_Settle()
\r
448 unsigned long ulCPU_Clock_KHz = ( configCPU_CLOCK_HZ / 1000UL );
\r
452 LFXT_Start( XT1DRIVE_0 );
\r
453 Init_FLL_Settle( ( unsigned short ) ulCPU_Clock_KHz, 488 );
\r
455 halButtonsInit( BUTTON_ALL );
\r
456 halButtonsInterruptEnable( BUTTON_SELECT );
\r
458 /* Initialise the LCD, but note that the backlight is not used as the
\r
459 library function uses timer A0 to modulate the backlight, and this file
\r
460 defines vApplicationSetupTimerInterrupt() to also use timer A0 to generate
\r
461 the tick interrupt. If the backlight is required, then change either the
\r
462 halLCD library or vApplicationSetupTimerInterrupt() to use a different
\r
463 timer. Timer A1 is used for the run time stats time base6. */
\r
465 halLcdSetContrast( 100 );
\r
466 halLcdClearScreen();
\r
468 halLcdPrintLine( " www.FreeRTOS.org", 0, OVERWRITE_TEXT );
\r
470 /*-----------------------------------------------------------*/
\r
472 void vApplicationTickHook( void )
\r
474 static unsigned short usLastRegTest1Counter = 0, usLastRegTest2Counter = 0;
\r
475 static unsigned long ulCounter = 0;
\r
476 static const unsigned long ulCheckFrequency = 5000UL / portTICK_RATE_MS;
\r
477 portBASE_TYPE xHigherPriorityTaskWoken = pdFALSE;
\r
479 /* Define the status message that is sent to the LCD task. By default the
\r
481 static xQueueMessage xStatusMessage = { mainMESSAGE_STATUS, pdPASS };
\r
483 /* This is called from within the tick interrupt and performs the 'check'
\r
484 functionality as described in the comments at the top of this file.
\r
486 Is it time to perform the 'check' functionality again? */
\r
488 if( ulCounter >= ulCheckFrequency )
\r
490 /* See if the standard demo tasks are executing as expected, changing
\r
491 the message that is sent to the LCD task from PASS to an error code if
\r
492 any tasks set reports an error. */
\r
493 if( xAreComTestTasksStillRunning() != pdPASS )
\r
495 xStatusMessage.ulMessageValue = mainERROR_COM_TEST;
\r
498 if( xAreDynamicPriorityTasksStillRunning() != pdPASS )
\r
500 xStatusMessage.ulMessageValue = mainERROR_DYNAMIC_TASKS;
\r
503 if( xAreGenericQueueTasksStillRunning() != pdPASS )
\r
505 xStatusMessage.ulMessageValue = mainERROR_GEN_QUEUE_TEST;
\r
508 /* Check the reg test tasks are still cycling. They will stop
\r
509 incrementing their loop counters if they encounter an error. */
\r
510 if( usRegTest1Counter == usLastRegTest1Counter )
\r
512 xStatusMessage.ulMessageValue = mainERROR_REG_TEST;
\r
515 if( usRegTest2Counter == usLastRegTest2Counter )
\r
517 xStatusMessage.ulMessageValue = mainERROR_REG_TEST;
\r
520 usLastRegTest1Counter = usRegTest1Counter;
\r
521 usLastRegTest2Counter = usRegTest2Counter;
\r
523 /* As this is the tick hook the lHigherPriorityTaskWoken parameter is not
\r
524 needed (a context switch is going to be performed anyway), but it must
\r
525 still be provided. */
\r
526 xQueueSendFromISR( xLCDQueue, &xStatusMessage, &xHigherPriorityTaskWoken );
\r
530 /* Just periodically toggle an LED to show that the tick interrupt is
\r
531 running. Note that this access LED_PORT_OUT in a non-atomic way, so tasks
\r
532 that access the same port must do so from a critical section. */
\r
533 if( ( ulCounter & 0xff ) == 0 )
\r
535 if( ( LED_PORT_OUT & LED_1 ) == 0 )
\r
537 LED_PORT_OUT |= LED_1;
\r
541 LED_PORT_OUT &= ~LED_1;
\r
545 /*-----------------------------------------------------------*/
\r
547 #pragma vector=PORT2_VECTOR
\r
548 __interrupt static void prvSelectButtonInterrupt(void)
\r
550 /* Define the message sent to the LCD task from this interrupt. */
\r
551 static const xQueueMessage xMessage = { mainMESSAGE_BUTTON_SEL, ( unsigned long ) "Select Interrupt" };
\r
552 portBASE_TYPE xHigherPriorityTaskWoken = pdFALSE;
\r
554 /* This is the interrupt handler for the joystick select button input.
\r
555 The button has been pushed, write a message to the LCD via the LCD task. */
\r
556 xQueueSendFromISR( xLCDQueue, &xMessage, &xHigherPriorityTaskWoken );
\r
560 /* If writing to xLCDQueue caused a task to unblock, and the unblocked task
\r
561 has a priority equal to or above the task that this interrupt interrupted,
\r
562 then lHigherPriorityTaskWoken will have been set to pdTRUE internally within
\r
563 xQueuesendFromISR(), and portEND_SWITCHING_ISR() will ensure that this
\r
564 interrupt returns directly to the higher priority unblocked task. */
\r
565 portYIELD_FROM_ISR( xHigherPriorityTaskWoken );
\r
567 /*-----------------------------------------------------------*/
\r
569 /* The MSP430X port uses this callback function to configure its tick interrupt.
\r
570 This allows the application to choose the tick interrupt source.
\r
571 configTICK_VECTOR must also be set in FreeRTOSConfig.h to the correct
\r
572 interrupt vector for the chosen tick interrupt source. This implementation of
\r
573 vApplicationSetupTimerInterrupt() generates the tick from timer A0, so in this
\r
574 case configTICK_VECTOR is set to TIMER0_A0_VECTOR. */
\r
575 void vApplicationSetupTimerInterrupt( void )
\r
577 const unsigned short usACLK_Frequency_Hz = 32768;
\r
579 /* Ensure the timer is stopped. */
\r
582 /* Run the timer from the ACLK. */
\r
585 /* Clear everything to start with. */
\r
588 /* Set the compare match value according to the tick rate we want. */
\r
589 TA0CCR0 = usACLK_Frequency_Hz / configTICK_RATE_HZ;
\r
591 /* Enable the interrupts. */
\r
594 /* Start up clean. */
\r
600 /*-----------------------------------------------------------*/
\r
602 void vApplicationIdleHook( void )
\r
604 /* Called on each iteration of the idle task. In this case the idle task
\r
605 just enters a low power mode. */
\r
606 __bis_SR_register( LPM3_bits + GIE );
\r
608 /*-----------------------------------------------------------*/
\r
610 void vApplicationMallocFailedHook( void )
\r
612 /* Called if a call to pvPortMalloc() fails because there is insufficient
\r
613 free memory available in the FreeRTOS heap. pvPortMalloc() is called
\r
614 internally by FreeRTOS API functions that create tasks, queues or
\r
616 taskDISABLE_INTERRUPTS();
\r
619 /*-----------------------------------------------------------*/
\r
621 void vApplicationStackOverflowHook( xTaskHandle *pxTask, signed char *pcTaskName )
\r
624 ( void ) pcTaskName;
\r
626 /* Run time stack overflow checking is performed if
\r
627 configconfigCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
628 function is called if a stack overflow is detected. */
\r
629 taskDISABLE_INTERRUPTS();
\r
632 /*-----------------------------------------------------------*/
\r
projects / freertos / blob