/*\r
- FreeRTOS V7.4.1 - Copyright (C) 2013 Real Time Engineers Ltd.\r
+ FreeRTOS V7.6.0 - Copyright (C) 2013 Real Time Engineers Ltd.\r
+ All rights reserved\r
\r
- FEATURES AND PORTS ARE ADDED TO FREERTOS ALL THE TIME. PLEASE VISIT\r
- http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.\r
+ VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.\r
\r
***************************************************************************\r
* *\r
- * FreeRTOS tutorial books are available in pdf and paperback. *\r
- * Complete, revised, and edited pdf reference manuals are also *\r
- * available. *\r
+ * FreeRTOS provides completely free yet professionally developed, *\r
+ * robust, strictly quality controlled, supported, and cross *\r
+ * platform software that has become a de facto standard. *\r
* *\r
- * Purchasing FreeRTOS documentation will not only help you, by *\r
- * ensuring you get running as quickly as possible and with an *\r
- * in-depth knowledge of how to use FreeRTOS, it will also help *\r
- * the FreeRTOS project to continue with its mission of providing *\r
- * professional grade, cross platform, de facto standard solutions *\r
- * for microcontrollers - completely free of charge! *\r
+ * Help yourself get started quickly and support the FreeRTOS *\r
+ * project by purchasing a FreeRTOS tutorial book, reference *\r
+ * manual, or both from: http://www.FreeRTOS.org/Documentation *\r
* *\r
- * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *\r
- * *\r
- * Thank you for using FreeRTOS, and thank you for your support! *\r
+ * Thank you! *\r
* *\r
***************************************************************************\r
\r
-\r
This file is part of the FreeRTOS distribution.\r
\r
FreeRTOS is free software; you can redistribute it and/or modify it under\r
the terms of the GNU General Public License (version 2) as published by the\r
- Free Software Foundation AND MODIFIED BY the FreeRTOS exception.\r
+ Free Software Foundation >>!AND MODIFIED BY!<< the FreeRTOS exception.\r
\r
- >>>>>>NOTE<<<<<< The modification to the GPL is included to allow you to\r
- distribute a combined work that includes FreeRTOS without being obliged to\r
- provide the source code for proprietary components outside of the FreeRTOS\r
- kernel.\r
+ >>! NOTE: The modification to the GPL is included to allow you to distribute\r
+ >>! a combined work that includes FreeRTOS without being obliged to provide\r
+ >>! the source code for proprietary components outside of the FreeRTOS\r
+ >>! kernel.\r
\r
FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY\r
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS\r
- FOR A PARTICULAR PURPOSE. See the GNU General Public License for more\r
- details. You should have received a copy of the GNU General Public License\r
- and the FreeRTOS license exception along with FreeRTOS; if not it can be\r
- viewed here: http://www.freertos.org/a00114.html and also obtained by\r
- writing to Real Time Engineers Ltd., contact details for whom are available\r
- on the FreeRTOS WEB site.\r
+ FOR A PARTICULAR PURPOSE. Full license text is available from the following\r
+ link: http://www.freertos.org/a00114.html\r
\r
1 tab == 4 spaces!\r
\r
* *\r
***************************************************************************\r
\r
-\r
- http://www.FreeRTOS.org - Documentation, books, training, latest versions, \r
+ http://www.FreeRTOS.org - Documentation, books, training, latest versions,\r
license and Real Time Engineers Ltd. contact details.\r
\r
http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,\r
- including FreeRTOS+Trace - an indispensable productivity tool, and our new\r
- fully thread aware and reentrant UDP/IP stack.\r
-\r
- http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High \r
- Integrity Systems, who sell the code with commercial support, \r
- indemnification and middleware, under the OpenRTOS brand.\r
- \r
- http://www.SafeRTOS.com - High Integrity Systems also provide a safety \r
- engineered and independently SIL3 certified version for use in safety and \r
+ including FreeRTOS+Trace - an indispensable productivity tool, a DOS\r
+ compatible FAT file system, and our tiny thread aware UDP/IP stack.\r
+\r
+ http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High\r
+ Integrity Systems to sell under the OpenRTOS brand. Low cost OpenRTOS\r
+ licenses offer ticketed support, indemnification and middleware.\r
+\r
+ http://www.SafeRTOS.com - High Integrity Systems also provide a safety\r
+ engineered and independently SIL3 certified version for use in safety and\r
mission critical applications that require provable dependability.\r
+\r
+ 1 tab == 4 spaces!\r
*/\r
\r
/*\r
* one queue, and one timer. It also demonstrates how MicroBlaze interrupts\r
* can interact with FreeRTOS tasks/timers.\r
*\r
- * This simple demo project was developed and tested on the Spartan-6 SP605 \r
+ * This simple demo project was developed and tested on the Spartan-6 SP605\r
* development board, using the hardware configuration found in the hardware\r
* project that is already included in the Eclipse project.\r
*\r
* in this file. prvQueueReceiveTask() sits in a loop that causes it to\r
* repeatedly attempt to read data from the queue that was created within\r
* main(). When data is received, the task checks the value of the data, and\r
- * if the value equals the expected 100, toggles an LED. The 'block time' \r
+ * if the value equals the expected 100, toggles an LED. The 'block time'\r
* parameter passed to the queue receive function specifies that the task\r
* should be held in the Blocked state indefinitely to wait for data to be\r
* available on the queue. The queue receive task will only leave the Blocked\r
#define mainQUEUE_SEND_FREQUENCY_MS ( 200 / portTICK_RATE_MS )\r
\r
/* The number of items the queue can hold. This is 1 as the receive task\r
-will remove items as they are added because it has the higher priority, meaning \r
+will remove items as they are added because it has the higher priority, meaning\r
the send task should always find the queue empty. */\r
#define mainQUEUE_LENGTH ( 1 )\r
\r
*/\r
static void vLEDTimerCallback( xTimerHandle xTimer );\r
\r
-/* \r
+/*\r
* The handler executed each time a button interrupt is generated. This ensures\r
* the LED defined by mainTIMER_CONTROLLED_LED is on, and resets the timer so\r
* the timer will not turn the LED off for a full 5 seconds after the button\r
int main( void )\r
{\r
/* *************************************************************************\r
- This is a very simple project suitable for getting started with FreeRTOS. \r
- If you would prefer a more complex project that demonstrates a lot more \r
- features and tests, then select the 'Full' build configuration within the \r
- SDK Eclipse IDE. \r
+ This is a very simple project suitable for getting started with FreeRTOS.\r
+ If you would prefer a more complex project that demonstrates a lot more\r
+ features and tests, then select the 'Full' build configuration within the\r
+ SDK Eclipse IDE.\r
***************************************************************************/\r
\r
/* Configure the interrupt controller, LED outputs and button inputs. */\r
/* Sanity check that the queue was created. */\r
configASSERT( xQueue );\r
\r
- /* Start the two tasks as described in the comments at the top of this \r
+ /* Start the two tasks as described in the comments at the top of this\r
file. */\r
- xTaskCreate( prvQueueReceiveTask, ( signed char * ) "Rx", configMINIMAL_STACK_SIZE, NULL, mainQUEUE_RECEIVE_TASK_PRIORITY, NULL );\r
- xTaskCreate( prvQueueSendTask, ( signed char * ) "TX", configMINIMAL_STACK_SIZE, NULL, mainQUEUE_SEND_TASK_PRIORITY, NULL );\r
+ xTaskCreate( prvQueueReceiveTask, "Rx", configMINIMAL_STACK_SIZE, NULL, mainQUEUE_RECEIVE_TASK_PRIORITY, NULL );\r
+ xTaskCreate( prvQueueSendTask, "TX", configMINIMAL_STACK_SIZE, NULL, mainQUEUE_SEND_TASK_PRIORITY, NULL );\r
\r
/* Create the software timer that is responsible for turning off the LED\r
if the button is not pushed within 5000ms, as described at the top of\r
this file. The timer is not actually started until a button interrupt is\r
pushed, as it is not until that point that the LED is turned on. */\r
- xLEDTimer = xTimerCreate( ( const signed char * ) "LEDTimer", /* A text name, purely to help debugging. */\r
- ( 5000 / portTICK_RATE_MS ), /* The timer period, in this case 5000ms (5s). */\r
- pdFALSE, /* This is a one shot timer, so xAutoReload is set to pdFALSE. */\r
- ( void * ) 0, /* The ID is not used, so can be set to anything. */\r
- vLEDTimerCallback /* The callback function that switches the LED off. */\r
+ xLEDTimer = xTimerCreate( "LEDTimer", /* A text name, purely to help debugging. */\r
+ ( 5000 / portTICK_RATE_MS ),/* The timer period, in this case 5000ms (5s). */\r
+ pdFALSE, /* This is a one shot timer, so xAutoReload is set to pdFALSE. */\r
+ ( void * ) 0, /* The ID is not used, so can be set to anything. */\r
+ vLEDTimerCallback /* The callback function that switches the LED off. */\r
);\r
\r
/* Start the tasks and timer running. */\r
\r
if( xStatus == XST_SUCCESS )\r
{\r
- /* Install the handler defined in this task for the button input. \r
+ /* Install the handler defined in this task for the button input.\r
*NOTE* The FreeRTOS defined xPortInstallInterruptHandler() API function\r
must be used for this purpose. */\r
xStatus = xPortInstallInterruptHandler( XPAR_MICROBLAZE_0_INTC_PUSH_BUTTONS_4BITS_IP2INTC_IRPT_INTR, prvButtonInputInterruptHandler, NULL );\r
{\r
/* Set buttons to input. */\r
XGpio_SetDataDirection( &xInputGPIOInstance, ulGPIOInputChannel, ~( ucSetToOutput ) );\r
- \r
+\r
/* Enable the button input interrupts in the interrupt controller.\r
*NOTE* The vPortEnableInterrupt() API function must be used for this\r
purpose. */\r
{\r
/* vApplicationMallocFailedHook() will only be called if\r
configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook\r
- function that will get called if a call to pvPortMalloc() fails. \r
+ function that will get called if a call to pvPortMalloc() fails.\r
pvPortMalloc() is called internally by the kernel whenever a task, queue or\r
semaphore is created. It is also called by various parts of the demo\r
application. If heap_1.c or heap_2.c are used, then the size of the heap\r
\r
/* vApplicationStackOverflowHook() will only be called if\r
configCHECK_FOR_STACK_OVERFLOW is set to either 1 or 2. The handle and name\r
- of the offending task will be passed into the hook function via its \r
+ of the offending task will be passed into the hook function via its\r
parameters. However, when a stack has overflowed, it is possible that the\r
parameters will have been corrupted, in which case the pxCurrentTCB variable\r
can be inspected directly. */\r
which will have the same timer peripherals defined or available. This example\r
uses the AXI Timer 0. If that is available on your hardware platform then this\r
example callback implementation should not require modification. The name of\r
-the interrupt handler that should be installed is vPortTickISR(), which the \r
+the interrupt handler that should be installed is vPortTickISR(), which the\r
function below declares as an extern. */\r
void vApplicationSetupTimerInterrupt( void )\r
{\r
\r
if( xStatus == XST_SUCCESS )\r
{\r
- /* Install the tick interrupt handler as the timer ISR. \r
+ /* Install the tick interrupt handler as the timer ISR.\r
*NOTE* The xPortInstallInterruptHandler() API function must be used for\r
this purpose. */\r
xStatus = xPortInstallInterruptHandler( XPAR_INTC_0_TMRCTR_0_VEC_ID, vPortTickISR, NULL );\r
\r
/* This is an application defined callback function used to clear whichever\r
interrupt was installed by the the vApplicationSetupTimerInterrupt() callback\r
-function - in this case the interrupt generated by the AXI timer. It is \r
-provided as an application callback because the kernel will run on lots of \r
-different MicroBlaze and FPGA configurations - not all of which will have the \r
-same timer peripherals defined or available. This example uses the AXI Timer 0. \r
-If that is available on your hardware platform then this example callback \r
+function - in this case the interrupt generated by the AXI timer. It is\r
+provided as an application callback because the kernel will run on lots of\r
+different MicroBlaze and FPGA configurations - not all of which will have the\r
+same timer peripherals defined or available. This example uses the AXI Timer 0.\r
+If that is available on your hardware platform then this example callback\r
implementation should not require modification provided the example definition\r
of vApplicationSetupTimerInterrupt() is also not modified. */\r
void vApplicationClearTimerInterrupt( void )\r
projects / freertos / blobdiff