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
54 /* ****************************************************************************
\r
55 * main-blinky.c is included when the "Blinky" build configuration is used.
\r
56 * main-full.c is included when the "Full" build configuration is used.
\r
58 * main-full.c creates a lot of demo and test tasks and timers, and is
\r
59 * therefore very comprehensive but also complex. If you would prefer a much
\r
60 * simpler project to get started with, then select the 'Blinky' build
\r
61 * configuration within the SDK Eclipse IDE. See the documentation page for
\r
62 * this demo on the http://www.FreeRTOS.org web site for more information.
\r
63 * ****************************************************************************
\r
65 * main() creates all the demo application tasks and timers, then starts the
\r
66 * scheduler. The web documentation provides more details of the standard demo
\r
67 * application tasks, which provide no particular functionality, but do provide
\r
68 * a good example of how to use the FreeRTOS API.
\r
70 * In addition to the standard demo tasks, the following tasks and tests are
\r
71 * defined and/or created within this file:
\r
73 * TCP/IP ("lwIP") task - TBD _RB_
\r
75 * "Reg test" tasks - These test the task context switch mechanism by first
\r
76 * filling the MicroBlaze registers with known values, before checking that each
\r
77 * register maintains the value that was written to it as the tasks are switched
\r
78 * in and out. The two register test tasks do not use the same values, and
\r
79 * execute at a very low priority to ensure they are pre-empted regularly.
\r
81 * "Check" timer - The check timer period is initially set to five seconds.
\r
82 * The check timer callback function checks that all the standard demo tasks,
\r
83 * and the register check tasks, are not only still executing, but are executing
\r
84 * without reporting any errors. If the check timer discovers that a task has
\r
85 * either stalled, or reported an error, then it changes its own period from
\r
86 * the initial five seconds, to just 200ms. The check timer callback function
\r
87 * also toggles an LED each time it is called. This provides a visual
\r
88 * indication of the system status: If the LED toggles every five seconds then
\r
89 * no issues have been discovered. If the LED toggles every 200ms then an issue
\r
90 * has been discovered with at least one task. The last reported issue is
\r
91 * latched into the pcStatusMessage variable.
\r
93 * This file also includes example implementations of the vApplicationTickHook(),
\r
94 * vApplicationIdleHook(), vApplicationStackOverflowHook(),
\r
95 * vApplicationMallocFailedHook(), vApplicationClearTimerInterrupt(), and
\r
96 * vApplicationSetupTimerInterrupt() callback (hook) functions.
\r
99 /* Standard includes. */
\r
100 #include <string.h>
\r
103 /* BSP includes. */
\r
104 #include "xtmrctr.h"
\r
105 #include "microblaze_exceptions_g.h"
\r
107 /* Kernel includes. */
\r
108 #include "FreeRTOS.h"
\r
110 #include "timers.h"
\r
112 /* Standard demo includes. */
\r
113 #include "partest.h"
\r
115 #include "BlockQ.h"
\r
117 #include "blocktim.h"
\r
118 #include "semtest.h"
\r
120 #include "GenQTest.h"
\r
122 #include "recmutex.h"
\r
124 #include "dynamic.h"
\r
125 #include "comtest_strings.h"
\r
126 #include "TimerDemo.h"
\r
128 /* lwIP includes. */
\r
129 #include "lwip/tcpip.h"
\r
132 /* Priorities at which the various tasks are created. */
\r
133 #define mainQUEUE_POLL_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
134 #define mainSEM_TEST_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
135 #define mainBLOCK_Q_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
136 #define mainCREATOR_TASK_PRIORITY ( tskIDLE_PRIORITY + 3 )
\r
137 #define mainFLASH_TASK_PRIORITY ( tskIDLE_PRIORITY + 1 )
\r
138 #define mainuIP_TASK_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
139 #define mainCOM_TEST_PRIORITY ( tskIDLE_PRIORITY + 2 )
\r
140 #define mainINTEGER_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
141 #define mainGEN_QUEUE_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
142 #define mainFLOP_TASK_PRIORITY ( tskIDLE_PRIORITY )
\r
144 /* The LED toggled by the check task. */
\r
145 #define mainCHECK_LED ( 3 )
\r
147 /* The rate at which mainCHECK_LED will toggle when all the tasks are running
\r
148 without error. See the description of the check timer in the comments at the
\r
149 top of this file. */
\r
150 #define mainNO_ERROR_CHECK_TIMER_PERIOD ( 5000 / portTICK_RATE_MS )
\r
152 /* The rate at which mainCHECK_LED will toggle when an error has been reported
\r
153 by at least one task. See the description of the check timer in the comments at
\r
154 the top of this file. */
\r
155 #define mainERROR_CHECK_TIMER_PERIOD ( 200 / portTICK_RATE_MS )
\r
157 /* A block time of zero simply means "don't block". */
158 #define mainDONT_BLOCK ( ( portTickType ) 0 )
\r
160 /* The LED used by the comtest tasks. See the comtest_strings.c file for more
\r
161 information. In this case an invalid LED number is provided as all four
\r
162 available LEDs (LEDs 0 to 3) are already in use. */
\r
163 #define mainCOM_TEST_LED ( 4 )
\r
165 /* Baud rate used by the comtest tasks. The baud rate used is actually fixed in
\r
166 UARTLite IP when the hardware was built, but the standard serial init function
\r
167 required a baud rate parameter to be provided - in this case it is just
\r
169 #define mainCOM_TEST_BAUD_RATE ( XPAR_RS232_UART_1_BAUDRATE )
\r
171 /* The timer test task generates a lot of timers that all use a different
\r
172 period that is a multiple of the mainTIMER_TEST_PERIOD definition. */
\r
173 #define mainTIMER_TEST_PERIOD ( 20 )
\r
175 /*-----------------------------------------------------------*/
\r
178 * The register test tasks as described in the comments at the top of this file.
\r
179 * The nature of the register test tasks means they have to be implemented in
\r
182 extern void vRegisterTest1( void *pvParameters );
\r
183 extern void vRegisterTest2( void *pvParameters );
\r
186 * Defines the 'check' timer functionality as described at the top of this file.
\r
187 * This function is the callback function associated with the 'check' timer.
\r
189 static void vCheckTimerCallback( xTimerHandle xTimer );
\r
192 * Configure the interrupt controller, LED outputs and button inputs.
\r
194 static void prvSetupHardware( void );
\r
196 /* Defined in lwIPApps.c. */
\r
197 extern void lwIPAppsInit( void *pvArguments );
\r
199 /*-----------------------------------------------------------*/
\r
201 /* The check timer callback function sets pcStatusMessage to a string that
\r
202 indicates the last reported error that it discovered. */
\r
203 static const char *pcStatusMessage = NULL;
\r
205 /* Structures that hold the state of the various peripherals used by this demo.
\r
206 These are used by the Xilinx peripheral driver API functions. In this case,
\r
207 only the timer/counter is used directly within this file. */
\r
208 static XTmrCtr xTimer0Instance;
\r
210 /* The 'check' timer, as described at the top of this file. */
\r
211 static xTimerHandle xCheckTimer = NULL;
\r
213 /*-----------------------------------------------------------*/
\r
217 /***************************************************************************
\r
218 This project includes a lot of demo and test tasks and timers, and is
\r
219 therefore comprehensive, but complex. If you would prefer a much simpler
\r
220 project to get started with, then select the 'Blinky' build configuration
\r
221 within the SDK Eclipse IDE.
\r
222 ***************************************************************************/
\r
224 /* Configure the interrupt controller, LED outputs and button inputs. */
\r
225 prvSetupHardware();
\r
227 /* This call creates the TCP/IP thread. */
\r
228 tcpip_init( lwIPAppsInit, NULL );
\r
230 /* Start the reg test tasks, as described in the comments at the top of this
\r
232 xTaskCreate( vRegisterTest1, ( const signed char * const ) "RegTst1", configMINIMAL_STACK_SIZE, ( void * ) 0, tskIDLE_PRIORITY, NULL );
\r
233 xTaskCreate( vRegisterTest2, ( const signed char * const ) "RegTst2", configMINIMAL_STACK_SIZE, ( void * ) 0, tskIDLE_PRIORITY, NULL );
\r
235 /* Create the standard demo tasks. */
\r
236 vStartBlockingQueueTasks( mainBLOCK_Q_PRIORITY );
\r
237 vCreateBlockTimeTasks();
\r
238 vStartSemaphoreTasks( mainSEM_TEST_PRIORITY );
\r
239 vStartPolledQueueTasks( mainQUEUE_POLL_PRIORITY );
\r
240 vStartGenericQueueTasks( mainGEN_QUEUE_TASK_PRIORITY );
\r
241 vStartLEDFlashTasks( mainFLASH_TASK_PRIORITY );
\r
242 vStartQueuePeekTasks();
\r
243 vStartRecursiveMutexTasks();
\r
244 vStartComTestStringsTasks( mainCOM_TEST_PRIORITY, mainCOM_TEST_BAUD_RATE, mainCOM_TEST_LED );
\r
245 vStartDynamicPriorityTasks();
\r
246 vStartTimerDemoTask( mainTIMER_TEST_PERIOD );
\r
248 /* Note - the set of standard demo tasks contains two versions of
\r
249 vStartMathTasks.c. One is defined in flop.c, and uses double precision
\r
250 floating point numbers and variables. The other is defined in sp_flop.c,
\r
251 and uses single precision floating point numbers and variables. The
\r
252 MicroBlaze floating point unit only handles single precision floating.
\r
253 Therefore, to test the floating point hardware, sp_flop.c should be included
\r
254 in this project. */
\r
255 vStartMathTasks( mainFLOP_TASK_PRIORITY );
\r
257 /* The suicide tasks must be created last as they need to know how many
\r
258 tasks were running prior to their creation. This then allows them to
\r
259 ascertain whether or not the correct/expected number of tasks are running at
\r
261 vCreateSuicidalTasks( mainCREATOR_TASK_PRIORITY );
\r
263 /* Create the 'check' timer - the timer that periodically calls the
\r
264 check function as described in the comments at the top of this file. Note
\r
265 that, for reasons stated in the comments within vApplicationIdleHook()
\r
266 (defined in this file), the check timer is not actually started until after
\r
267 the scheduler has been started. */
\r
268 xCheckTimer = xTimerCreate( ( const signed char * ) "Check timer", mainNO_ERROR_CHECK_TIMER_PERIOD, pdTRUE, ( void * ) 0, vCheckTimerCallback );
\r
270 /* Start the scheduler running. From this point on, only tasks and
\r
271 interrupts will be executing. */
\r
272 vTaskStartScheduler();
\r
274 /* If all is well then the following line will never be reached. If
\r
275 execution does reach here, then it is highly probably that the heap size
\r
276 is too small for the idle and/or timer tasks to be created within
\r
277 vTaskStartScheduler(). */
\r
278 taskDISABLE_INTERRUPTS();
\r
281 /*-----------------------------------------------------------*/
\r
283 static void vCheckTimerCallback( xTimerHandle xTimer )
\r
285 extern unsigned long ulRegTest1CycleCount, ulRegTest2CycleCount;
\r
286 static volatile unsigned long ulLastRegTest1CycleCount = 0UL, ulLastRegTest2CycleCount = 0UL;
\r
287 static long lErrorAlreadyLatched = pdFALSE;
\r
288 portTickType xExecutionRate = mainNO_ERROR_CHECK_TIMER_PERIOD;
\r
290 /* This is the callback function used by the 'check' timer, as described
\r
291 in the comments at the top of this file. */
\r
293 /* Check the standard demo tasks are running without error. */
\r
294 if( xAreGenericQueueTasksStillRunning() != pdTRUE )
\r
296 pcStatusMessage = "Error: GenQueue";
\r
298 else if( xAreQueuePeekTasksStillRunning() != pdTRUE )
\r
300 pcStatusMessage = "Error: QueuePeek\r\n";
\r
302 else if( xAreBlockingQueuesStillRunning() != pdTRUE )
\r
304 pcStatusMessage = "Error: BlockQueue\r\n";
\r
306 else if( xAreBlockTimeTestTasksStillRunning() != pdTRUE )
\r
308 pcStatusMessage = "Error: BlockTime\r\n";
\r
310 else if( xAreSemaphoreTasksStillRunning() != pdTRUE )
\r
312 pcStatusMessage = "Error: SemTest\r\n";
\r
314 else if( xArePollingQueuesStillRunning() != pdTRUE )
\r
316 pcStatusMessage = "Error: PollQueue\r\n";
\r
318 else if( xIsCreateTaskStillRunning() != pdTRUE )
\r
320 pcStatusMessage = "Error: Death\r\n";
\r
322 else if( xAreRecursiveMutexTasksStillRunning() != pdTRUE )
\r
324 pcStatusMessage = "Error: RecMutex\r\n";
\r
326 else if( xAreMathsTaskStillRunning() != pdPASS )
\r
328 pcStatusMessage = "Error: Flop\r\n";
\r
330 else if( xAreComTestTasksStillRunning() != pdPASS )
\r
332 pcStatusMessage = "Error: Comtest\r\n";
\r
334 else if( xAreDynamicPriorityTasksStillRunning() != pdPASS )
\r
336 pcStatusMessage = "Error: Dynamic\r\n";
\r
338 else if( xAreTimerDemoTasksStillRunning( xExecutionRate ) != pdTRUE )
\r
340 pcStatusMessage = "Error: TimerDemo";
\r
342 else if( ulRegTest1CycleCount == ulLastRegTest1CycleCount )
\r
344 /* Check the reg test tasks are still cycling. They will stop
\r
345 incrementing their loop counters if they encounter an error. */
\r
346 pcStatusMessage = "Error: RegTest1\r\n";
\r
348 else if( ulRegTest2CycleCount == ulLastRegTest2CycleCount )
\r
350 pcStatusMessage = "Error: RegTest2\r\n";
\r
353 /* Store a local copy of the current reg test loop counters. If these have
\r
354 not incremented the next time this callback function is executed then the
\r
355 reg test tasks have either stalled or discovered an error. */
\r
356 ulLastRegTest1CycleCount = ulRegTest1CycleCount;
\r
357 ulLastRegTest2CycleCount = ulRegTest2CycleCount;
\r
359 /* Toggle the check LED to give an indication of the system status. If
\r
360 the LED toggles every 5 seconds then everything is ok. A faster toggle
\r
361 indicates an error. */
\r
362 vParTestToggleLED( mainCHECK_LED );
\r
364 if( pcStatusMessage != NULL )
\r
366 if( lErrorAlreadyLatched == pdFALSE )
\r
368 /* An error has occurred, so change the period of the timer that
\r
369 calls this callback function. This results in the LED toggling at
\r
370 a faster rate - giving the user visual feedback that something is not
\r
371 as it should be. This function is called from the context of the
\r
372 timer service task so must ***not*** attempt to block while calling
\r
374 if( xTimerChangePeriod( xTimer, mainERROR_CHECK_TIMER_PERIOD, mainDONT_BLOCK ) == pdPASS )
\r
376 /* If the command to change the timer period was sent to the
\r
377 timer command queue successfully, then latch the fact that the
\r
378 timer period has already been changed. This is just done to
\r
379 prevent xTimerChangePeriod() being called on every execution of
\r
380 this function once an error has been discovered. */
\r
381 lErrorAlreadyLatched = pdTRUE;
\r
384 /* Update the xExecutionRate variable too as the rate at which this
\r
385 callback is executed has to be passed into the
\r
386 xAreTimerDemoTasksStillRunning() function. */
\r
387 xExecutionRate = mainERROR_CHECK_TIMER_PERIOD;
\r
391 /*-----------------------------------------------------------*/
\r
393 /* This is an application defined callback function used to install the tick
\r
394 interrupt handler. It is provided as an application callback because the kernel
\r
395 will run on lots of different MicroBlaze and FPGA configurations - not all of
\r
396 which will have the same timer peripherals defined or available. This example
\r
397 uses the AXI Timer 0. If that is available on your hardware platform then this
\r
398 example callback implementation should not require modification. The name of
\r
399 the interrupt handler that should be installed is vPortTickISR(), which the
\r
400 function below declares as an extern. */
\r
401 void vApplicationSetupTimerInterrupt( void )
\r
403 portBASE_TYPE xStatus;
\r
404 const unsigned char ucTimerCounterNumber = ( unsigned char ) 0U;
\r
405 const unsigned long ulCounterValue = ( ( XPAR_AXI_TIMER_0_CLOCK_FREQ_HZ / configTICK_RATE_HZ ) - 1UL );
\r
406 extern void vPortTickISR( void *pvUnused );
\r
408 /* Initialise the timer/counter. */
\r
409 xStatus = XTmrCtr_Initialize( &xTimer0Instance, XPAR_AXI_TIMER_0_DEVICE_ID );
\r
411 if( xStatus == XST_SUCCESS )
\r
413 /* Install the tick interrupt handler as the timer ISR.
\r
414 *NOTE* The xPortInstallInterruptHandler() API function must be used for
\r
416 xStatus = xPortInstallInterruptHandler( XPAR_INTC_0_TMRCTR_0_VEC_ID, vPortTickISR, NULL );
\r
419 if( xStatus == pdPASS )
\r
421 /* Enable the timer interrupt in the interrupt controller.
\r
422 *NOTE* The vPortEnableInterrupt() API function must be used for this
\r
424 vPortEnableInterrupt( XPAR_INTC_0_TMRCTR_0_VEC_ID );
\r
426 /* Configure the timer interrupt handler. */
\r
427 XTmrCtr_SetHandler( &xTimer0Instance, ( void * ) vPortTickISR, NULL );
\r
429 /* Set the correct period for the timer. */
\r
430 XTmrCtr_SetResetValue( &xTimer0Instance, ucTimerCounterNumber, ulCounterValue );
\r
432 /* Enable the interrupts. Auto-reload mode is used to generate a
\r
433 periodic tick. Note that interrupts are disabled when this function is
\r
434 called, so interrupts will not start to be processed until the first
\r
435 task has started to run. */
\r
436 XTmrCtr_SetOptions( &xTimer0Instance, ucTimerCounterNumber, ( XTC_INT_MODE_OPTION | XTC_AUTO_RELOAD_OPTION | XTC_DOWN_COUNT_OPTION ) );
\r
438 /* Start the timer. */
\r
439 XTmrCtr_Start( &xTimer0Instance, ucTimerCounterNumber );
\r
442 /* Sanity check that the function executed as expected. */
\r
443 configASSERT( ( xStatus == pdPASS ) );
\r
445 /*-----------------------------------------------------------*/
\r
447 /* This is an application defined callback function used to clear whichever
\r
448 interrupt was installed by the the vApplicationSetupTimerInterrupt() callback
\r
449 function - in this case the interrupt generated by the AXI timer. It is
\r
450 provided as an application callback because the kernel will run on lots of
\r
451 different MicroBlaze and FPGA configurations - not all of which will have the
\r
452 same timer peripherals defined or available. This example uses the AXI Timer 0.
\r
453 If that is available on your hardware platform then this example callback
\r
454 implementation should not require modification provided the example definition
\r
455 of vApplicationSetupTimerInterrupt() is also not modified. */
\r
456 void vApplicationClearTimerInterrupt( void )
\r
458 unsigned long ulCSR;
\r
460 /* Clear the timer interrupt */
\r
461 ulCSR = XTmrCtr_GetControlStatusReg( XPAR_AXI_TIMER_0_BASEADDR, 0 );
\r
462 XTmrCtr_SetControlStatusReg( XPAR_AXI_TIMER_0_BASEADDR, 0, ulCSR );
\r
464 /*-----------------------------------------------------------*/
\r
466 void vApplicationMallocFailedHook( void )
\r
468 /* vApplicationMallocFailedHook() will only be called if
\r
469 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
470 function that will get called if a call to pvPortMalloc() fails.
\r
471 pvPortMalloc() is called internally by the kernel whenever a task, queue or
\r
472 semaphore is created. It is also called by various parts of the demo
\r
473 application. If heap_1.c or heap_2.c are used, then the size of the heap
\r
474 available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
475 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
476 to query the size of free heap space that remains (although it does not
\r
477 provide information on how the remaining heap might be fragmented). */
\r
478 taskDISABLE_INTERRUPTS();
\r
481 /*-----------------------------------------------------------*/
\r
483 void vApplicationStackOverflowHook( xTaskHandle *pxTask, signed char *pcTaskName )
\r
485 ( void ) pcTaskName;
\r
488 /* vApplicationStackOverflowHook() will only be called if
\r
489 configCHECK_FOR_STACK_OVERFLOW is set to either 1 or 2. The handle and name
\r
490 of the offending task will be passed into the hook function via its
\r
491 parameters. However, when a stack has overflowed, it is possible that the
\r
492 parameters will have been corrupted, in which case the pxCurrentTCB variable
\r
493 can be inspected directly. */
\r
494 taskDISABLE_INTERRUPTS();
\r
497 /*-----------------------------------------------------------*/
\r
499 void vApplicationIdleHook( void )
\r
501 static long lCheckTimerStarted = pdFALSE;
\r
503 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
504 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
505 task. It is essential that code added to this hook function never attempts
\r
506 to block in any way (for example, call xQueueReceive() with a block time
\r
507 specified, or call vTaskDelay()). If the application makes use of the
\r
508 vTaskDelete() API function (as this demo application does) then it is also
\r
509 important that vApplicationIdleHook() is permitted to return to its calling
\r
510 function, because it is the responsibility of the idle task to clean up
\r
511 memory allocated by the kernel to any task that has since been deleted. */
\r
513 /* If the check timer has not already been started, then start it now.
\r
514 Normally, the xTimerStart() API function can be called immediately after the
\r
515 timer is created - how this demo application includes the timer demo tasks.
\r
516 The timer demo tasks, as part of their test function, deliberately fill up
\r
517 the timer command queue - meaning the check timer cannot be started until
\r
518 after the scheduler has been started - at which point the timer command
\r
519 queue will have been drained. */
\r
520 if( lCheckTimerStarted == pdFALSE )
\r
522 xTimerStart( xCheckTimer, mainDONT_BLOCK );
\r
523 lCheckTimerStarted = pdTRUE;
\r
526 /*-----------------------------------------------------------*/
\r
528 void vApplicationTickHook( void )
\r
530 /* vApplicationTickHook() will only be called if configUSE_TICK_HOOK is set
\r
531 to 1 in FreeRTOSConfig.h. It executes from an interrupt context so must
\r
532 not use any FreeRTOS API functions that do not end in ...FromISR(). */
\r
534 /* Call the periodic timer test, which tests the timer API functions that
\r
535 can be called from an ISR. */
\r
536 vTimerPeriodicISRTests();
\r
538 /*-----------------------------------------------------------*/
\r
540 void vApplicationExceptionRegisterDump( xPortRegisterDump *xRegisterDump )
\r
542 ( void ) xRegisterDump;
\r
544 /* If configINSTALL_EXCEPTION_HANDLERS is set to 1 in FreeRTOSConfig.h, then
\r
545 the kernel will automatically install its own exception handlers before the
\r
546 kernel is started, if the application writer has not already caused them to
\r
547 be installed by calling either of the vPortExceptionsInstallHandlers()
\r
548 or xPortInstallInterruptHandler() API functions before that time. The
\r
549 kernels exception handler populates an xPortRegisterDump structure with
\r
550 the processor state at the point that the exception was triggered - and also
\r
551 includes a strings that say what the exception cause was and which task was
\r
552 running at the time. The exception handler then passes the populated
\r
553 xPortRegisterDump structure into vApplicationExceptionRegisterDump() to
\r
554 allow the application writer to perform any debugging that may be necessary.
\r
555 However, defining vApplicationExceptionRegisterDump() within the application
\r
556 itself is optional. The kernel will use a default implementation if the
\r
557 application writer chooses not to provide their own. */
\r
563 /*-----------------------------------------------------------*/
\r
565 static void prvSetupHardware( void )
\r
567 taskDISABLE_INTERRUPTS();
\r
569 /* Configure the LED outputs. */
\r
570 vParTestInitialise();
\r
572 /* Tasks inherit the exception and cache configuration of the MicroBlaze
\r
573 at the point that they are created. */
\r
574 #if MICROBLAZE_EXCEPTIONS_ENABLED == 1
\r
575 microblaze_enable_exceptions();
\r
578 #if XPAR_MICROBLAZE_USE_ICACHE == 1
\r
579 microblaze_invalidate_icache();
\r
580 microblaze_enable_icache();
\r
583 #if XPAR_MICROBLAZE_USE_DCACHE == 1
\r
584 microblaze_invalidate_dcache();
\r
585 microblaze_enable_dcache();
\r
589 /*-----------------------------------------------------------*/
\r
591 void vMainConfigureTimerForRunTimeStats( void )
\r
593 unsigned long ulRunTimeStatsDivisor;
\r
595 /* How many times does the counter counter increment in 10ms? */
\r
596 ulRunTimeStatsDivisor = 0UL / 1000UL; //_RB_
\r
598 /*-----------------------------------------------------------*/
\r
600 unsigned long ulMainGetRunTimeCounterValue( void )
\r
602 unsigned long ulReturn, ulCurrentCount;
\r
604 ulCurrentCount = 0UL;
\r
609 /*-----------------------------------------------------------*/
\r
611 char *pcMainGetTaskStatusMessage( void )
\r
613 return ( char * ) pcStatusMessage;
\r