/*\r
- FreeRTOS V8.0.1 - Copyright (C) 2014 Real Time Engineers Ltd. \r
+ FreeRTOS V8.0.1 - Copyright (C) 2014 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 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 is used to select between the two. \r
- * The simply blinky demo is implemented and described in main_blinky.c. The \r
- * more comprehensive test and demo application is implemented and described in \r
+ * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is used to select between the two.\r
+ * The simply blinky demo is implemented and described in main_blinky.c. The\r
+ * more comprehensive test and demo application is implemented and described in\r
* main_full.c.\r
*\r
* This file implements the code that is not demo specific, including the\r
* application. It is provided as a convenient development and demonstration\r
* test bed only. This was tested using Windows XP on a dual core laptop.\r
*\r
- * Windows will not be running the FreeRTOS simulator threads continuously, so \r
- * the timing information in the FreeRTOS+Trace logs have no meaningful units. \r
- * See the documentation page for the Windows simulator for an explanation of \r
+ * Windows will not be running the FreeRTOS simulator threads continuously, so\r
+ * the timing information in the FreeRTOS+Trace logs have no meaningful units.\r
+ * See the documentation page for the Windows simulator for an explanation of\r
* the slow timing:\r
* http://www.freertos.org/FreeRTOS-Windows-Simulator-Emulator-for-Visual-Studio-and-Eclipse-MingW.html\r
* - READ THE WEB DOCUMENTATION FOR THIS PORT FOR MORE INFORMATION ON USING IT -\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 is used to select between the two. \r
-The simply blinky demo is implemented and described in main_blinky.c. The more \r
-comprehensive test and demo application is implemented and described in \r
+mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is used to select between the two.\r
+The simply blinky demo is implemented and described in main_blinky.c. The more\r
+comprehensive test and demo application is implemented and described in\r
main_full.c. */\r
#define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 0\r
\r
+/* This demo uses heap_5.c, and these constants define the sizes of the regions\r
+that make up the total heap. This is only done to provide an example of heap_5\r
+being used as this demo could easily create one large heap region instead of\r
+multiple smaller heap regions - in which case heap_4.c would be the more\r
+appropriate choice. */\r
+#define mainREGION_1_SIZE 2001\r
+#define mainREGION_2_SIZE 18005\r
+#define mainREGION_3_SIZE 1007\r
+\r
/*\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
extern void main_blinky( void );\r
extern void main_full( void );\r
\r
-/* Some of the RTOS hook (callback) functions only need special processing when\r
-the full demo is being used. The simply blinky demo has no special requirements,\r
-so these functions are called from the hook functions defined in this file, but\r
-are defined in main_full.c. */\r
+/*\r
+ * Some of the RTOS hook (callback) functions only need special processing when\r
+ * the full demo is being used. The simply blinky demo has no special\r
+ * requirements, so these functions are called from the hook functions defined\r
+ * in this file, but are defined in main_full.c.\r
+ */\r
void vFullDemoTickHookFunction( void );\r
void vFullDemoIdleFunction( void );\r
\r
-/* Prototypes for the standard FreeRTOS callback/hook functions implemented\r
-within this file. */\r
+/*\r
+ * This demo uses heap_5.c, so start by defining some heap regions. This is\r
+ * only done to provide an example as this demo could easily create one large\r
+ * heap region instead of multiple smaller heap regions - in which case heap_4.c\r
+ * would be the more appropriate choice. No initialisation is required when\r
+ * heap_4.c is used.\r
+ */\r
+static void prvInitialiseHeap( void );\r
+\r
+/*\r
+ * Prototypes for the standard FreeRTOS callback/hook functions implemented\r
+ * within this file.\r
+ */\r
void vApplicationMallocFailedHook( void );\r
void vApplicationIdleHook( void );\r
void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName );\r
\r
int main( void )\r
{\r
+ /* This demo uses heap_5.c, so start by defining some heap regions. This\r
+ is only done to provide an example as this demo could easily create one\r
+ large heap region instead of multiple smaller heap regions - in which case\r
+ heap_4.c would be the more appropriate choice. No initialisation is\r
+ required when heap_4.c is used. */\r
+ prvInitialiseHeap();\r
+\r
/* Initialise the trace recorder and create the label used to post user\r
events to the trace recording on each tick interrupt. */\r
vTraceInitTraceData();\r
function, because it is the responsibility of the idle task to clean up\r
memory allocated by the kernel to any task that has since been deleted. */\r
\r
- /* Uncomment the following code to allow the trace to be stopped with any \r
+ /* Uncomment the following code to allow the trace to be stopped with any\r
key press. The code is commented out by default as the kbhit() function\r
interferes with the run time behaviour. */\r
- /* \r
+ /*\r
if( _kbhit() != pdFALSE )\r
{\r
if( xTraceRunning == pdTRUE )\r
}\r
#endif /* mainCREATE_SIMPLE_BLINKY_DEMO_ONLY */\r
\r
- /* Write a user event to the trace log. \r
+ /* Write a user event to the trace log.\r
Note tick events will not appear in the trace recording with regular period\r
because this project runs in a Windows simulator, and does not therefore\r
- exhibit deterministic behaviour. Windows will run the simulator in \r
+ exhibit deterministic behaviour. Windows will run the simulator in\r
bursts. */\r
vTraceUserEvent( xTickTraceUserEvent );\r
}\r
printf( "\r\nFailed to create trace dump file\r\n" );\r
}\r
}\r
+/*-----------------------------------------------------------*/\r
+\r
+static void prvInitialiseHeap( void )\r
+{\r
+/* This demo uses heap_5.c, so start by defining some heap regions. This is\r
+only done to provide an example as this demo could easily create one large heap\r
+region instead of multiple smaller heap regions - in which case heap_4.c would\r
+be the more appropriate choice. No initialisation is required when heap_4.c is\r
+used. The xHeapRegions structure requires the regions to be defined in order,\r
+so this just creates one big array, then populates the structure with offsets\r
+into the array - with gaps in between and messy alignment just for test\r
+purposes. */\r
+static uint8_t ucHeap[ configTOTAL_HEAP_SIZE ];\r
+volatile uint32_t ulAdditionalOffset = 19; /* Just to prevent 'condition is always true' warnings in configASSERT(). */\r
+const HeapRegion_t xHeapRegions[] =\r
+{\r
+ /* Start address with dummy offsets Size */\r
+ { ucHeap + 1, mainREGION_1_SIZE },\r
+ { ucHeap + 15 + mainREGION_1_SIZE, mainREGION_2_SIZE },\r
+ { ucHeap + 19 + mainREGION_1_SIZE + mainREGION_2_SIZE, mainREGION_3_SIZE },\r
+ { NULL, 0 }\r
+};\r
+\r
+ /* Sanity check that the sizes and offsets defined actually fit into the\r
+ array. */\r
+ configASSERT( ( ulAdditionalOffset + mainREGION_1_SIZE + mainREGION_2_SIZE + mainREGION_3_SIZE ) < configTOTAL_HEAP_SIZE );\r
+\r
+ vPortDefineHeapRegions( xHeapRegions );\r
+}\r
+\r
projects / freertos / commitdiff