/*\r
- FreeRTOS V7.3.0 - Copyright (C) 2012 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
- >>>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. FreeRTOS is distributed in the hope that it will be useful, but\r
- WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY\r
- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for\r
- more details. You should have received a copy of the GNU General Public\r
- License and the FreeRTOS license exception along with FreeRTOS; if not it\r
- can be viewed here: http://www.freertos.org/a00114.html and also obtained\r
- by writing to Richard Barry, contact details for whom are available on the\r
- FreeRTOS WEB site.\r
+ Free Software Foundation >>>> AND MODIFIED BY <<<< the FreeRTOS exception.\r
+\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. 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
* *\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
- \r
- http://www.FreeRTOS.org - Documentation, training, latest versions, license \r
- and contact details. \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/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.\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
- Real Time Engineers ltd license FreeRTOS to High Integrity Systems, who sell \r
- the code with commercial support, indemnification, and middleware, under \r
- the OpenRTOS brand: http://www.OpenRTOS.com. High Integrity Systems also\r
- provide a safety engineered and independently SIL3 certified version under \r
- the SafeRTOS brand: http://www.SafeRTOS.com.\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
/*lint -e950 Non ANSI reserved words okay in this file only. */\r
\r
#define portTIMER_EOI_TYPE ( 8 )\r
-#define portRESET_PIC() portOUTPUT_WORD( ( unsigned short ) 0xff22, portTIMER_EOI_TYPE )\r
+#define portRESET_PIC() portOUTPUT_WORD( ( uint16_t ) 0xff22, portTIMER_EOI_TYPE )\r
#define portTIMER_INT_NUMBER 0x12\r
\r
-#define portTIMER_1_CONTROL_REGISTER ( ( unsigned short ) 0xff5e )\r
-#define portTIMER_0_CONTROL_REGISTER ( ( unsigned short ) 0xff56 )\r
-#define portTIMER_INTERRUPT_ENABLE ( ( unsigned short ) 0x2000 )\r
+#define portTIMER_1_CONTROL_REGISTER ( ( uint16_t ) 0xff5e )\r
+#define portTIMER_0_CONTROL_REGISTER ( ( uint16_t ) 0xff56 )\r
+#define portTIMER_INTERRUPT_ENABLE ( ( uint16_t ) 0x2000 )\r
\r
/* Setup the hardware to generate the required tick frequency. */\r
-static void prvSetTickFrequency( unsigned long ulTickRateHz );\r
+static void prvSetTickFrequency( uint32_t ulTickRateHz );\r
\r
/* Set the hardware back to the state as per before the scheduler started. */\r
static void prvExitFunction( void );\r
/*lint -e956 File scopes necessary here. */\r
\r
/* Set true when the vectors are set so the scheduler will service the tick. */\r
-static portBASE_TYPE xSchedulerRunning = pdFALSE;\r
+static BaseType_t xSchedulerRunning = pdFALSE;\r
\r
/* Points to the original routine installed on the vector we use for manual\r
context switches. This is then used to restore the original routine during\r
/*lint +e956 */\r
\r
/*-----------------------------------------------------------*/\r
-portBASE_TYPE xPortStartScheduler( void )\r
+BaseType_t xPortStartScheduler( void )\r
{\r
/* This is called with interrupts already disabled. */\r
\r
static void __interrupt __far prvPreemptiveTick( void )\r
{\r
/* Get the scheduler to update the task states following the tick. */\r
- vTaskIncrementTick();\r
-\r
- /* Switch in the context of the next task to be run. */\r
- portSWITCH_CONTEXT();\r
+ if( xTaskIncrementTick() != pdFALSE )\r
+ {\r
+ /* Switch in the context of the next task to be run. */\r
+ portSWITCH_CONTEXT();\r
+ }\r
\r
/* Reset the PIC ready for the next time. */\r
portRESET_PIC();\r
{\r
/* Same as preemptive tick, but the cooperative scheduler is being used\r
so we don't have to switch in the context of the next task. */\r
- vTaskIncrementTick();\r
+ xTaskIncrementTick();\r
portRESET_PIC();\r
}\r
#endif\r
\r
static void prvExitFunction( void )\r
{\r
-const unsigned short usTimerDisable = 0x0000;\r
-unsigned short usTimer0Control;\r
+const uint16_t usTimerDisable = 0x0000;\r
+uint16_t usTimer0Control;\r
\r
/* Interrupts should be disabled here anyway - but no\r
harm in making sure. */\r
}\r
/*-----------------------------------------------------------*/\r
\r
-static void prvSetTickFrequency( unsigned long ulTickRateHz )\r
+static void prvSetTickFrequency( uint32_t ulTickRateHz )\r
{\r
-const unsigned short usMaxCountRegister = 0xff5a;\r
-const unsigned short usTimerPriorityRegister = 0xff32;\r
-const unsigned short usTimerEnable = 0xC000;\r
-const unsigned short usRetrigger = 0x0001;\r
-const unsigned short usTimerHighPriority = 0x0000;\r
-unsigned short usTimer0Control;\r
+const uint16_t usMaxCountRegister = 0xff5a;\r
+const uint16_t usTimerPriorityRegister = 0xff32;\r
+const uint16_t usTimerEnable = 0xC000;\r
+const uint16_t usRetrigger = 0x0001;\r
+const uint16_t usTimerHighPriority = 0x0000;\r
+uint16_t usTimer0Control;\r
\r
/* ( CPU frequency / 4 ) / clock 2 max count [inpw( 0xff62 ) = 7] */\r
\r
-const unsigned long ulClockFrequency = ( unsigned long ) 0x7f31a0UL;\r
+const uint32_t ulClockFrequency = ( uint32_t ) 0x7f31a0UL;\r
\r
-unsigned long ulTimerCount = ulClockFrequency / ulTickRateHz;\r
+uint32_t ulTimerCount = ulClockFrequency / ulTickRateHz;\r
\r
portOUTPUT_WORD( portTIMER_1_CONTROL_REGISTER, usTimerEnable | portTIMER_INTERRUPT_ENABLE | usRetrigger );\r
- portOUTPUT_WORD( usMaxCountRegister, ( unsigned short ) ulTimerCount );\r
+ portOUTPUT_WORD( usMaxCountRegister, ( uint16_t ) ulTimerCount );\r
portOUTPUT_WORD( usTimerPriorityRegister, usTimerHighPriority );\r
\r
/* Stop the DOS tick - don't do this if you want to maintain a TOD clock. */\r