/*\r
- FreeRTOS V7.6.0 - Copyright (C) 2013 Real Time Engineers Ltd. \r
+ FreeRTOS V7.6.0 - Copyright (C) 2013 Real Time Engineers Ltd.\r
All rights reserved\r
\r
VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.\r
* required to configure the hardware, are defined in main.c.\r
******************************************************************************\r
*\r
- * main_full() creates all the demo application tasks and software timers, then \r
- * starts the scheduler. The WEB documentation provides more details of the \r
- * standard demo application tasks. In addition to the standard demo tasks, the \r
+ * main_full() creates all the demo application tasks and software timers, then\r
+ * starts the scheduler. The WEB documentation provides more details of the\r
+ * standard demo application tasks. In addition to the standard demo tasks, the\r
* following tasks and tests are defined and/or created within this file:\r
*\r
* "LCD" task - the LCD task is a 'gatekeeper' task. It is the only task that\r
* the check software timer discovers that a task has either stalled, or\r
* reported an error, then it changes its own execution period from the initial\r
* three seconds, to just 200ms. The check software timer callback function\r
- * also writes a status message to the LCD (via the LCD task). If all the demo \r
- * tasks are executing with their expected behaviour then the check task writes \r
+ * also writes a status message to the LCD (via the LCD task). If all the demo\r
+ * tasks are executing with their expected behaviour then the check task writes\r
* a count of the number of times the high frequency interrupt has incremented\r
* ulHighFrequencyTimerInterrupts - which is one in every 20,000 interrupts.\r
*\r
* "Register test" tasks - These tasks are used in part to test the kernel port.\r
- * They set each processor register to a known value, then check that the \r
+ * They set each processor register to a known value, then check that the\r
* register still contains that value. Each of the tasks sets the registers\r
- * to different values, and will get swapping in and out between setting and \r
+ * to different values, and will get swapping in and out between setting and\r
* then subsequently checking the register values. Discovery of an incorrect\r
* value would be indicative of an error in the task switching mechanism.\r
*\r
- * By way of demonstration, the demo application defines \r
- * configMAX_SYSCALL_INTERRUPT_PRIORITY to be 3, configKERNEL_INTERRUPT_PRIORITY \r
+ * By way of demonstration, the demo application defines\r
+ * configMAX_SYSCALL_INTERRUPT_PRIORITY to be 3, configKERNEL_INTERRUPT_PRIORITY\r
* to be 1, and all other interrupts as follows:\r
*\r
- * + The UART is allocated a priority of 2. This means it can interrupt the \r
+ * + The UART is allocated a priority of 2. This means it can interrupt the\r
* RTOS tick, and can also safely use queues.\r
- * + Two timers are configured to generate interrupts just to test the nesting \r
- * and queue access mechanisms. These timers are allocated priorities 2 and 3 \r
- * respectively. Even though they both access the same two queues, the \r
- * priority 3 interrupt can safely interrupt the priority 2 interrupt. Both \r
+ * + Two timers are configured to generate interrupts just to test the nesting\r
+ * and queue access mechanisms. These timers are allocated priorities 2 and 3\r
+ * respectively. Even though they both access the same two queues, the\r
+ * priority 3 interrupt can safely interrupt the priority 2 interrupt. Both\r
* can interrupt the RTOS tick.\r
- * + Finally a high frequency timer interrupt is configured to use priority 4 - \r
- * therefore kernel activity will never prevent the high frequency timer from \r
- * executing immediately that the interrupt is raised (within the limitations \r
- * of the hardware itself). It would not be safe to access a queue from this \r
- * interrupt as it is above configMAX_SYSCALL_INTERRUPT_PRIORITY. \r
+ * + Finally a high frequency timer interrupt is configured to use priority 4 -\r
+ * therefore kernel activity will never prevent the high frequency timer from\r
+ * executing immediately that the interrupt is raised (within the limitations\r
+ * of the hardware itself). It would not be safe to access a queue from this\r
+ * interrupt as it is above configMAX_SYSCALL_INTERRUPT_PRIORITY.\r
*\r
* See the online documentation for this demo for more information on interrupt\r
* usage.\r
/* Misc. */\r
#define mainDONT_BLOCK ( 0 )\r
\r
-/* Dimension the buffer used to hold the value of the high frequency timer \r
+/* Dimension the buffer used to hold the value of the high frequency timer\r
count when it is converted to a string. */\r
#define mainMAX_STRING_LENGTH ( 20 )\r
\r
/* The frequency at which the "fast interrupt test" interrupt will occur. */\r
#define mainTEST_INTERRUPT_FREQUENCY ( 20000 )\r
\r
-/* The number of timer clocks expected to occur between each "fast interrupt \r
+/* The number of timer clocks expected to occur between each "fast interrupt\r
test" interrupt. */\r
#define mainEXPECTED_CLOCKS_BETWEEN_INTERRUPTS ( ( configCPU_CLOCK_HZ >> 1 ) / mainTEST_INTERRUPT_FREQUENCY )\r
\r
static void prvSetupHighFrequencyTimerTest( xTimerHandle xTimer );\r
\r
/*\r
- * Tasks that test the context switch mechanism by filling the processor \r
+ * Tasks that test the context switch mechanism by filling the processor\r
* registers with known values, then checking that the values contained\r
* within the registers is as expected. The tasks are likely to get swapped\r
* in and out between setting the register values and checking the register\r
- * values. \r
+ * values.\r
*/\r
static void prvRegTestTask1( void *pvParameters );\r
static void prvRegTestTask2( void *pvParameters );\r
/* The queue used to send messages to the LCD task. */\r
static xQueueHandle xLCDQueue;\r
\r
-/* Variables incremented by prvRegTestTask1() and prvRegTestTask2() respectively on \r
+/* Variables incremented by prvRegTestTask1() and prvRegTestTask2() respectively on\r
each iteration of their function. This is used to detect either task stopping\r
their execution.. */\r
volatile unsigned long ulRegTest1Cycles = 0, ulRegTest2Cycles = 0;\r
{\r
xTimerHandle xTimer = NULL;\r
\r
- /* Create the LCD task - this returns the queue to use when writing \r
+ /* Create the LCD task - this returns the queue to use when writing\r
messages to the LCD. */\r
xLCDQueue = xStartLCDTask();\r
\r
vStartInterruptQueueTasks();\r
\r
/* Create the tasks defined within this file. */\r
- xTaskCreate( prvRegTestTask1, ( const signed char * const ) "Reg1", configMINIMAL_STACK_SIZE, NULL, tskIDLE_PRIORITY, NULL );\r
- xTaskCreate( prvRegTestTask2, ( const signed char * const ) "Reg2", configMINIMAL_STACK_SIZE, NULL, tskIDLE_PRIORITY, NULL );\r
+ xTaskCreate( prvRegTestTask1, "Reg1", configMINIMAL_STACK_SIZE, NULL, tskIDLE_PRIORITY, NULL );\r
+ xTaskCreate( prvRegTestTask2, "Reg2", configMINIMAL_STACK_SIZE, NULL, tskIDLE_PRIORITY, NULL );\r
\r
- /* The PIC32MX795 uses an 8 deep fifo where TX interrupts are asserted \r
- whilst the TX buffer is empty. This causes an issue with the test driver so \r
+ /* The PIC32MX795 uses an 8 deep fifo where TX interrupts are asserted\r
+ whilst the TX buffer is empty. This causes an issue with the test driver so\r
it is not used in this demo */\r
#if !defined(__32MX795F512L__)\r
vAltStartComTestTasks( mainCOM_TEST_PRIORITY, mainCOM_TEST_BAUD_RATE, mainCOM_TEST_LED );\r
- #endif \r
- \r
- /* Create the software timer that performs the 'check' functionality, as \r
+ #endif\r
+\r
+ /* Create the software timer that performs the 'check' functionality, as\r
described at the top of this file. */\r
- xTimer = xTimerCreate( ( const signed char * ) "CheckTimer",/* A text name, purely to help debugging. */\r
+ xTimer = xTimerCreate( "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
+ );\r
+\r
if( xTimer != NULL )\r
{\r
xTimerStart( xTimer, mainDONT_BLOCK );\r
}\r
- \r
+\r
/* A software timer is also used to start the high frequency timer test.\r
This is to ensure the test does not start before the kernel. This time a\r
one shot software timer is used. */\r
- xTimer = xTimerCreate( ( const signed char * ) "HighHzTimerSetup", 1, pdFALSE, ( void * ) 0, prvSetupHighFrequencyTimerTest );\r
+ xTimer = xTimerCreate( "HighHzTimerSetup", 1, pdFALSE, ( void * ) 0, prvSetupHighFrequencyTimerTest );\r
if( xTimer != NULL )\r
{\r
xTimerStart( xTimer, mainDONT_BLOCK );\r
}\r
ulLastRegTest1Value = ulRegTest1Cycles;\r
\r
- \r
+\r
/* Check that the register test 2 task is still running. */\r
if( ulLastRegTest2Value == ulRegTest2Cycles )\r
{\r
xMessage.pcMessage = "Error: Reg test3";\r
}\r
ulLastRegTest2Value = ulRegTest2Cycles;\r
- \r
\r
- /* Have any of the standard demo tasks detected an error in their \r
+\r
+ /* Have any of the standard demo tasks detected an error in their\r
operation? */\r
if( xAreGenericQueueTasksStillRunning() != pdTRUE )\r
{\r
if( lChangedTimerPeriodAlready == pdFALSE )\r
{\r
lChangedTimerPeriodAlready = pdTRUE;\r
- \r
+\r
/* This call to xTimerChangePeriod() uses a zero block time.\r
Functions called from inside of a timer callback function must\r
*never* attempt to block as to do so could impact other software\r
timers. */\r
xTimerChangePeriod( xTimer, ( mainERROR_CHECK_TIMER_PERIOD_MS ), mainDONT_BLOCK );\r
- } \r
+ }\r
}\r
else\r
{\r
- /* Write the ulHighFrequencyTimerInterrupts value to the string \r
+ /* Write the ulHighFrequencyTimerInterrupts value to the string\r
buffer. It will only be displayed if no errors have been detected. */\r
sprintf( cStringBuffer, "Pass %u", ( unsigned int ) ulHighFrequencyTimerInterrupts );\r
}\r
\r
- /* Send the status message to the LCD task for display on the LCD. This is \r
+ /* Send the status message to the LCD task for display on the LCD. This is\r
a timer callback function, so the queue send function *must not* block. */\r
xQueueSend( xLCDQueue, &xMessage, mainDONT_BLOCK );\r
- vParTestToggleLED( mainCHECK_LED ); \r
+ vParTestToggleLED( mainCHECK_LED );\r
}\r
/*-----------------------------------------------------------*/\r
\r
/* Setup the high frequency, high priority, timer test. It is setup in this\r
software timer callback to ensure it does not start before the kernel does.\r
This is a one shot timer - so the setup routine will only be executed once. */\r
- vSetupTimerTest( mainTEST_INTERRUPT_FREQUENCY ); \r
+ vSetupTimerTest( mainTEST_INTERRUPT_FREQUENCY );\r
}\r
\r
projects / freertos / blobdiff