2 FreeRTOS V8.2.3 - Copyright (C) 2015 Real Time Engineers Ltd.
\r
5 VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.
\r
7 This file is part of the FreeRTOS distribution.
\r
9 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
10 the terms of the GNU General Public License (version 2) as published by the
\r
11 Free Software Foundation >>>> AND MODIFIED BY <<<< the FreeRTOS exception.
\r
13 ***************************************************************************
\r
14 >>! NOTE: The modification to the GPL is included to allow you to !<<
\r
15 >>! distribute a combined work that includes FreeRTOS without being !<<
\r
16 >>! obliged to provide the source code for proprietary components !<<
\r
17 >>! outside of the FreeRTOS kernel. !<<
\r
18 ***************************************************************************
\r
20 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
21 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
22 FOR A PARTICULAR PURPOSE. Full license text is available on the following
\r
23 link: http://www.freertos.org/a00114.html
\r
25 ***************************************************************************
\r
27 * FreeRTOS provides completely free yet professionally developed, *
\r
28 * robust, strictly quality controlled, supported, and cross *
\r
29 * platform software that is more than just the market leader, it *
\r
30 * is the industry's de facto standard. *
\r
32 * Help yourself get started quickly while simultaneously helping *
\r
33 * to support the FreeRTOS project by purchasing a FreeRTOS *
\r
34 * tutorial book, reference manual, or both: *
\r
35 * http://www.FreeRTOS.org/Documentation *
\r
37 ***************************************************************************
\r
39 http://www.FreeRTOS.org/FAQHelp.html - Having a problem? Start by reading
\r
40 the FAQ page "My application does not run, what could be wrong?". Have you
\r
41 defined configASSERT()?
\r
43 http://www.FreeRTOS.org/support - In return for receiving this top quality
\r
44 embedded software for free we request you assist our global community by
\r
45 participating in the support forum.
\r
47 http://www.FreeRTOS.org/training - Investing in training allows your team to
\r
48 be as productive as possible as early as possible. Now you can receive
\r
49 FreeRTOS training directly from Richard Barry, CEO of Real Time Engineers
\r
50 Ltd, and the world's leading authority on the world's leading RTOS.
\r
52 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
53 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
54 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
56 http://www.FreeRTOS.org/labs - Where new FreeRTOS products go to incubate.
\r
57 Come and try FreeRTOS+TCP, our new open source TCP/IP stack for FreeRTOS.
\r
59 http://www.OpenRTOS.com - Real Time Engineers ltd. license FreeRTOS to High
\r
60 Integrity Systems ltd. to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
61 licenses offer ticketed support, indemnification and commercial middleware.
\r
63 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
64 engineered and independently SIL3 certified version for use in safety and
\r
65 mission critical applications that require provable dependability.
\r
70 /******************************************************************************
\r
71 * This project provides two demo applications. A simple blinky style project,
\r
72 * and a more comprehensive test and demo application. The
\r
73 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is used to select between the two.
\r
74 * The simply blinky demo is implemented and described in main_blinky.c. The
\r
75 * more comprehensive test and demo application is implemented and described in
\r
78 * This file implements the code that is not demo specific, including the
\r
79 * hardware setup and FreeRTOS hook functions.
\r
81 *******************************************************************************
\r
82 * NOTE: Windows will not be running the FreeRTOS demo threads continuously, so
\r
83 * do not expect to get real time behaviour from the FreeRTOS Windows port, or
\r
84 * this demo application. Also, the timing information in the FreeRTOS+Trace
\r
85 * logs have no meaningful units. See the documentation page for the Windows
\r
86 * port for further information:
\r
87 * http://www.freertos.org/FreeRTOS-Windows-Simulator-Emulator-for-Visual-Studio-and-Eclipse-MingW.html
\r
89 * This demo was created using Windows XP on a dual core laptop, and has since
\r
90 * been maintained using Windows 7 on a quad core laptop.
\r
92 *******************************************************************************
\r
95 /* Standard includes. */
\r
100 /* FreeRTOS kernel includes. */
\r
101 #include "FreeRTOS.h"
\r
104 /* This project provides two demo applications. A simple blinky style demo
\r
105 application, and a more comprehensive test and demo application. The
\r
106 mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is used to select between the two.
\r
108 If mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is 1 then the blinky demo will be built.
\r
109 The blinky demo is implemented and described in main_blinky.c.
\r
111 If mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is not 1 then the comprehensive test and
\r
112 demo application will be built. The comprehensive test and demo application is
\r
113 implemented and described in main_full.c. */
\r
114 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 1
\r
116 /* This demo uses heap_5.c, and these constants define the sizes of the regions
\r
117 that make up the total heap. heap_5 is only used for test and example purposes
\r
118 as this demo could easily create one large heap region instead of multiple
\r
119 smaller heap regions - in which case heap_4.c would be the more appropriate
\r
120 choice. See http://www.freertos.org/a00111.html for an explanation. */
\r
121 #define mainREGION_1_SIZE 4001
\r
122 #define mainREGION_2_SIZE 18105
\r
123 #define mainREGION_3_SIZE 1807
\r
125 /*-----------------------------------------------------------*/
\r
128 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
129 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
131 extern void main_blinky( void );
\r
132 extern void main_full( void );
\r
135 * Only the comprehensive demo uses application hook (callback) functions. See
\r
136 * http://www.freertos.org/a00016.html for more information.
\r
138 void vFullDemoTickHookFunction( void );
\r
139 void vFullDemoIdleFunction( void );
\r
142 * This demo uses heap_5.c, so start by defining some heap regions. It is not
\r
143 * necessary for this demo to use heap_5, as it could define one large heap
\r
144 * region. Heap_5 is only used for test and example purposes. See
\r
145 * http://www.freertos.org/a00111.html for an explanation.
\r
147 static void prvInitialiseHeap( void );
\r
150 * Prototypes for the standard FreeRTOS application hook (callback) functions
\r
151 * implemented within this file. See http://www.freertos.org/a00016.html .
\r
153 void vApplicationMallocFailedHook( void );
\r
154 void vApplicationIdleHook( void );
\r
155 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName );
\r
156 void vApplicationTickHook( void );
\r
157 void vApplicationGetIdleTaskMemory( DummyTCB_t **ppxIdleTaskTCBBuffer, StackType_t **ppxIdleTaskStackBuffer, uint16_t *pusIdleTaskStackSize );
\r
158 void vApplicationGetTimerTaskMemory( DummyTCB_t **ppxTimerTaskTCBBuffer, StackType_t **ppxTimerTaskStackBuffer, uint16_t *pusTimerTaskStackSize );
\r
161 * Writes trace data to a disk file when the trace recording is stopped.
\r
162 * This function will simply overwrite any trace files that already exist.
\r
164 static void prvSaveTraceFile( void );
\r
166 /* The user trace event posted to the trace recording on each tick interrupt.
\r
167 Note: This project runs under Windows, and Windows will not be executing the
\r
168 RTOS threads continuously. Therefore tick events will not appear with a regular
\r
169 interval within the the trace recording. */
\r
170 traceLabel xTickTraceUserEvent;
\r
171 static portBASE_TYPE xTraceRunning = pdTRUE;
\r
173 /*-----------------------------------------------------------*/
\r
177 /* This demo uses heap_5.c, so start by defining some heap regions. heap_5
\r
178 is only used for test and example reasons. Heap_4 is more appropriate. See
\r
179 http://www.freertos.org/a00111.html for an explanation. */
\r
180 prvInitialiseHeap();
\r
182 /* Initialise the trace recorder and create the label used to post user
\r
183 events to the trace recording on each tick interrupt. Use of the trace
\r
184 recorder is optional. See http://www.FreeRTOS.org/trace for more
\r
186 vTraceInitTraceData();
\r
187 xTickTraceUserEvent = xTraceOpenLabel( "tick" );
\r
189 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
191 #if ( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1 )
\r
197 /* Start the trace recording - the recording is written to a file if
\r
198 configASSERT() is called. */
\r
199 printf( "\r\nTrace started.\r\nThe trace will be dumped to disk if a call to configASSERT() fails.\r\n" );
\r
200 printf( "Uncomment the call to kbhit() in this file to also dump trace with a key press.\r\n" );
\r
209 /*-----------------------------------------------------------*/
\r
211 void vApplicationMallocFailedHook( void )
\r
213 /* vApplicationMallocFailedHook() will only be called if
\r
214 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
215 function that will get called if a call to pvPortMalloc() fails.
\r
216 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
217 timer or semaphore is created. It is also called by various parts of the
\r
218 demo application. If heap_1.c, heap_2.c or heap_4.c is being used, then the
\r
219 size of the heap available to pvPortMalloc() is defined by
\r
220 configTOTAL_HEAP_SIZE in FreeRTOSConfig.h, and the xPortGetFreeHeapSize()
\r
221 API function can be used to query the size of free heap space that remains
\r
222 (although it does not provide information on how the remaining heap might be
\r
223 fragmented). See http://www.freertos.org/a00111.html for more
\r
225 vAssertCalled( __LINE__, __FILE__ );
\r
227 /*-----------------------------------------------------------*/
\r
229 void vApplicationIdleHook( void )
\r
231 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
232 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
233 task. It is essential that code added to this hook function never attempts
\r
234 to block in any way (for example, call xQueueReceive() with a block time
\r
235 specified, or call vTaskDelay()). If application tasks make use of the
\r
236 vTaskDelete() API function to delete themselves then it is also important
\r
237 that vApplicationIdleHook() is permitted to return to its calling function,
\r
238 because it is the responsibility of the idle task to clean up memory
\r
239 allocated by the kernel to any task that has since deleted itself. */
\r
241 /* Uncomment the following code to allow the trace to be stopped with any
\r
242 key press. The code is commented out by default as the kbhit() function
\r
243 interferes with the run time behaviour. */
\r
245 if( _kbhit() != pdFALSE )
\r
247 if( xTraceRunning == pdTRUE )
\r
250 prvSaveTraceFile();
\r
251 xTraceRunning = pdFALSE;
\r
256 #if ( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY != 1 )
\r
258 /* Call the idle task processing used by the full demo. The simple
\r
259 blinky demo does not use the idle task hook. */
\r
260 vFullDemoIdleFunction();
\r
264 /*-----------------------------------------------------------*/
\r
266 void vApplicationStackOverflowHook( TaskHandle_t pxTask, char *pcTaskName )
\r
268 ( void ) pcTaskName;
\r
271 /* Run time stack overflow checking is performed if
\r
272 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
273 function is called if a stack overflow is detected. This function is
\r
274 provided as an example only as stack overflow checking does not function
\r
275 when running the FreeRTOS Windows port. */
\r
276 vAssertCalled( __LINE__, __FILE__ );
\r
278 /*-----------------------------------------------------------*/
\r
280 void vApplicationTickHook( void )
\r
282 /* This function will be called by each tick interrupt if
\r
283 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
284 added here, but the tick hook is called from an interrupt context, so
\r
285 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
286 functions can be used (those that end in FromISR()). */
\r
288 #if ( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY != 1 )
\r
290 vFullDemoTickHookFunction();
\r
292 #endif /* mainCREATE_SIMPLE_BLINKY_DEMO_ONLY */
\r
294 /* Write a user event to the trace log. Note: This project runs under
\r
295 Windows, and Windows will not be executing the RTOS threads continuously.
\r
296 Therefore tick events will not appear with a regular interval within the the
\r
297 trace recording. */
\r
298 vTraceUserEvent( xTickTraceUserEvent );
\r
300 /*-----------------------------------------------------------*/
\r
302 void vAssertCalled( unsigned long ulLine, const char * const pcFileName )
\r
304 static portBASE_TYPE xPrinted = pdFALSE;
\r
305 volatile uint32_t ulSetToNonZeroInDebuggerToContinue = 0;
\r
307 /* Called if an assertion passed to configASSERT() fails. See
\r
308 http://www.freertos.org/a00110.html#configASSERT for more information. */
\r
310 /* Parameters are not used. */
\r
312 ( void ) pcFileName;
\r
314 printf( "ASSERT! Line %d, file %s\r\n", ulLine, pcFileName );
\r
316 taskENTER_CRITICAL();
\r
318 /* Stop the trace recording. */
\r
319 if( xPrinted == pdFALSE )
\r
322 if( xTraceRunning == pdTRUE )
\r
325 prvSaveTraceFile();
\r
329 /* You can step out of this function to debug the assertion by using
\r
330 the debugger to set ulSetToNonZeroInDebuggerToContinue to a non-zero
\r
332 while( ulSetToNonZeroInDebuggerToContinue == 0 )
\r
338 taskEXIT_CRITICAL();
\r
340 /*-----------------------------------------------------------*/
\r
342 static void prvSaveTraceFile( void )
\r
344 FILE* pxOutputFile;
\r
346 fopen_s( &pxOutputFile, "Trace.dump", "wb");
\r
348 if( pxOutputFile != NULL )
\r
350 fwrite( RecorderDataPtr, sizeof( RecorderDataType ), 1, pxOutputFile );
\r
351 fclose( pxOutputFile );
\r
352 printf( "\r\nTrace output saved to Trace.dump\r\n" );
\r
356 printf( "\r\nFailed to create trace dump file\r\n" );
\r
359 /*-----------------------------------------------------------*/
\r
361 static void prvInitialiseHeap( void )
\r
363 /* The Windows demo could create one large heap region, in which case it would
\r
364 be appropriate to use heap_4. However, purely for demonstration purposes,
\r
365 heap_5 is used instead, so start by defining some heap regions. No
\r
366 initialisation is required when any other heap implementation is used. See
\r
367 http://www.freertos.org/a00111.html for more information.
\r
369 The xHeapRegions structure requires the regions to be defined in start address
\r
370 order, so this just creates one big array, then populates the structure with
\r
371 offsets into the array - with gaps in between and messy alignment just for test
\r
373 static uint8_t ucHeap[ configTOTAL_HEAP_SIZE ];
\r
374 volatile uint32_t ulAdditionalOffset = 19; /* Just to prevent 'condition is always true' warnings in configASSERT(). */
\r
375 const HeapRegion_t xHeapRegions[] =
\r
377 /* Start address with dummy offsets Size */
\r
378 { ucHeap + 1, mainREGION_1_SIZE },
\r
379 { ucHeap + 15 + mainREGION_1_SIZE, mainREGION_2_SIZE },
\r
380 { ucHeap + 19 + mainREGION_1_SIZE + mainREGION_2_SIZE, mainREGION_3_SIZE },
\r
384 /* Sanity check that the sizes and offsets defined actually fit into the
\r
386 configASSERT( ( ulAdditionalOffset + mainREGION_1_SIZE + mainREGION_2_SIZE + mainREGION_3_SIZE ) < configTOTAL_HEAP_SIZE );
\r
388 /* Prevent compiler warnings when configASSERT() is not defined. */
\r
389 ( void ) ulAdditionalOffset;
\r
391 vPortDefineHeapRegions( xHeapRegions );
\r
393 /*-----------------------------------------------------------*/
\r
395 void vApplicationGetIdleTaskMemory( DummyTCB_t **ppxIdleTaskTCBBuffer, StackType_t **ppxIdleTaskStackBuffer, uint16_t *pusIdleTaskStackSize )
\r
397 /* The buffers used by the idle task must be static so they are persistent, and
\r
398 so exist after this function returns. */
\r
399 static DummyTCB_t xIdleTaskTCB;
\r
400 static StackType_t uxIdleTaskStack[ configMINIMAL_STACK_SIZE ];
\r
402 /* configUSE_STATIC_ALLOCATION is set to 1, so the application has the
\r
403 opportunity to supply the buffers that will be used by the Idle task as its
\r
404 stack and to hold its TCB. If these are set to NULL then the buffers will
\r
405 be allocated dynamically, just as if xTaskCreate() had been called. */
\r
406 *ppxIdleTaskTCBBuffer = &xIdleTaskTCB;
\r
407 *ppxIdleTaskStackBuffer = uxIdleTaskStack;
\r
408 *pusIdleTaskStackSize = configMINIMAL_STACK_SIZE; /* In words. NOT in bytes! */
\r
410 /*-----------------------------------------------------------*/
\r
411 DummyTCB_t xTimerTaskTCB;
\r
412 void vApplicationGetTimerTaskMemory( DummyTCB_t **ppxTimerTaskTCBBuffer, StackType_t **ppxTimerTaskStackBuffer, uint16_t *pusTimerTaskStackSize )
\r
414 /* The buffers used by the Timer/Daemon task must be static so they are
\r
415 persistent, and so exist after this function returns. */
\r
416 //static DummyTCB_t xTimerTaskTCB;
\r
417 static StackType_t uxTimerTaskStack[ configTIMER_TASK_STACK_DEPTH ];
\r
419 /* configUSE_STATIC_ALLOCATION is set to 1, so the application has the
\r
420 opportunity to supply the buffers that will be used by the Timer/RTOS daemon
\r
421 task as its stack and to hold its TCB. If these are set to NULL then the
\r
422 buffers will be allocated dynamically, just as if xTaskCreate() had been
\r
424 *ppxTimerTaskTCBBuffer = &xTimerTaskTCB;
\r
425 *ppxTimerTaskStackBuffer = uxTimerTaskStack;
\r
426 *pusTimerTaskStackSize = configTIMER_TASK_STACK_DEPTH; /* In words. NOT in bytes! */
\r