2 FreeRTOS V7.6.0 - Copyright (C) 2013 Real Time Engineers Ltd.
\r
5 VISIT http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.
\r
7 ***************************************************************************
\r
9 * FreeRTOS provides completely free yet professionally developed, *
\r
10 * robust, strictly quality controlled, supported, and cross *
\r
11 * platform software that has become a de facto standard. *
\r
13 * Help yourself get started quickly and support the FreeRTOS *
\r
14 * project by purchasing a FreeRTOS tutorial book, reference *
\r
15 * manual, or both from: http://www.FreeRTOS.org/Documentation *
\r
19 ***************************************************************************
\r
21 This file is part of the FreeRTOS distribution.
\r
23 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
24 the terms of the GNU General Public License (version 2) as published by the
\r
25 Free Software Foundation >>!AND MODIFIED BY!<< the FreeRTOS exception.
\r
27 >>! NOTE: The modification to the GPL is included to allow you to distribute
\r
28 >>! a combined work that includes FreeRTOS without being obliged to provide
\r
29 >>! the source code for proprietary components outside of the FreeRTOS
\r
32 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
33 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
34 FOR A PARTICULAR PURPOSE. Full license text is available from the following
\r
35 link: http://www.freertos.org/a00114.html
\r
39 ***************************************************************************
\r
41 * Having a problem? Start by reading the FAQ "My application does *
\r
42 * not run, what could be wrong?" *
\r
44 * http://www.FreeRTOS.org/FAQHelp.html *
\r
46 ***************************************************************************
\r
48 http://www.FreeRTOS.org - Documentation, books, training, latest versions,
\r
49 license and Real Time Engineers Ltd. contact details.
\r
51 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
52 including FreeRTOS+Trace - an indispensable productivity tool, a DOS
\r
53 compatible FAT file system, and our tiny thread aware UDP/IP stack.
\r
55 http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High
\r
56 Integrity Systems to sell under the OpenRTOS brand. Low cost OpenRTOS
\r
57 licenses offer ticketed support, indemnification and middleware.
\r
59 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
60 engineered and independently SIL3 certified version for use in safety and
\r
61 mission critical applications that require provable dependability.
\r
66 /******************************************************************************
\r
67 * This project provides two demo applications. A simple blinky style project,
\r
68 * and a more comprehensive test and demo application. The
\r
69 * mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is used to select between the two.
\r
70 * The simply blinky demo is implemented and described in main_blinky.c. The
\r
71 * more comprehensive test and demo application is implemented and described in
\r
74 * This file implements the code that is not demo specific, including the
\r
75 * hardware setup and FreeRTOS hook functions.
\r
77 *******************************************************************************
\r
78 * -NOTE- The Win32 port is a simulation (or is that emulation?) only! Do not
\r
79 * expect to get real time behaviour from the Win32 port or this demo
\r
80 * application. It is provided as a convenient development and demonstration
\r
81 * test bed only. This was tested using Windows XP on a dual core laptop.
\r
83 * Windows will not be running the FreeRTOS simulator threads continuously, so
\r
84 * the timing information in the FreeRTOS+Trace logs have no meaningful units.
\r
85 * See the documentation page for the Windows simulator for an explanation of
\r
87 * http://www.freertos.org/FreeRTOS-Windows-Simulator-Emulator-for-Visual-Studio-and-Eclipse-MingW.html
\r
88 * - READ THE WEB DOCUMENTATION FOR THIS PORT FOR MORE INFORMATION ON USING IT -
\r
89 *******************************************************************************
\r
93 /* Standard includes. */
\r
98 /* FreeRTOS kernel includes. */
\r
99 #include "FreeRTOS.h"
\r
102 /* This project provides two demo applications. A simple blinky style project,
\r
103 and a more comprehensive test and demo application. The
\r
104 mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is used to select between the two.
\r
105 The simply blinky demo is implemented and described in main_blinky.c. The more
\r
106 comprehensive test and demo application is implemented and described in
\r
108 #define mainCREATE_SIMPLE_BLINKY_DEMO_ONLY 0
\r
111 * main_blinky() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 1.
\r
112 * main_full() is used when mainCREATE_SIMPLE_BLINKY_DEMO_ONLY is set to 0.
\r
114 extern void main_blinky( void );
\r
115 extern void main_full( void );
\r
117 /* Some of the RTOS hook (callback) functions only need special processing when
\r
118 the full demo is being used. The simply blinky demo has no special requirements,
\r
119 so these functions are called from the hook functions defined in this file, but
\r
120 are defined in main_full.c. */
\r
121 void vFullDemoTickHookFunction( void );
\r
122 void vFullDemoIdleFunction( void );
\r
124 /* Prototypes for the standard FreeRTOS callback/hook functions implemented
\r
125 within this file. */
\r
126 void vApplicationMallocFailedHook( void );
\r
127 void vApplicationIdleHook( void );
\r
128 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName );
\r
129 void vApplicationTickHook( void );
\r
132 * Writes trace data to a disk file when the trace recording is stopped.
\r
133 * This function will simply overwrite any trace files that already exist.
\r
135 static void prvSaveTraceFile( void );
\r
137 /* The user trace event posted to the trace recording on each tick interrupt.
\r
138 Note tick events will not appear in the trace recording with regular period
\r
139 because this project runs in a Windows simulator, and does not therefore
\r
140 exhibit deterministic behaviour. */
\r
141 traceLabel xTickTraceUserEvent;
\r
142 static portBASE_TYPE xTraceRunning = pdTRUE;
\r
144 /*-----------------------------------------------------------*/
\r
149 /* Initialise the trace recorder and create the label used to post user
\r
150 events to the trace recording on each tick interrupt. */
\r
151 vTraceInitTraceData();
\r
152 printf( "Trace started. Hit a key to dump trace file to disk. Note stdin does not work when using the Eclipse console with MingW.\r\n" );
\r
155 xTickTraceUserEvent = xTraceOpenLabel( "tick" );
\r
157 /* Start the trace recording - the recording is written to a file if
\r
158 configASSERT() is called. */
\r
161 /* The mainCREATE_SIMPLE_BLINKY_DEMO_ONLY setting is described at the top
\r
163 #if ( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY == 1 )
\r
175 /*-----------------------------------------------------------*/
\r
177 void vApplicationMallocFailedHook( void )
\r
179 /* vApplicationMallocFailedHook() will only be called if
\r
180 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
181 function that will get called if a call to pvPortMalloc() fails.
\r
182 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
183 timer or semaphore is created. It is also called by various parts of the
\r
184 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
185 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
186 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
187 to query the size of free heap space that remains (although it does not
\r
188 provide information on how the remaining heap might be fragmented). */
\r
189 vAssertCalled( __LINE__, __FILE__ );
\r
191 /*-----------------------------------------------------------*/
\r
193 void vApplicationIdleHook( void )
\r
195 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
196 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
197 task. It is essential that code added to this hook function never attempts
\r
198 to block in any way (for example, call xQueueReceive() with a block time
\r
199 specified, or call vTaskDelay()). If the application makes use of the
\r
200 vTaskDelete() API function (as this demo application does) then it is also
\r
201 important that vApplicationIdleHook() is permitted to return to its calling
\r
202 function, because it is the responsibility of the idle task to clean up
\r
203 memory allocated by the kernel to any task that has since been deleted. */
\r
205 /* The trace can be stopped with any key press. */
\r
206 if( kbhit() != pdFALSE )
\r
208 if( xTraceRunning == pdTRUE )
\r
211 prvSaveTraceFile();
\r
212 xTraceRunning = pdFALSE;
\r
216 #if ( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY != 1 )
\r
218 /* Call the idle task processing used by the full demo. The simple
\r
219 blinky demo does not use the idle task hook. */
\r
220 vFullDemoIdleFunction();
\r
224 /*-----------------------------------------------------------*/
\r
226 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName )
\r
228 ( void ) pcTaskName;
\r
231 /* Run time stack overflow checking is performed if
\r
232 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
233 function is called if a stack overflow is detected. */
\r
234 vAssertCalled( __LINE__, __FILE__ );
\r
236 /*-----------------------------------------------------------*/
\r
238 void vApplicationTickHook( void )
\r
240 /* This function will be called by each tick interrupt if
\r
241 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
242 added here, but the tick hook is called from an interrupt context, so
\r
243 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
244 functions can be used (those that end in FromISR()). */
\r
246 #if ( mainCREATE_SIMPLE_BLINKY_DEMO_ONLY != 1 )
\r
248 vFullDemoTickHookFunction();
\r
250 #endif /* mainCREATE_SIMPLE_BLINKY_DEMO_ONLY */
\r
252 /* Write a user event to the trace log.
\r
253 Note tick events will not appear in the trace recording with regular period
\r
254 because this project runs in a Windows simulator, and does not therefore
\r
255 exhibit deterministic behaviour. Windows will run the simulator in
\r
257 vTraceUserEvent( xTickTraceUserEvent );
\r
259 /*-----------------------------------------------------------*/
\r
261 void vAssertCalled( unsigned long ulLine, const char * const pcFileName )
\r
263 /* Parameters are not used. */
\r
265 ( void ) pcFileName;
\r
267 taskDISABLE_INTERRUPTS();
\r
268 __asm volatile( "int $3" );
\r
270 /* Stop the trace recording. */
\r
271 if( xTraceRunning == pdTRUE )
\r
274 prvSaveTraceFile();
\r
277 taskENABLE_INTERRUPTS();
\r
279 /*-----------------------------------------------------------*/
\r
281 static void prvSaveTraceFile( void )
\r
283 FILE* pxOutputFile;
\r
285 pxOutputFile = fopen( "Trace.dump", "wb");
\r
287 if( pxOutputFile != NULL )
\r
289 fwrite( RecorderDataPtr, sizeof( RecorderDataType ), 1, pxOutputFile );
\r
290 fclose( pxOutputFile );
\r
291 printf( "\r\nTrace output saved to Trace.dump\r\n" );
\r
296 printf( "\r\nFailed to create trace dump file\r\n" );
\r