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 low power project that
\r
68 * demonstrates the FreeRTOS tickless mode, and a more comprehensive test and
\r
69 * demo application. The configCREATE_LOW_POWER_DEMO setting (defined at the
\r
70 * top of FreeRTOSConfig.h) is used to select between the two. The low power
\r
71 * demo is implemented and described in main_low_power.c. The more
\r
72 * comprehensive test and demo application is implemented and described in
\r
75 * This file implements the code that is not demo specific, including the
\r
76 * hardware setup and FreeRTOS hook functions.
\r
79 /* Kernel includes. */
\r
80 #include "FreeRTOS.h"
\r
83 /* ST library functions. */
\r
84 #include "stm32l1xx.h"
\r
85 #include "discover_board.h"
\r
86 #include "discover_functions.h"
\r
88 /*-----------------------------------------------------------*/
\r
91 * Set up the hardware ready to run this demo.
\r
93 static void prvSetupHardware( void );
\r
96 * main_low_power() is used when configCREATE_LOW_POWER_DEMO is set to 1.
\r
97 * main_full() is used when configCREATE_LOW_POWER_DEMO is set to 0.
\r
98 * configCREATE_LOW_POWER_DEMO is defined at the top of main.c.
\r
100 extern void main_low_power( void );
\r
101 extern void main_full( void );
\r
103 /* Prototypes for the standard FreeRTOS callback/hook functions implemented
\r
104 within this file. */
\r
105 void vApplicationMallocFailedHook( void );
\r
106 void vApplicationIdleHook( void );
\r
107 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName );
\r
108 void vApplicationTickHook( void );
\r
110 /*-----------------------------------------------------------*/
\r
114 /* Prepare the hardware to run this demo. */
\r
115 prvSetupHardware();
\r
117 /* The configCREATE_LOW_POWER_DEMO setting is described at the top of
\r
119 #if configCREATE_LOW_POWER_DEMO == 1
\r
129 /* This line will never be reached. */
\r
132 /*-----------------------------------------------------------*/
\r
134 static void prvSetupHardware( void )
\r
136 /* GPIO, EXTI and NVIC Init structure declaration */
\r
137 GPIO_InitTypeDef GPIO_InitStructure;
\r
138 EXTI_InitTypeDef EXTI_InitStructure;
\r
139 NVIC_InitTypeDef NVIC_InitStructure;
\r
140 void SystemCoreClockUpdate( void );
\r
142 /* System function that updates the SystemCoreClock variable. */
\r
143 SystemCoreClockUpdate();
\r
145 /* Essential on STM32 Cortex-M devices. */
\r
146 NVIC_PriorityGroupConfig( NVIC_PriorityGroup_4 );
\r
148 /* Systick is fed from HCLK/8. */
\r
149 SysTick_CLKSourceConfig( SysTick_CLKSource_HCLK_Div8 );
\r
151 /* Set MSI clock range to ~4.194MHz. */
\r
152 RCC_MSIRangeConfig( RCC_MSIRange_6 );
\r
154 /* Enable the GPIOs clocks. */
\r
155 RCC_AHBPeriphClockCmd( RCC_AHBPeriph_GPIOA | RCC_AHBPeriph_GPIOB | RCC_AHBPeriph_GPIOC| RCC_AHBPeriph_GPIOD| RCC_AHBPeriph_GPIOE| RCC_AHBPeriph_GPIOH, ENABLE );
\r
157 /* Enable comparator clocks. */
\r
158 RCC_APB1PeriphClockCmd( RCC_APB1Periph_COMP, ENABLE );
\r
160 /* Enable SYSCFG clocks. */
\r
161 RCC_APB2PeriphClockCmd( RCC_APB2Periph_SYSCFG , ENABLE );
\r
163 /* Set internal voltage regulator to 1.5V. */
\r
164 PWR_VoltageScalingConfig( PWR_VoltageScaling_Range2 );
\r
166 /* Wait Until the Voltage Regulator is ready. */
\r
167 while( PWR_GetFlagStatus( PWR_FLAG_VOS ) != RESET );
\r
169 /* Configure User Button pin as input */
\r
170 GPIO_InitStructure.GPIO_Pin = USERBUTTON_GPIO_PIN;
\r
171 GPIO_InitStructure.GPIO_Mode = GPIO_Mode_IN;
\r
172 GPIO_InitStructure.GPIO_PuPd = GPIO_PuPd_NOPULL;
\r
173 GPIO_InitStructure.GPIO_Speed = GPIO_Speed_40MHz;
\r
174 GPIO_Init( USERBUTTON_GPIO_PORT, &GPIO_InitStructure );
\r
176 /* Select User Button pin as input source for EXTI Line */
\r
177 SYSCFG_EXTILineConfig( EXTI_PortSourceGPIOA, EXTI_PinSource0 );
\r
179 /* Configure EXT1 Line 0 in interrupt mode trigged on Rising edge */
\r
180 EXTI_InitStructure.EXTI_Line = EXTI_Line0 ; /* PA0 for User button AND IDD_WakeUP */
\r
181 EXTI_InitStructure.EXTI_Mode = EXTI_Mode_Interrupt;
\r
182 EXTI_InitStructure.EXTI_Trigger = EXTI_Trigger_Rising;
\r
183 EXTI_InitStructure.EXTI_LineCmd = ENABLE;
\r
184 EXTI_Init( &EXTI_InitStructure );
\r
186 /* Enable and set EXTI0 Interrupt to the lowest priority */
\r
187 NVIC_InitStructure.NVIC_IRQChannel = EXTI0_IRQn;
\r
188 NVIC_InitStructure.NVIC_IRQChannelPreemptionPriority = configLIBRARY_LOWEST_INTERRUPT_PRIORITY;
\r
189 NVIC_InitStructure.NVIC_IRQChannelSubPriority = 0;
\r
190 NVIC_InitStructure.NVIC_IRQChannelCmd = ENABLE;
\r
191 NVIC_Init( &NVIC_InitStructure );
\r
193 /* Configure the LED_pin as output push-pull for LD3 & LD4 usage */
\r
194 GPIO_InitStructure.GPIO_Pin = LD_GREEN_GPIO_PIN | LD_BLUE_GPIO_PIN;
\r
195 GPIO_InitStructure.GPIO_Mode = GPIO_Mode_OUT;
\r
196 GPIO_InitStructure.GPIO_OType = GPIO_OType_PP;
\r
197 GPIO_InitStructure.GPIO_PuPd = GPIO_PuPd_NOPULL;
\r
198 GPIO_InitStructure.GPIO_Speed = GPIO_Speed_2MHz;
\r
199 GPIO_Init( LD_GPIO_PORT, &GPIO_InitStructure );
\r
201 /* Force a low level on LEDs */
\r
202 GPIO_LOW( LD_GPIO_PORT, LD_GREEN_GPIO_PIN );
\r
203 GPIO_LOW( LD_GPIO_PORT, LD_BLUE_GPIO_PIN );
\r
205 /*-----------------------------------------------------------*/
\r
207 void vApplicationMallocFailedHook( void )
\r
209 /* vApplicationMallocFailedHook() will only be called if
\r
210 configUSE_MALLOC_FAILED_HOOK is set to 1 in FreeRTOSConfig.h. It is a hook
\r
211 function that will get called if a call to pvPortMalloc() fails.
\r
212 pvPortMalloc() is called internally by the kernel whenever a task, queue,
\r
213 timer or semaphore is created. It is also called by various parts of the
\r
214 demo application. If heap_1.c or heap_2.c are used, then the size of the
\r
215 heap available to pvPortMalloc() is defined by configTOTAL_HEAP_SIZE in
\r
216 FreeRTOSConfig.h, and the xPortGetFreeHeapSize() API function can be used
\r
217 to query the size of free heap space that remains (although it does not
\r
218 provide information on how the remaining heap might be fragmented). */
\r
219 taskDISABLE_INTERRUPTS();
\r
222 /*-----------------------------------------------------------*/
\r
224 void vApplicationIdleHook( void )
\r
226 /* vApplicationIdleHook() will only be called if configUSE_IDLE_HOOK is set
\r
227 to 1 in FreeRTOSConfig.h. It will be called on each iteration of the idle
\r
228 task. It is essential that code added to this hook function never attempts
\r
229 to block in any way (for example, call xQueueReceive() with a block time
\r
230 specified, or call vTaskDelay()). If the application makes use of the
\r
231 vTaskDelete() API function (as this demo application does) then it is also
\r
232 important that vApplicationIdleHook() is permitted to return to its calling
\r
233 function, because it is the responsibility of the idle task to clean up
\r
234 memory allocated by the kernel to any task that has since been deleted. */
\r
236 /*-----------------------------------------------------------*/
\r
238 void vApplicationStackOverflowHook( xTaskHandle pxTask, signed char *pcTaskName )
\r
240 ( void ) pcTaskName;
\r
243 /* Run time stack overflow checking is performed if
\r
244 configCHECK_FOR_STACK_OVERFLOW is defined to 1 or 2. This hook
\r
245 function is called if a stack overflow is detected. */
\r
246 taskDISABLE_INTERRUPTS();
\r
249 /*-----------------------------------------------------------*/
\r
251 void vApplicationTickHook( void )
\r
253 /* This function will be called by each tick interrupt if
\r
254 configUSE_TICK_HOOK is set to 1 in FreeRTOSConfig.h. User code can be
\r
255 added here, but the tick hook is called from an interrupt context, so
\r
256 code must not attempt to block, and only the interrupt safe FreeRTOS API
\r
257 functions can be used (those that end in FromISR()). */
\r
259 /*-----------------------------------------------------------*/
\r
261 void vAssertCalled( unsigned long ulLine, const char * const pcFileName )
\r
263 volatile unsigned long ulSetToNonZeroInDebuggerToContinue = 0;
\r
265 /* Parameters are not used. */
\r
267 ( void ) pcFileName;
\r
269 taskENTER_CRITICAL();
\r
271 while( ulSetToNonZeroInDebuggerToContinue == 0 )
\r
273 /* Use the debugger to set ulSetToNonZeroInDebuggerToContinue to a
\r
274 non zero value to step out of this function to the point that raised
\r
276 __asm volatile( "NOP" );
\r
277 __asm volatile( "NOP" );
\r
280 taskEXIT_CRITICAL();
\r