/*\r
- FreeRTOS V7.1.1 - Copyright (C) 2012 Real Time Engineers Ltd.\r
- \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 information, \r
- license 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
+ 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
- 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.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
* See http://www.serialporttool.com/CommEcho.htm for a suitable echo server\r
* for Windows hosts.\r
*\r
- * The timer sends a string to the UART, toggles an LED, then resets itself by \r
- * changing its own period. The period is calculated as a pseudo random number \r
+ * The timer sends a string to the UART, toggles an LED, then resets itself by\r
+ * changing its own period. The period is calculated as a pseudo random number\r
* between comTX_MAX_BLOCK_TIME and comTX_MIN_BLOCK_TIME.\r
*\r
- * The task blocks on an Rx queue waiting for a character to become available. \r
- * Received characters are checked to ensure they match those transmitted by the \r
- * Tx timer. An error is latched if characters are missing, incorrect, or \r
+ * The task blocks on an Rx queue waiting for a character to become available.\r
+ * Received characters are checked to ensure they match those transmitted by the\r
+ * Tx timer. An error is latched if characters are missing, incorrect, or\r
* arrive too slowly.\r
*\r
* How characters are actually transmitted and received is port specific. Demos\r
* that include this test/demo file will provide example drivers. The Tx timer\r
- * executes in the context of the timer service (daemon) task, and must \r
+ * executes in the context of the timer service (daemon) task, and must\r
* therefore never attempt to block.\r
*\r
*/\r
/* The Tx timer transmits the sequence of characters at a pseudo random\r
interval that is capped between comTX_MAX_BLOCK_TIME and\r
comTX_MIN_BLOCK_TIME. */\r
-#define comTX_MAX_BLOCK_TIME ( ( portTickType ) 0x96 )\r
-#define comTX_MIN_BLOCK_TIME ( ( portTickType ) 0x32 )\r
-#define comOFFSET_TIME ( ( portTickType ) 3 )\r
+#define comTX_MAX_BLOCK_TIME ( ( TickType_t ) 0x96 )\r
+#define comTX_MIN_BLOCK_TIME ( ( TickType_t ) 0x32 )\r
+#define comOFFSET_TIME ( ( TickType_t ) 3 )\r
\r
/* States for the simple state machine implemented in the Rx task. */\r
#define comtstWAITING_START_OF_STRING 0\r
to comTX_MIN_BLOCK_TIME to ensure it is never longer than the shortest gap\r
between transmissions. It could be worked out more scientifically from the\r
baud rate being used. */\r
-#define comSHORT_DELAY ( comTX_MIN_BLOCK_TIME >> ( portTickType ) 2 )\r
+#define comSHORT_DELAY ( comTX_MIN_BLOCK_TIME >> ( TickType_t ) 2 )\r
\r
/* The string that is transmitted and received. */\r
#define comTRANSACTED_STRING "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ1234567890"\r
\r
/* A block time of 0 simply means "don't block". */\r
-#define comtstDONT_BLOCK ( portTickType ) 0\r
+#define comtstDONT_BLOCK ( TickType_t ) 0\r
\r
/* Handle to the com port used by both tasks. */\r
static xComPortHandle xPort = NULL;\r
\r
/* The callback function allocated to the transmit timer, as described in the\r
comments at the top of this file. */\r
-static void prvComTxTimerCallback( xTimerHandle xTimer );\r
+static void prvComTxTimerCallback( TimerHandle_t xTimer );\r
\r
/* The receive task as described in the comments at the top of this file. */\r
static void vComRxTask( void *pvParameters );\r
\r
/* The Rx task will toggle LED ( uxBaseLED + comRX_LED_OFFSET). The Tx task\r
will toggle LED ( uxBaseLED + comTX_LED_OFFSET ). */\r
-static unsigned portBASE_TYPE uxBaseLED = 0;\r
+static UBaseType_t uxBaseLED = 0;\r
\r
/* The Rx task toggles uxRxLoops on each successful iteration of its defined\r
function - provided no errors have ever been latched. If this variable stops\r
incrementing, then an error has occurred. */\r
-static volatile unsigned portBASE_TYPE uxRxLoops = 0UL;\r
+static volatile UBaseType_t uxRxLoops = 0UL;\r
\r
/* The timer used to periodically transmit the string. This is the timer that\r
has prvComTxTimerCallback allocated to it as its callback function. */\r
-static xTimerHandle xTxTimer = NULL;\r
+static TimerHandle_t xTxTimer = NULL;\r
\r
/* The string length is held at file scope so the Tx timer does not need to\r
calculate it each time it executes. */\r
\r
/*-----------------------------------------------------------*/\r
\r
-void vStartComTestStringsTasks( unsigned portBASE_TYPE uxPriority, unsigned long ulBaudRate, unsigned portBASE_TYPE uxLED )\r
+void vStartComTestStringsTasks( UBaseType_t uxPriority, uint32_t ulBaudRate, UBaseType_t uxLED )\r
{\r
/* Store values that are used at run time. */\r
uxBaseLED = uxLED;\r
\r
/* Create the Rx task and the Tx timer. The timer is started from the\r
Rx task. */\r
- xTaskCreate( vComRxTask, ( signed char * ) "COMRx", comSTACK_SIZE, NULL, uxPriority, ( xTaskHandle * ) NULL );\r
- xTxTimer = xTimerCreate( ( const signed char * ) "TxTimer", comTX_MIN_BLOCK_TIME, pdFALSE, NULL, prvComTxTimerCallback );\r
+ xTaskCreate( vComRxTask, "COMRx", comSTACK_SIZE, NULL, uxPriority, ( TaskHandle_t * ) NULL );\r
+ xTxTimer = xTimerCreate( "TxTimer", comTX_MIN_BLOCK_TIME, pdFALSE, NULL, prvComTxTimerCallback );\r
configASSERT( xTxTimer );\r
}\r
/*-----------------------------------------------------------*/\r
\r
-static void prvComTxTimerCallback( xTimerHandle xTimer )\r
+static void prvComTxTimerCallback( TimerHandle_t xTimer )\r
{\r
-portTickType xTimeToWait;\r
+TickType_t xTimeToWait;\r
\r
/* The parameter is not used in this case. */\r
( void ) xTimer;\r
sample driver provided with this demo. However - as this is a timer,\r
it executes in the context of the timer task and therefore must not\r
block. */\r
- vSerialPutString( xPort, ( const signed char * const ) comTRANSACTED_STRING, xStringLength );\r
+ vSerialPutString( xPort, comTRANSACTED_STRING, xStringLength );\r
\r
/* Toggle an LED to give a visible indication that another transmission\r
has been performed. */\r
\r
static void vComRxTask( void *pvParameters )\r
{\r
-portBASE_TYPE xState = comtstWAITING_START_OF_STRING, xErrorOccurred = pdFALSE;\r
-signed char *pcExpectedByte, cRxedChar;\r
+BaseType_t xState = comtstWAITING_START_OF_STRING, xErrorOccurred = pdFALSE;\r
+char *pcExpectedByte, cRxedChar;\r
const xComPortHandle xPort = NULL;\r
\r
/* The parameter is not used in this example. */\r
\r
/* The first expected Rx character is the first in the string that is\r
transmitted. */\r
- pcExpectedByte = ( signed char * ) comTRANSACTED_STRING;\r
+ pcExpectedByte = comTRANSACTED_STRING;\r
\r
for( ;; )\r
{\r
xState = comtstWAITING_END_OF_STRING;\r
pcExpectedByte++;\r
\r
- /* Block for a short period. This just allows the Rx queue \r
+ /* Block for a short period. This just allows the Rx queue\r
to contain more than one character, and therefore prevent\r
- thrashing reads to the queue, and repetitive context \r
+ thrashing reads to the queue, and repetitive context\r
switches as each character is received. */\r
vTaskDelay( comSHORT_DELAY );\r
}\r
}\r
\r
/* Go back to wait for the start of the next string. */\r
- pcExpectedByte = ( signed char * ) comTRANSACTED_STRING;\r
+ pcExpectedByte = comTRANSACTED_STRING;\r
xState = comtstWAITING_START_OF_STRING;\r
}\r
else\r
}\r
/*-----------------------------------------------------------*/\r
\r
-portBASE_TYPE xAreComTestTasksStillRunning( void )\r
+BaseType_t xAreComTestTasksStillRunning( void )\r
{\r
-portBASE_TYPE xReturn;\r
+BaseType_t xReturn;\r
\r
/* If the count of successful reception loops has not changed than at\r
some time an error occurred (i.e. a character was received out of sequence)\r
projects / freertos / blobdiff