#define INCLUDE_vTaskDelete 0\r
#define INCLUDE_vTaskCleanUpResources 0\r
#define INCLUDE_vTaskSuspend 1\r
-#define INCLUDE_vTaskDelayUntil 0\r
+#define INCLUDE_vTaskDelayUntil 1\r
#define INCLUDE_vTaskDelay 1\r
#define INCLUDE_xTaskGetIdleTaskHandle 0\r
#define INCLUDE_xTimerGetTimerDaemonTaskHandle 0\r
\r
-#define configASSERT( x ) if( ( x ) == 0 ) vAssertCalled()\r
+#define configASSERT( x ) if( ( x ) == 0 ) { taskDISABLE_INTERRUPTS(); for( ;; ); }\r
\r
\r
#endif /* FREERTOS_CONFIG_H */\r
\r
/* Write in the parameter value. */\r
pulLocal = ( unsigned long * ) pxTopOfStack;\r
- *pulLocal = ( unsigned long ) pvParameters;\r
+ *pulLocal = ( portSTACK_TYPE ) pvParameters;\r
pxTopOfStack--;\r
\r
/* These values are just spacers. The return address of the function\r
\r
void HardwareSetup( void )\r
{\r
-unsigned char ucResetFlag = RESF;
-
portDISABLE_INTERRUPTS();
/* Set fMX */
mission critical applications that require provable dependability.\r
*/\r
\r
-/*\r
+/******************************************************************************\r
+ * This project provides two demo applications. A simple blinky style project,\r
+ * and a more comprehensive test and demo application. The\r
+ * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting (defined in this file) is used to\r
+ * select between the two. The simply blinky demo is implemented and described\r
+ * in main_blinky.c. The more comprehensive test and demo application is\r
+ * implemented and described in main_full.c.\r
+ *\r
+ * This file implements the code that is not demo specific, including the\r
+ * hardware setup and FreeRTOS hook functions.\r
+ *\r
*\r
* ENSURE TO READ THE DOCUMENTATION PAGE FOR THIS PORT AND DEMO APPLICATION ON\r
* THE http://www.FreeRTOS.org WEB SITE FOR FULL INFORMATION ON USING THIS DEMO\r
* APPLICATION, AND ITS ASSOCIATE FreeRTOS ARCHITECTURE PORT!\r
*\r
- *\r
- * main() creates the demo application tasks and timers, then starts the\r
- * scheduler.\r
- *\r
- * This demo is configured to run on the RL78/G13 Promotion Board, which is\r
- * fitted with a R5F100LEA microcontroller. The R5F100LEA contains a little\r
- * under 4K bytes of usable internal RAM. The RAM size restricts the number of\r
- * demo tasks that can be created, and the demo creates 13 tasks, 4 queues and\r
- * two timers. The RL78 range does however include parts with up to 32K bytes\r
- * of RAM (at the time of writing). Using FreeRTOS on such a part will allow an\r
- * application to make a more comprehensive use of FreeRTOS tasks, and other\r
- * FreeRTOS features.\r
- *\r
- * In addition to the standard demo tasks, the following tasks, tests and timers\r
- * are created within this file:\r
- *\r
- * "Reg test" tasks - These fill the registers with known values, then check\r
- * that each register still contains its expected value. Each task uses a\r
- * different set of values. The reg test tasks execute with a very low priority,\r
- * so get preempted very frequently. A register containing an unexpected value\r
- * is indicative of an error in the context switching mechanism.\r
- *\r
- * The "Demo" Timer and Callback Function:\r
- * The demo timer callback function does nothing more than increment a variable.\r
- * The period of the demo timer is set relative to the period of the check timer\r
- * (described below). This allows the check timer to know how many times the\r
- * demo timer callback function should execute between each execution of the\r
- * check timer callback function. The variable incremented in the demo timer\r
- * callback function is used to determine how many times the callback function\r
- * has executed.\r
- *\r
- * The "Check" Timer and Callback Function:\r
- * The check timer period is initially set to three seconds. The check timer\r
- * callback function checks that all the standard demo tasks, the reg test tasks,\r
- * and the demo timer are not only still executing, but are executing without\r
- * reporting any errors. If the check timer discovers that a task or timer has\r
- * stalled, or reported an error, then it changes its own period from the\r
- * initial three seconds, to just 200ms. The check timer callback function also\r
- * toggles the user LED each time it is called. This provides a visual\r
- * indication of the system status: If the LED toggles every three seconds,\r
- * then no issues have been discovered. If the LED toggles every 200ms, then an\r
- * issue has been discovered with at least one task.\r
- *\r
*/\r
\r
/* Scheduler include files. */\r
#include "FreeRTOS.h"\r
#include "task.h"\r
-#include "timers.h"\r
-\r
-/* Standard demo includes. */\r
-#include "dynamic.h"\r
-#include "PollQ.h"\r
-#include "blocktim.h"\r
-\r
-/* Hardware includes. */\r
-#include "port_iodefine.h"\r
-#include "port_iodefine_ext.h"\r
-#include "LED.h"\r
\r
-/* The period at which the check timer will expire, in ms, provided no errors\r
-have been reported by any of the standard demo tasks. ms are converted to the\r
-equivalent in ticks using the portTICK_RATE_MS constant. */\r
-#define mainCHECK_TIMER_PERIOD_MS ( 3000UL / portTICK_RATE_MS )\r
-\r
-/* The period at which the check timer will expire, in ms, if an error has been\r
-reported in one of the standard demo tasks, the check tasks, or the demo timer.\r
-ms are converted to the equivalent in ticks using the portTICK_RATE_MS\r
-constant. */\r
-#define mainERROR_CHECK_TIMER_PERIOD_MS ( 200UL / portTICK_RATE_MS )\r
-\r
-/* These two definitions are used to set the period of the demo timer. The demo\r
-timer period is always relative to the check timer period, so the check timer\r
-can determine if the demo timer has expired the expected number of times between\r
-its own executions. */\r
-#define mainDEMO_TIMER_INCREMENTS_PER_CHECK_TIMER_TIMEOUT ( 100UL )\r
-#define mainDEMO_TIMER_PERIOD_MS ( mainCHECK_TIMER_PERIOD_MS / mainDEMO_TIMER_INCREMENTS_PER_CHECK_TIMER_TIMEOUT )\r
-\r
-/* A block time of zero simple means "don't block". */\r
-#define mainDONT_BLOCK ( 0U )\r
-\r
-/* Values that are passed as parameters into the reg test tasks (purely to\r
-ensure task parameters are passed correctly). */\r
-#define mainREG_TEST_1_PARAMETER ( ( void * ) 0x1234 )\r
-#define mainREG_TEST_2_PARAMETER ( ( void * ) 0x5678 )\r
+/* Set mainCREATE_SIMPLE_BLINKY_DEMO_ONLY to one to run the simple blinky demo,\r
+or 0 to run the more comprehensive test and demo application. */\r
+#define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 0\r
\r
/*-----------------------------------------------------------*/\r
\r
/*\r
- * The 'check' timer callback function, as described at the top of this file.\r
- */\r
-static void prvCheckTimerCallback( xTimerHandle xTimer );\r
-\r
-/*\r
- * The 'demo' timer callback function, as described at the top of this file.\r
- */\r
-static void prvDemoTimerCallback( xTimerHandle xTimer );\r
-\r
-/*\r
- * Functions that define the RegTest tasks, as described at the top of this\r
- * file. The RegTest tasks are written (necessarily) in assembler. Their\r
- * entry points are written in C to allow for easy checking of the task\r
- * parameter values.\r
+ * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.\r
+ * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.\r
*/\r
-extern void vRegTest1Task( void );\r
-extern void vRegTest2Task( void );\r
-static void prvRegTest1Entry( void *pvParameters );\r
-static void prvRegTest2Entry( void *pvParameters );\r
+extern void main_blinky( void );\r
+extern void main_full( void );\r
\r
-/*\r
- * Called if a RegTest task discovers an error as a mechanism to stop the\r
- * tasks loop counter incrementing (so the check task can detect that an\r
- * error exists).\r
- */\r
-void vRegTestError( void );\r
+/* Prototypes for the standard FreeRTOS callback/hook functions implemented\r
+within this file. */\r
+void vApplicationMallocFailedHook( void );\r
+void vApplicationIdleHook( void );\r
+void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName );\r
+void vApplicationTickHook( void );\r
\r
/*-----------------------------------------------------------*/\r
\r
-/* Variables that are incremented on each cycle of the two reg tests to allow\r
-the check timer to know that they are still executing. */\r
-unsigned short usRegTest1LoopCounter = 0, usRegTest2LoopCounter;\r
-\r
-/* The check timer. This uses prvCheckTimerCallback() as its callback\r
-function. */\r
-static xTimerHandle xCheckTimer = NULL;\r
-\r
-/* The demo timer. This uses prvDemoTimerCallback() as its callback function. */\r
-static xTimerHandle xDemoTimer = NULL;\r
-\r
-/* This variable is incremented each time the demo timer expires. */\r
-static volatile unsigned long ulDemoSoftwareTimerCounter = 0UL;\r
-\r
-/*-----------------------------------------------------------*/\r
-\r
-short main( void )\r
+int main( void )\r
{\r
- /* Creates all the tasks and timers, then starts the scheduler. */\r
-\r
- /* First create the 'standard demo' tasks. These are used to demonstrate\r
- API functions being used and also to test the kernel port. More information\r
- is provided on the FreeRTOS.org WEB site. */\r
- vStartDynamicPriorityTasks();\r
- vStartPolledQueueTasks( tskIDLE_PRIORITY );\r
- vCreateBlockTimeTasks();\r
-\r
- /* Create the RegTest tasks as described at the top of this file. */\r
- xTaskCreate( prvRegTest1Entry, "Reg1", configMINIMAL_STACK_SIZE, mainREG_TEST_1_PARAMETER, tskIDLE_PRIORITY, NULL );\r
- xTaskCreate( prvRegTest2Entry, "Reg2", configMINIMAL_STACK_SIZE, mainREG_TEST_2_PARAMETER, tskIDLE_PRIORITY, NULL );\r
-\r
- /* Create the software timer that performs the 'check' functionality,\r
- as described at the top of this file. */\r
- xCheckTimer = xTimerCreate( ( const signed char * ) "CheckTimer",/* A text name, purely to help debugging. */\r
- ( mainCHECK_TIMER_PERIOD_MS ), /* The timer period, in this case 3000ms (3s). */\r
- pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */\r
- ( void * ) 0, /* The ID is not used, so can be set to anything. */\r
- prvCheckTimerCallback /* The callback function that inspects the status of all the other tasks. */\r
- );\r
-\r
- /* Create the software timer that just increments a variable for demo\r
- purposes. */\r
- xDemoTimer = xTimerCreate( ( const signed char * ) "DemoTimer",/* A text name, purely to help debugging. */\r
- ( mainDEMO_TIMER_PERIOD_MS ), /* The timer period, in this case it is always calculated relative to the check timer period (see the definition of mainDEMO_TIMER_PERIOD_MS). */\r
- pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */\r
- ( void * ) 0, /* The ID is not used, so can be set to anything. */\r
- prvDemoTimerCallback /* The callback function that inspects the status of all the other tasks. */\r
- );\r
-\r
- /* Start both the check timer and the demo timer. The timers won't actually\r
- start until the scheduler is started. */\r
- xTimerStart( xCheckTimer, mainDONT_BLOCK );\r
- xTimerStart( xDemoTimer, mainDONT_BLOCK );\r
-\r
- /* Finally start the scheduler running. */\r
- vTaskStartScheduler();\r
-\r
- /* If all is well execution will never reach here as the scheduler will be\r
- running. If this null loop is reached then it is likely there was\r
- insufficient FreeRTOS heap available for the idle task and/or timer task to\r
- be created. See http://www.freertos.org/a00111.html. */\r
- for( ;; );\r
-}\r
-/*-----------------------------------------------------------*/\r
-\r
-static void prvDemoTimerCallback( xTimerHandle xTimer )\r
-{\r
- /* The demo timer has expired. All it does is increment a variable. The\r
- period of the demo timer is relative to that of the check timer, so the\r
- check timer knows how many times this variable should have been incremented\r
- between each execution of the check timer's own callback. */\r
- ulDemoSoftwareTimerCounter++;\r
-}\r
-/*-----------------------------------------------------------*/\r
-\r
-static void prvCheckTimerCallback( xTimerHandle xTimer )\r
-{\r
-static portBASE_TYPE xChangedTimerPeriodAlready = pdFALSE, xErrorStatus = pdPASS;\r
-static unsigned short usLastRegTest1Counter = 0, usLastRegTest2Counter = 0;\r
-\r
- /* Inspect the status of the standard demo tasks. */\r
- if( xAreDynamicPriorityTasksStillRunning() != pdTRUE )\r
+ /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top\r
+ of this file. */\r
+ #if mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1\r
{\r
- xErrorStatus = pdFAIL;\r
+ main_blinky();\r
}\r
-\r
- if( xArePollingQueuesStillRunning() != pdTRUE )\r
- {\r
- xErrorStatus = pdFAIL;\r
- }\r
-\r
- if( xAreBlockTimeTestTasksStillRunning() != pdTRUE )\r
- {\r
- xErrorStatus = pdFAIL;\r
- }\r
-\r
- /* Indicate an error if either of the reg test loop counters have not\r
- incremented since the last time this function was called. */\r
- if( usLastRegTest1Counter == usRegTest1LoopCounter )\r
- {\r
- xErrorStatus = pdFAIL;\r
- }\r
- else\r
- {\r
- usLastRegTest1Counter = usRegTest1LoopCounter;\r
- }\r
-\r
- if( usLastRegTest2Counter == usRegTest2LoopCounter )\r
+ #else\r
{\r
- xErrorStatus = pdFAIL;\r
- }\r
- else\r
- {\r
- usLastRegTest2Counter = usRegTest2LoopCounter;\r
- }\r
-\r
- /* Ensure that the demo software timer has expired\r
- mainDEMO_TIMER_INCREMENTS_PER_CHECK_TIMER_TIMEOUT times in between\r
- each call of this function. A critical section is not required to access\r
- ulDemoSoftwareTimerCounter as the variable is only accessed from another\r
- software timer callback, and only one software timer callback can be\r
- executing at any time. */\r
- if( ( ulDemoSoftwareTimerCounter < ( mainDEMO_TIMER_INCREMENTS_PER_CHECK_TIMER_TIMEOUT - 1 ) ) ||\r
- ( ulDemoSoftwareTimerCounter > ( mainDEMO_TIMER_INCREMENTS_PER_CHECK_TIMER_TIMEOUT + 1 ) )\r
- )\r
- {\r
- xErrorStatus = pdFAIL;\r
- }\r
- else\r
- {\r
- ulDemoSoftwareTimerCounter = 0UL;\r
- }\r
-\r
- if( ( xErrorStatus == pdFAIL ) && ( xChangedTimerPeriodAlready == pdFALSE ) )\r
- {\r
- /* An error has occurred, but the timer's period has not yet been changed,\r
- change it now, and remember that it has been changed. Shortening the\r
- timer's period means the LED will toggle at a faster rate, giving a\r
- visible indication that something has gone wrong. */\r
- xChangedTimerPeriodAlready = pdTRUE;\r
-\r
- /* This call to xTimerChangePeriod() uses a zero block time. Functions\r
- called from inside of a timer callback function must *never* attempt to\r
- block. */\r
- xTimerChangePeriod( xCheckTimer, ( mainERROR_CHECK_TIMER_PERIOD_MS ), mainDONT_BLOCK );\r
+ main_full();\r
}\r
+ #endif\r
\r
- /* Toggle the LED. The toggle rate will depend on whether or not an error\r
- has been found in any tasks. */\r
- LED_BIT = !LED_BIT;\r
-}\r
-/*-----------------------------------------------------------*/\r
-\r
-void vRegTestError( void )\r
-{\r
- /* Called by both reg test tasks if an error is found. There is no way out\r
- of this function so the loop counter of the calling task will stop\r
- incrementing, which will result in the check timer signaling an error. */\r
- for( ;; );\r
+ /* Should not get here. See the definitions of main_blinky() and\r
+ main_full(). */\r
+ return 0;\r
}\r
/*-----------------------------------------------------------*/\r
\r
configTOTAL_HEAP_SIZE value in FreeRTOSConfig.h can be reduced to free up\r
RAM. */\r
xFreeHeapSpace = xPortGetFreeHeapSize();\r
-}\r
-/*-----------------------------------------------------------*/\r
\r
-static void prvRegTest1Entry( void *pvParameters )\r
-{\r
- /* If the parameter has its expected value then start the first reg test\r
- task (this is only done to test that the RTOS port is correctly handling\r
- task parameters. */\r
- if( pvParameters == mainREG_TEST_1_PARAMETER )\r
- {\r
- vRegTest1Task();\r
- }\r
- else\r
- {\r
- vRegTestError();\r
- }\r
-\r
- /* It is not possible to get here as neither of the two functions called\r
- above will ever return. */\r
-}\r
-/*-----------------------------------------------------------*/\r
-\r
-static void prvRegTest2Entry( void *pvParameters )\r
-{\r
- /* If the parameter has its expected value then start the first reg test\r
- task (this is only done to test that the RTOS port is correctly handling\r
- task parameters. */\r
- if( pvParameters == mainREG_TEST_2_PARAMETER )\r
- {\r
- vRegTest2Task();\r
- }\r
- else\r
- {\r
- vRegTestError();\r
- }\r
-\r
- /* It is not possible to get here as neither of the two functions called\r
- above will ever return. */\r
+ /* Remove compiler warning about xFreeHeapSpace being set but never used. */\r
+ ( void ) xFreeHeapSpace;\r
}\r
/*-----------------------------------------------------------*/\r
\r
void vAssertCalled( void )\r
{\r
volatile unsigned long ul = 0;\r
+\r
taskENTER_CRITICAL();\r
{\r
/* Set ul to a non-zero value using the debugger to step out of this\r
--- /dev/null
+/*\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
+\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\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
+ 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
+\r
+ ***************************************************************************\r
+ * *\r
+ * Having a problem? Start by reading the FAQ "My application does *\r
+ * not run, what could be wrong?" *\r
+ * *\r
+ * http://www.FreeRTOS.org/FAQHelp.html *\r
+ * *\r
+ ***************************************************************************\r
+\r
+\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
+ mission critical applications that require provable dependability.\r
+*/\r
+\r
+/******************************************************************************\r
+ * NOTE 1: This project provides two demo applications. A simple blinky style\r
+ * project, and a more comprehensive test and demo application. The\r
+ * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting in main.c is used to select\r
+ * between the two. See the notes on using mainCREATE_SIMPLE_BLINKY_DEMO_ONLY\r
+ * in main.c. This file implements the simply blinky style version.\r
+ *\r
+ * NOTE 2: This file only contains the source code that is specific to the\r
+ * basic demo. Generic functions, such FreeRTOS hook functions, and functions\r
+ * required to configure the hardware, are defined in main.c.\r
+ ******************************************************************************\r
+ *\r
+ * main_blinky() creates one queue, and two tasks. It then starts the\r
+ * scheduler.\r
+ *\r
+ * The Queue Send Task:\r
+ * The queue send task is implemented by the prvQueueSendTask() function in\r
+ * this file. prvQueueSendTask() sits in a loop that causes it to repeatedly\r
+ * block for 200 milliseconds, before sending the value 100 to the queue that\r
+ * was created within main_blinky(). Once the value is sent, the task loops\r
+ * back around to block for another 200 milliseconds.\r
+ *\r
+ * The Queue Receive Task:\r
+ * The queue receive task is implemented by the prvQueueReceiveTask() function\r
+ * in this file. prvQueueReceiveTask() sits in a loop where it repeatedly\r
+ * blocks on attempts to read data from the queue that was created within\r
+ * main_blinky(). When data is received, the task checks the value of the\r
+ * data, and if the value equals the expected 100, toggles the LED. The 'block\r
+ * time' parameter passed to the queue receive function specifies that the\r
+ * task should be held in the Blocked state indefinitely to wait for data to\r
+ * be available on the queue. The queue receive task will only leave the\r
+ * Blocked state when the queue send task writes to the queue. As the queue\r
+ * send task writes to the queue every 200 milliseconds, the queue receive\r
+ * task leaves the Blocked state every 200 milliseconds, and therefore toggles\r
+ * the LED every 200 milliseconds.\r
+ */\r
+\r
+/* Standard includes. */\r
+#include <stdio.h>\r
+\r
+/* Kernel includes. */\r
+#include "FreeRTOS.h"\r
+#include "task.h"\r
+#include "semphr.h"\r
+\r
+/* Eval board specific definitions. */\r
+#include "port_iodefine.h"\r
+#include "port_iodefine_ext.h"\r
+#include "LED.h"\r
+\r
+/* Priorities at which the tasks are created. */\r
+#define mainQUEUE_RECEIVE_TASK_PRIORITY ( tskIDLE_PRIORITY + 2 )\r
+#define mainQUEUE_SEND_TASK_PRIORITY ( tskIDLE_PRIORITY + 1 )\r
+\r
+/* The rate at which data is sent to the queue. The 200ms value is converted\r
+to ticks using the portTICK_RATE_MS constant. */\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, meaning the send task should always find\r
+the queue empty. */\r
+#define mainQUEUE_LENGTH ( 1 )\r
+\r
+\r
+/*-----------------------------------------------------------*/\r
+\r
+/*\r
+ * The tasks as described in the comments at the top of this file.\r
+ */\r
+static void prvQueueReceiveTask( void *pvParameters );\r
+static void prvQueueSendTask( void *pvParameters );\r
+\r
+/*\r
+ * Called by main() to create the simply blinky style application if\r
+ * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.\r
+ */\r
+void main_blinky( void );\r
+\r
+/*-----------------------------------------------------------*/\r
+\r
+/* The queue used by both tasks. */\r
+static xQueueHandle xQueue = NULL;\r
+\r
+/*-----------------------------------------------------------*/\r
+\r
+void main_blinky( void )\r
+{\r
+ /* Create the queue. */\r
+ xQueue = xQueueCreate( mainQUEUE_LENGTH, sizeof( unsigned long ) );\r
+\r
+ if( xQueue != NULL )\r
+ {\r
+ /* Start the two tasks as described in the comments at the top of this\r
+ file. */\r
+ xTaskCreate( prvQueueReceiveTask, /* The function that implements the task. */\r
+ ( signed char * ) "Rx", /* The text name assigned to the task - for debug only as it is not used by the kernel. */\r
+ configMINIMAL_STACK_SIZE, /* The size of the stack to allocate to the task. */\r
+ NULL, /* The parameter passed to the task - not used in this case. */\r
+ mainQUEUE_RECEIVE_TASK_PRIORITY, /* The priority assigned to the task. */\r
+ NULL ); /* The task handle is not required, so NULL is passed. */\r
+\r
+ xTaskCreate( prvQueueSendTask, ( signed char * ) "TX", configMINIMAL_STACK_SIZE, NULL, mainQUEUE_SEND_TASK_PRIORITY, NULL );\r
+\r
+ /* Start the tasks and timer running. */\r
+ vTaskStartScheduler();\r
+ }\r
+\r
+ /* If all is well, the scheduler will now be running, and the following\r
+ line will never be reached. If the following line does execute, then\r
+ there was insufficient FreeRTOS heap memory available for the idle and/or\r
+ timer tasks to be created. See the memory management section on the\r
+ FreeRTOS web site for more details. http://www.freertos.org/a00111.html. */\r
+ for( ;; );\r
+}\r
+/*-----------------------------------------------------------*/\r
+\r
+static void prvQueueSendTask( void *pvParameters )\r
+{\r
+portTickType xNextWakeTime;\r
+const unsigned long ulValueToSend = 100UL;\r
+\r
+ /* Remove compiler warning about unused parameter. */\r
+ ( void ) pvParameters;\r
+\r
+ /* Initialise xNextWakeTime - this only needs to be done once. */\r
+ xNextWakeTime = xTaskGetTickCount();\r
+\r
+ for( ;; )\r
+ {\r
+ /* Place this task in the blocked state until it is time to run again. */\r
+ vTaskDelayUntil( &xNextWakeTime, mainQUEUE_SEND_FREQUENCY_MS );\r
+\r
+ /* Send to the queue - causing the queue receive task to unblock and\r
+ toggle the LED. 0 is used as the block time so the sending operation\r
+ will not block - it shouldn't need to block as the queue should always\r
+ be empty at this point in the code. */\r
+ xQueueSend( xQueue, &ulValueToSend, 0U );\r
+ }\r
+}\r
+/*-----------------------------------------------------------*/\r
+\r
+static void prvQueueReceiveTask( void *pvParameters )\r
+{\r
+unsigned long ulReceivedValue;\r
+const unsigned long ulExpectedValue = 100UL;\r
+\r
+ /* Remove compiler warning about unused parameter. */\r
+ ( void ) pvParameters;\r
+\r
+ for( ;; )\r
+ {\r
+ /* Wait until something arrives in the queue - this task will block\r
+ indefinitely provided INCLUDE_vTaskSuspend is set to 1 in\r
+ FreeRTOSConfig.h. */\r
+ xQueueReceive( xQueue, &ulReceivedValue, portMAX_DELAY );\r
+\r
+ /* To get here something must have been received from the queue, but\r
+ is it the expected value? If it is, toggle the LED. */\r
+ if( ulReceivedValue == ulExpectedValue )\r
+ {\r
+ LED_BIT = !LED_BIT;\r
+ ulReceivedValue = 0U;\r
+ }\r
+ }\r
+}\r
+/*-----------------------------------------------------------*/\r
+\r
--- /dev/null
+/*\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
+\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\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
+ 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
+\r
+ ***************************************************************************\r
+ * *\r
+ * Having a problem? Start by reading the FAQ "My application does *\r
+ * not run, what could be wrong?" *\r
+ * *\r
+ * http://www.FreeRTOS.org/FAQHelp.html *\r
+ * *\r
+ ***************************************************************************\r
+\r
+\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
+ mission critical applications that require provable dependability.\r
+*/\r
+\r
+/******************************************************************************\r
+ * NOTE 1: This project provides two demo applications. A simple blinky style\r
+ * project, and a more comprehensive test and demo application. The\r
+ * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting in main.c is used to select\r
+ * between the two. See the notes on using mainCREATE_SIMPLE_BLINKY_DEMO_ONLY\r
+ * in main.c. This file implements the comprehensive test and demo version.\r
+ *\r
+ * NOTE 2: This file only contains the source code that is specific to the\r
+ * full demo. Generic functions, such FreeRTOS hook functions, and functions\r
+ * required to configure the hardware, are defined in main.c.\r
+ ******************************************************************************\r
+ *\r
+ * main_full() creates all the demo application tasks and two software timers,\r
+ * then starts the scheduler. The web documentation provides more details of\r
+ * the standard demo application tasks, which provide no particular\r
+ * functionality, but do provide a good example of how to use the FreeRTOS API.\r
+ *\r
+ * In addition to the standard demo tasks, the following tasks, tests and\r
+ * timers are created within this file:\r
+ *\r
+ * "Reg test" tasks - These fill the registers with known values, then check\r
+ * that each register still contains its expected value. Each task uses a\r
+ * different set of values. The reg test tasks execute with a very low priority,\r
+ * so get preempted very frequently. A register containing an unexpected value\r
+ * is indicative of an error in the context switching mechanism.\r
+ *\r
+ * The "Demo" Timer and Callback Function:\r
+ * The demo timer callback function does nothing more than increment a variable.\r
+ * The period of the demo timer is set relative to the period of the check timer\r
+ * (described below). This allows the check timer to know how many times the\r
+ * demo timer callback function should execute between each execution of the\r
+ * check timer callback function. The variable incremented in the demo timer\r
+ * callback function is used to determine how many times the callback function\r
+ * has executed.\r
+ *\r
+ * The "Check" Timer and Callback Function:\r
+ * The check timer period is initially set to three seconds. The check timer\r
+ * callback function checks that all the standard demo tasks, the reg test\r
+ * tasks, and the demo timer are not only still executing, but are executing\r
+ * without reporting any errors. If the check timer discovers that a task or\r
+ * timer has stalled, or reported an error, then it changes its own period from\r
+ * the initial three seconds, to just 200ms. The check timer callback function\r
+ * also toggles an LED each time it is called. This provides a visual\r
+ * indication of the system status: If the LED toggles every three seconds,\r
+ * then no issues have been discovered. If the LED toggles every 200ms, then\r
+ * an issue has been discovered with at least one task.\r
+ *\r
+ * ENSURE TO READ THE DOCUMENTATION PAGE FOR THIS PORT AND DEMO APPLICATION ON\r
+ * THE http://www.FreeRTOS.org WEB SITE FOR FULL INFORMATION ON USING THIS DEMO\r
+ * APPLICATION, AND ITS ASSOCIATE FreeRTOS ARCHITECTURE PORT!\r
+ *\r
+ */\r
+\r
+/* Scheduler include files. */\r
+#include "FreeRTOS.h"\r
+#include "task.h"\r
+#include "timers.h"\r
+\r
+/* Standard demo includes. */\r
+#include "dynamic.h"\r
+#include "PollQ.h"\r
+#include "blocktim.h"\r
+\r
+/* Hardware includes. */\r
+#include "port_iodefine.h"\r
+#include "port_iodefine_ext.h"\r
+#include "LED.h"\r
+\r
+/* The period at which the check timer will expire, in ms, provided no errors\r
+have been reported by any of the standard demo tasks. ms are converted to the\r
+equivalent in ticks using the portTICK_RATE_MS constant. */\r
+#define mainCHECK_TIMER_PERIOD_MS ( 3000UL / portTICK_RATE_MS )\r
+\r
+/* The period at which the check timer will expire, in ms, if an error has been\r
+reported in one of the standard demo tasks, the check tasks, or the demo timer.\r
+ms are converted to the equivalent in ticks using the portTICK_RATE_MS\r
+constant. */\r
+#define mainERROR_CHECK_TIMER_PERIOD_MS ( 200UL / portTICK_RATE_MS )\r
+\r
+/* These two definitions are used to set the period of the demo timer. The demo\r
+timer period is always relative to the check timer period, so the check timer\r
+can determine if the demo timer has expired the expected number of times between\r
+its own executions. */\r
+#define mainDEMO_TIMER_INCREMENTS_PER_CHECK_TIMER_TIMEOUT ( 100UL )\r
+#define mainDEMO_TIMER_PERIOD_MS ( mainCHECK_TIMER_PERIOD_MS / mainDEMO_TIMER_INCREMENTS_PER_CHECK_TIMER_TIMEOUT )\r
+\r
+/* A block time of zero simply means "don't block". */\r
+#define mainDONT_BLOCK ( 0U )\r
+\r
+/* Values that are passed as parameters into the reg test tasks (purely to\r
+ensure task parameters are passed correctly). */\r
+#define mainREG_TEST_1_PARAMETER ( ( void * ) 0x1234 )\r
+#define mainREG_TEST_2_PARAMETER ( ( void * ) 0x5678 )\r
+\r
+/*-----------------------------------------------------------*/\r
+\r
+/*\r
+ * The 'check' timer callback function, as described at the top of this file.\r
+ */\r
+static void prvCheckTimerCallback( xTimerHandle xTimer );\r
+\r
+/*\r
+ * The 'demo' timer callback function, as described at the top of this file.\r
+ */\r
+static void prvDemoTimerCallback( xTimerHandle xTimer );\r
+\r
+/*\r
+ * Functions that define the RegTest tasks, as described at the top of this\r
+ * file. The RegTest tasks are written (necessarily) in assembler. Their\r
+ * entry points are written in C to allow for easy checking of the task\r
+ * parameter values.\r
+ */\r
+extern void vRegTest1Task( void );\r
+extern void vRegTest2Task( void );\r
+static void prvRegTest1Entry( void *pvParameters );\r
+static void prvRegTest2Entry( void *pvParameters );\r
+\r
+/*\r
+ * Called if a RegTest task discovers an error as a mechanism to stop the\r
+ * tasks loop counter incrementing (so the check task can detect that an\r
+ * error exists).\r
+ */\r
+void vRegTestError( void );\r
+\r
+/*\r
+ * Called by main() to create the more comprehensive application if\r
+ * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.\r
+ */\r
+void main_full( void );\r
+\r
+/*-----------------------------------------------------------*/\r
+\r
+/* Variables that are incremented on each cycle of the two reg tests to allow\r
+the check timer to know that they are still executing. */\r
+unsigned short usRegTest1LoopCounter = 0, usRegTest2LoopCounter;\r
+\r
+/* The check timer. This uses prvCheckTimerCallback() as its callback\r
+function. */\r
+static xTimerHandle xCheckTimer = NULL;\r
+\r
+/* The demo timer. This uses prvDemoTimerCallback() as its callback function. */\r
+static xTimerHandle xDemoTimer = NULL;\r
+\r
+/* This variable is incremented each time the demo timer expires. */\r
+static volatile unsigned long ulDemoSoftwareTimerCounter = 0UL;\r
+\r
+/*-----------------------------------------------------------*/\r
+\r
+void main_full( void )\r
+{\r
+ /* Creates all the tasks and timers, then starts the scheduler. */\r
+\r
+ /* First create the 'standard demo' tasks. These are used to demonstrate\r
+ API functions being used and also to test the kernel port. More information\r
+ is provided on the FreeRTOS.org WEB site. */\r
+ vStartDynamicPriorityTasks();\r
+ vStartPolledQueueTasks( tskIDLE_PRIORITY );\r
+ vCreateBlockTimeTasks();\r
+\r
+ /* Create the RegTest tasks as described at the top of this file. */\r
+ xTaskCreate( prvRegTest1Entry, /* The function that implements the task. */\r
+ ( const signed char * ) "Reg1",/* Text name for the task - to assist debugging only, not used by the kernel. */\r
+ configMINIMAL_STACK_SIZE, /* The size of the stack allocated to the task (in words, not bytes). */\r
+ mainREG_TEST_1_PARAMETER, /* The parameter passed into the task. */\r
+ tskIDLE_PRIORITY, /* The priority at which the task will execute. */\r
+ NULL ); /* Used to pass the handle of the created task out to the function caller - not used in this case. */\r
+\r
+ xTaskCreate( prvRegTest2Entry, ( const signed char * ) "Reg2", configMINIMAL_STACK_SIZE, mainREG_TEST_2_PARAMETER, tskIDLE_PRIORITY, NULL );\r
+\r
+ /* Create the software timer that performs the 'check' functionality,\r
+ as described at the top of this file. */\r
+ xCheckTimer = xTimerCreate( ( const signed char * ) "CheckTimer",/* A text name, purely to help debugging. */\r
+ ( mainCHECK_TIMER_PERIOD_MS ), /* The timer period, in this case 3000ms (3s). */\r
+ pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */\r
+ ( void * ) 0, /* The ID is not used, so can be set to anything. */\r
+ prvCheckTimerCallback /* The callback function that inspects the status of all the other tasks. */\r
+ );\r
+\r
+ /* Create the software timer that just increments a variable for demo\r
+ purposes. */\r
+ xDemoTimer = xTimerCreate( ( const signed char * ) "DemoTimer",/* A text name, purely to help debugging. */\r
+ ( mainDEMO_TIMER_PERIOD_MS ), /* The timer period, in this case it is always calculated relative to the check timer period (see the definition of mainDEMO_TIMER_PERIOD_MS). */\r
+ pdTRUE, /* This is an auto-reload timer, so xAutoReload is set to pdTRUE. */\r
+ ( void * ) 0, /* The ID is not used, so can be set to anything. */\r
+ prvDemoTimerCallback /* The callback function that inspects the status of all the other tasks. */\r
+ );\r
+\r
+ /* Start both the check timer and the demo timer. The timers won't actually\r
+ start until the scheduler is started. */\r
+ xTimerStart( xCheckTimer, mainDONT_BLOCK );\r
+ xTimerStart( xDemoTimer, mainDONT_BLOCK );\r
+\r
+ /* Finally start the scheduler running. */\r
+ vTaskStartScheduler();\r
+\r
+ /* If all is well execution will never reach here as the scheduler will be\r
+ running. If this null loop is reached then it is likely there was\r
+ insufficient FreeRTOS heap available for the idle task and/or timer task to\r
+ be created. See http://www.freertos.org/a00111.html. */\r
+ for( ;; );\r
+}\r
+/*-----------------------------------------------------------*/\r
+\r
+static void prvDemoTimerCallback( xTimerHandle xTimer )\r
+{\r
+ /* Remove compiler warning about unused parameter. */\r
+ ( void ) xTimer;\r
+\r
+ /* The demo timer has expired. All it does is increment a variable. The\r
+ period of the demo timer is relative to that of the check timer, so the\r
+ check timer knows how many times this variable should have been incremented\r
+ between each execution of the check timer's own callback. */\r
+ ulDemoSoftwareTimerCounter++;\r
+}\r
+/*-----------------------------------------------------------*/\r
+\r
+static void prvCheckTimerCallback( xTimerHandle xTimer )\r
+{\r
+static portBASE_TYPE xChangedTimerPeriodAlready = pdFALSE, xErrorStatus = pdPASS;\r
+static unsigned short usLastRegTest1Counter = 0, usLastRegTest2Counter = 0;\r
+\r
+ /* Remove compiler warning about unused parameter. */\r
+ ( void ) xTimer;\r
+\r
+ /* Inspect the status of the standard demo tasks. */\r
+ if( xAreDynamicPriorityTasksStillRunning() != pdTRUE )\r
+ {\r
+ xErrorStatus = pdFAIL;\r
+ }\r
+\r
+ if( xArePollingQueuesStillRunning() != pdTRUE )\r
+ {\r
+ xErrorStatus = pdFAIL;\r
+ }\r
+\r
+ if( xAreBlockTimeTestTasksStillRunning() != pdTRUE )\r
+ {\r
+ xErrorStatus = pdFAIL;\r
+ }\r
+\r
+ /* Indicate an error if either of the reg test loop counters have not\r
+ incremented since the last time this function was called. */\r
+ if( usLastRegTest1Counter == usRegTest1LoopCounter )\r
+ {\r
+ xErrorStatus = pdFAIL;\r
+ }\r
+ else\r
+ {\r
+ usLastRegTest1Counter = usRegTest1LoopCounter;\r
+ }\r
+\r
+ if( usLastRegTest2Counter == usRegTest2LoopCounter )\r
+ {\r
+ xErrorStatus = pdFAIL;\r
+ }\r
+ else\r
+ {\r
+ usLastRegTest2Counter = usRegTest2LoopCounter;\r
+ }\r
+\r
+ /* Ensure that the demo software timer has expired\r
+ mainDEMO_TIMER_INCREMENTS_PER_CHECK_TIMER_TIMEOUT times in between\r
+ each call of this function. A critical section is not required to access\r
+ ulDemoSoftwareTimerCounter as the variable is only accessed from another\r
+ software timer callback, and only one software timer callback can be\r
+ executing at any time. */\r
+ if( ( ulDemoSoftwareTimerCounter < ( mainDEMO_TIMER_INCREMENTS_PER_CHECK_TIMER_TIMEOUT - 1 ) ) ||\r
+ ( ulDemoSoftwareTimerCounter > ( mainDEMO_TIMER_INCREMENTS_PER_CHECK_TIMER_TIMEOUT + 1 ) )\r
+ )\r
+ {\r
+ xErrorStatus = pdFAIL;\r
+ }\r
+ else\r
+ {\r
+ ulDemoSoftwareTimerCounter = 0UL;\r
+ }\r
+\r
+ if( ( xErrorStatus == pdFAIL ) && ( xChangedTimerPeriodAlready == pdFALSE ) )\r
+ {\r
+ /* An error has occurred, but the timer's period has not yet been changed,\r
+ change it now, and remember that it has been changed. Shortening the\r
+ timer's period means the LED will toggle at a faster rate, giving a\r
+ visible indication that something has gone wrong. */\r
+ xChangedTimerPeriodAlready = pdTRUE;\r
+\r
+ /* This call to xTimerChangePeriod() uses a zero block time. Functions\r
+ called from inside of a timer callback function must *never* attempt to\r
+ block. */\r
+ xTimerChangePeriod( xCheckTimer, ( mainERROR_CHECK_TIMER_PERIOD_MS ), mainDONT_BLOCK );\r
+ }\r
+\r
+ /* Toggle the LED. The toggle rate will depend on whether or not an error\r
+ has been found in any tasks. */\r
+ LED_BIT = !LED_BIT;\r
+}\r
+/*-----------------------------------------------------------*/\r
+\r
+void vRegTestError( void )\r
+{\r
+ /* Called by both reg test tasks if an error is found. There is no way out\r
+ of this function so the loop counter of the calling task will stop\r
+ incrementing, which will result in the check timer signaling an error. */\r
+ for( ;; );\r
+}\r
+/*-----------------------------------------------------------*/\r
+\r
+static void prvRegTest1Entry( void *pvParameters )\r
+{\r
+ /* If the parameter has its expected value then start the first reg test\r
+ task (this is only done to test that the RTOS port is correctly handling\r
+ task parameters. */\r
+ if( pvParameters == mainREG_TEST_1_PARAMETER )\r
+ {\r
+ vRegTest1Task();\r
+ }\r
+ else\r
+ {\r
+ vRegTestError();\r
+ }\r
+\r
+ /* It is not possible to get here as neither of the two functions called\r
+ above will ever return. */\r
+}\r
+/*-----------------------------------------------------------*/\r
+\r
+static void prvRegTest2Entry( void *pvParameters )\r
+{\r
+ /* If the parameter has its expected value then start the first reg test\r
+ task (this is only done to test that the RTOS port is correctly handling\r
+ task parameters. */\r
+ if( pvParameters == mainREG_TEST_2_PARAMETER )\r
+ {\r
+ vRegTest2Task();\r
+ }\r
+ else\r
+ {\r
+ vRegTestError();\r
+ }\r
+\r
+ /* It is not possible to get here as neither of the two functions called\r
+ above will ever return. */\r
+}\r
+/*-----------------------------------------------------------*/\r
+\r
/* */
/* This file is generated by e2studio. */
/* */
-/***********************************************************************/ \r
+/***********************************************************************/\r
\r
#include "interrupt_handlers.h"\r
\r
extern void vPortTickISR( void );
extern void vPortYield( void );\r
-#warning Check the options bytes.\r
const unsigned char Option_Bytes[] __attribute__ ((section (".option_bytes"))) = {\r
- 0x6e, 0xff, 0xe8, 0x85 /* 0x00U, 0xFFU, 0xF8U, 0x81U */\r
+ 0x6e, 0xff, 0xe8, 0x85\r
};\r
\r
const unsigned char Security_Id[] __attribute__ ((section (".security_id"))) = {\r
projects / freertos / commitdiff