/*\r
- FreeRTOS V7.4.0 - Copyright (C) 2013 Real Time Engineers Ltd.\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
-\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
- * *\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
- * *\r
- * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *\r
- * *\r
- * Thank you for using FreeRTOS, and thank you for your support! *\r
- * *\r
- ***************************************************************************\r
+ FreeRTOS V9.0.0rc2 - Copyright (C) 2016 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
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
+ ***************************************************************************\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
\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 itcan 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
-\r
- 1 tab == 4 spaces!\r
+ FOR A PARTICULAR PURPOSE. Full license text is available on the following\r
+ link: http://www.freertos.org/a00114.html\r
\r
***************************************************************************\r
* *\r
- * Having a problem? Start by reading the FAQ "My application does *\r
- * not run, what could be wrong?" *\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
- * http://www.FreeRTOS.org/FAQHelp.html *\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
+ http://www.FreeRTOS.org/FAQHelp.html - Having a problem? Start by reading\r
+ the FAQ page "My application does not run, what could be wrong?". Have you\r
+ defined configASSERT()?\r
+\r
+ http://www.FreeRTOS.org/support - In return for receiving this top quality\r
+ embedded software for free we request you assist our global community by\r
+ participating in the support forum.\r
\r
- http://www.FreeRTOS.org - Documentation, books, training, latest versions, \r
- license and Real Time Engineers Ltd. contact details.\r
+ http://www.FreeRTOS.org/training - Investing in training allows your team to\r
+ be as productive as possible as early as possible. Now you can receive\r
+ FreeRTOS training directly from Richard Barry, CEO of Real Time Engineers\r
+ Ltd, and the world's leading authority on the world's leading RTOS.\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.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 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
mission critical applications that require provable dependability.\r
+\r
+ 1 tab == 4 spaces!\r
*/\r
\r
/*\r
* THIS DEMO APPLICATION REQUIRES A LOOPBACK CONNECTOR TO BE FITTED TO THE PIC\r
* USART PORT - connect pin 2 to pin 3 on J2.\r
*\r
- * Instead of the normal single demo application, the PIC18F demo is split \r
- * into several smaller programs of which this is the third. 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 third. 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 RTOSDemo3 project is configured for a PIC18F452 device. Main3.c starts\r
* 5 tasks (including the idle task).\r
- * \r
+ *\r
* The first task repeatedly transmits a string of characters on the PIC USART\r
* port. The second task receives the characters, checking that the correct\r
- * sequence is maintained (i.e. what is transmitted is identical to that \r
- * received). Each transmitted and each received character causes an LED to \r
+ * sequence is maintained (i.e. what is transmitted is identical to that\r
+ * received). Each transmitted and each received character causes an LED to\r
* flash. See demo/common/minimal/comtest. c for more information.\r
*\r
* The third task continuously performs a 32 bit calculation. This is a good\r
- * test of the context switch mechanism as the 8 bit architecture requires \r
+ * test of the context switch mechanism as the 8 bit architecture requires\r
* the use of several file registers to perform the 32 bit operations. See\r
* demo/common/minimal/integer. c for more information.\r
*\r
* The third task is the check task. This periodically checks that the other\r
* tasks are still running and have not experienced any errors. If no errors\r
* have been reported by either the comms or integer tasks an LED is flashed\r
- * with a frequency mainNO_ERROR_CHECK_PERIOD. If an error is discovered the \r
+ * with a frequency mainNO_ERROR_CHECK_PERIOD. If an error is discovered the\r
* frequency is increased to mainERROR_FLASH_RATE.\r
*\r
* The check task also provides a visual indication of a system reset by\r
- * flashing the one remaining LED (mainRESET_LED) when it starts. After \r
+ * flashing the one remaining LED (mainRESET_LED) when it starts. After\r
* this initial flash mainRESET_LED should remain off.\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
/* The period for which mainRESET_LED remain on every reset. */\r
-#define mainRESET_LED_PERIOD ( ( portTickType ) 500 / portTICK_RATE_MS )\r
+#define mainRESET_LED_PERIOD ( ( TickType_t ) 500 / portTICK_PERIOD_MS )\r
\r
/* The LED that is toggled whenever a character is transmitted.\r
mainCOMM_TX_RX_LED + 1 will be toggled every time a character is received. */\r
#define mainCOMM_TX_RX_LED ( ( unsigned portBASE_TYPE ) 2 )\r
\r
-/* The LED that is flashed by the check task at a rate that indicates the \r
+/* The LED that is flashed by the check task at a rate that indicates the\r
error status. */\r
#define mainCHECK_TASK_LED ( ( unsigned portBASE_TYPE ) 1 )\r
\r
#define mainBAUD_RATE ( ( unsigned long ) 57600 )\r
/*-----------------------------------------------------------*/\r
\r
-/* \r
+/*\r
* Task function which periodically checks the other tasks for errors. Flashes\r
- * an LED at a rate that indicates whether an error has ever been detected. \r
+ * an LED at a rate that indicates whether an error has ever been detected.\r
*/\r
static void vErrorChecks( void *pvParameters );\r
\r
vStartIntegerMathTasks( tskIDLE_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. This will never return. */\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
volatile unsigned long ulDummy = 3UL;\r
\r
/* Toggle the LED so we can see when a reset occurs. */\r
xDelayTime = mainERROR_CHECK_PERIOD;\r
}\r
\r
- /* Flash the LED for visual feedback. The rate of the flash will \r
+ /* Flash the LED for visual feedback. The rate of the flash will\r
indicate the health of the system. */\r
vParTestToggleLED( mainCHECK_TASK_LED );\r
}\r
projects / freertos / blobdiff