/*\r
- FreeRTOS V7.5.3 - Copyright (C) 2013 Real Time Engineers Ltd. \r
+ FreeRTOS V8.2.0rc1 - Copyright (C) 2014 Real Time Engineers Ltd.\r
All rights reserved\r
\r
VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.\r
\r
- ***************************************************************************\r
- * *\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
- * 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
- * Thank you! *\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
\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
+ >>! NOTE: The modification to the GPL is included to allow you to !<<\r
+ >>! distribute a combined work that includes FreeRTOS without being !<<\r
+ >>! obliged to provide the source code for proprietary components !<<\r
+ >>! outside of the FreeRTOS 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. Full license text is available from the following\r
+ FOR A PARTICULAR PURPOSE. Full license text is available on the following\r
link: http://www.freertos.org/a00114.html\r
\r
1 tab == 4 spaces!\r
***************************************************************************\r
* *\r
* Having a problem? Start by reading the FAQ "My application does *\r
- * not run, what could be wrong?" *\r
+ * not run, what could be wrong?". Have you defined configASSERT()? *\r
* *\r
* http://www.FreeRTOS.org/FAQHelp.html *\r
* *\r
***************************************************************************\r
\r
+ ***************************************************************************\r
+ * *\r
+ * FreeRTOS provides completely free yet professionally developed, *\r
+ * robust, strictly quality controlled, supported, and cross *\r
+ * platform software that is more than just the market leader, it *\r
+ * is the industry's de facto standard. *\r
+ * *\r
+ * Help yourself get started quickly while simultaneously helping *\r
+ * to support the FreeRTOS project by purchasing a FreeRTOS *\r
+ * tutorial book, reference manual, or both: *\r
+ * http://www.FreeRTOS.org/Documentation *\r
+ * *\r
+ ***************************************************************************\r
+\r
+ ***************************************************************************\r
+ * *\r
+ * Investing in training allows your team to be as productive as *\r
+ * possible as early as possible, lowering your overall development *\r
+ * cost, and enabling you to bring a more robust product to market *\r
+ * earlier than would otherwise be possible. Richard Barry is both *\r
+ * the architect and key author of FreeRTOS, and so also the world's *\r
+ * leading authority on what is the world's most popular real time *\r
+ * kernel for deeply embedded MCU designs. Obtaining your training *\r
+ * from Richard ensures your team will gain directly from his in-depth *\r
+ * product knowledge and years of usage experience. Contact Real Time *\r
+ * Engineers Ltd to enquire about the FreeRTOS Masterclass, presented *\r
+ * by Richard Barry: http://www.FreeRTOS.org/contact\r
+ * *\r
+ ***************************************************************************\r
+\r
+ ***************************************************************************\r
+ * *\r
+ * You are receiving this top quality software for free. Please play *\r
+ * fair and reciprocate by reporting any suspected issues and *\r
+ * participating in the community forum: *\r
+ * http://www.FreeRTOS.org/support *\r
+ * *\r
+ * Thank you! *\r
+ * *\r
+ ***************************************************************************\r
+\r
http://www.FreeRTOS.org - Documentation, books, training, latest versions,\r
license and Real Time Engineers Ltd. contact details.\r
\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.FreeRTOS.org/labs - Where new FreeRTOS products go to incubate.\r
+ Come and try FreeRTOS+TCP, our new open source TCP/IP stack for FreeRTOS.\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
+ Integrity Systems ltd. to sell under the OpenRTOS brand. Low cost OpenRTOS\r
+ licenses offer ticketed support, indemnification and commercial 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
*/\r
\r
/*\r
- * Instead of the normal single demo application, the PIC18F demo is split \r
- * into several smaller programs of which this is the first. This enables the \r
- * demo's to be executed on the RAM limited 40 pin devices. The 64 and 80 pin \r
- * devices require a more costly development platform and are not so readily \r
+ * Instead of the normal single demo application, the PIC18F demo is split\r
+ * into several smaller programs of which this is the first. This enables the\r
+ * demo's to be executed on the RAM limited 40 pin devices. The 64 and 80 pin\r
+ * devices require a more costly development platform and are not so readily\r
* available.\r
*\r
- * The RTOSDemo1 project is configured for a PIC18F452 device. Main1.c starts 5 \r
+ * The RTOSDemo1 project is configured for a PIC18F452 device. Main1.c starts 5\r
* tasks (including the idle task).\r
*\r
- * The first task runs at the idle priority. It repeatedly performs a 32bit \r
- * calculation and checks it's result against the expected value. This checks \r
- * that the temporary storage utilised by the compiler to hold intermediate \r
- * results does not get corrupted when the task gets switched in and out. See \r
+ * The first task runs at the idle priority. It repeatedly performs a 32bit\r
+ * calculation and checks it's result against the expected value. This checks\r
+ * that the temporary storage utilised by the compiler to hold intermediate\r
+ * results does not get corrupted when the task gets switched in and out. See\r
* demo/common/minimal/integer.c for more information.\r
*\r
- * The second and third tasks pass an incrementing value between each other on \r
+ * The second and third tasks pass an incrementing value between each other on\r
* a message queue. See demo/common/minimal/PollQ.c for more information.\r
*\r
- * Main1.c also creates a check task. This periodically checks that all the \r
- * other tasks are still running and have not experienced any unexpected \r
- * results. If all the other tasks are executing correctly an LED is flashed \r
- * once every mainCHECK_PERIOD milliseconds. If any of the tasks have not \r
- * executed, or report and error, the frequency of the LED flash will increase \r
+ * Main1.c also creates a check task. This periodically checks that all the\r
+ * other tasks are still running and have not experienced any unexpected\r
+ * results. If all the other tasks are executing correctly an LED is flashed\r
+ * once every mainCHECK_PERIOD milliseconds. If any of the tasks have not\r
+ * executed, or report and error, the frequency of the LED flash will increase\r
* to mainERROR_FLASH_RATE.\r
*\r
* On entry to main an 'X' is transmitted. Monitoring the serial port using a\r
- * dumb terminal allows for verification that the device is not continuously \r
+ * dumb terminal allows for verification that the device is not continuously\r
* being reset (no more than one 'X' should be transmitted).\r
*\r
- * http://www.FreeRTOS.org contains important information on the use of the \r
+ * http://www.FreeRTOS.org contains important information on the use of the\r
* PIC18F port.\r
*/\r
\r
Changes from V2.0.0\r
\r
+ Delay periods are now specified using variables and constants of\r
- portTickType rather than unsigned long.\r
+ TickType_t rather than unsigned long.\r
*/\r
\r
/* Scheduler include files. */\r
/* The period between executions of the check task before and after an error\r
has been discovered. If an error has been discovered the check task runs\r
more frequently - increasing the LED flash rate. */\r
-#define mainNO_ERROR_CHECK_PERIOD ( ( portTickType ) 1000 / portTICK_RATE_MS )\r
-#define mainERROR_CHECK_PERIOD ( ( portTickType ) 100 / portTICK_RATE_MS )\r
+#define mainNO_ERROR_CHECK_PERIOD ( ( TickType_t ) 1000 / portTICK_PERIOD_MS )\r
+#define mainERROR_CHECK_PERIOD ( ( TickType_t ) 100 / portTICK_PERIOD_MS )\r
\r
/* Priority definitions for some of the tasks. Other tasks just use the idle\r
priority. */\r
/* The LED that is flashed by the check task. */\r
#define mainCHECK_TASK_LED ( 0 )\r
\r
-/* Constants required for the communications. Only one character is ever \r
+/* Constants required for the communications. Only one character is ever\r
transmitted. */\r
#define mainCOMMS_QUEUE_LENGTH ( 5 )\r
-#define mainNO_BLOCK ( ( portTickType ) 0 )\r
+#define mainNO_BLOCK ( ( TickType_t ) 0 )\r
#define mainBAUD_RATE ( ( unsigned long ) 9600 )\r
\r
/*\r
vStartPolledQueueTasks( mainQUEUE_POLL_PRIORITY );\r
\r
/* Start the check task defined in this file. */\r
- xTaskCreate( vErrorChecks, ( const char * const ) "Check", configMINIMAL_STACK_SIZE, NULL, mainCHECK_TASK_PRIORITY, NULL );\r
+ xTaskCreate( vErrorChecks, "Check", configMINIMAL_STACK_SIZE, NULL, mainCHECK_TASK_PRIORITY, NULL );\r
\r
/* Start the scheduler. Will never return here. */\r
vTaskStartScheduler();\r
\r
static void vErrorChecks( void *pvParameters )\r
{\r
-portTickType xDelayTime = mainNO_ERROR_CHECK_PERIOD;\r
+TickType_t xDelayTime = mainNO_ERROR_CHECK_PERIOD;\r
portBASE_TYPE xErrorOccurred;\r
\r
/* Cycle for ever, delaying then checking all the other tasks are still\r