2 FreeRTOS V7.3.0 - Copyright (C) 2012 Real Time Engineers Ltd.
\r
4 FEATURES AND PORTS ARE ADDED TO FREERTOS ALL THE TIME. PLEASE VISIT
\r
5 http://www.FreeRTOS.org TO ENSURE YOU ARE USING THE LATEST VERSION.
\r
7 ***************************************************************************
\r
9 * FreeRTOS tutorial books are available in pdf and paperback. *
\r
10 * Complete, revised, and edited pdf reference manuals are also *
\r
13 * Purchasing FreeRTOS documentation will not only help you, by *
\r
14 * ensuring you get running as quickly as possible and with an *
\r
15 * in-depth knowledge of how to use FreeRTOS, it will also help *
\r
16 * the FreeRTOS project to continue with its mission of providing *
\r
17 * professional grade, cross platform, de facto standard solutions *
\r
18 * for microcontrollers - completely free of charge! *
\r
20 * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *
\r
22 * Thank you for using FreeRTOS, and thank you for your support! *
\r
24 ***************************************************************************
\r
27 This file is part of the FreeRTOS distribution.
\r
29 FreeRTOS is free software; you can redistribute it and/or modify it under
\r
30 the terms of the GNU General Public License (version 2) as published by the
\r
31 Free Software Foundation AND MODIFIED BY the FreeRTOS exception.
\r
32 >>>NOTE<<< The modification to the GPL is included to allow you to
\r
33 distribute a combined work that includes FreeRTOS without being obliged to
\r
34 provide the source code for proprietary components outside of the FreeRTOS
\r
35 kernel. FreeRTOS is distributed in the hope that it will be useful, but
\r
36 WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
\r
37 or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
\r
38 more details. You should have received a copy of the GNU General Public
\r
39 License and the FreeRTOS license exception along with FreeRTOS; if not it
\r
40 can be viewed here: http://www.freertos.org/a00114.html and also obtained
\r
41 by writing to Richard Barry, contact details for whom are available on the
\r
46 ***************************************************************************
\r
48 * Having a problem? Start by reading the FAQ "My application does *
\r
49 * not run, what could be wrong?" *
\r
51 * http://www.FreeRTOS.org/FAQHelp.html *
\r
53 ***************************************************************************
\r
56 http://www.FreeRTOS.org - Documentation, training, latest versions, license
\r
57 and contact details.
\r
59 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
60 including FreeRTOS+Trace - an indispensable productivity tool.
\r
62 Real Time Engineers ltd license FreeRTOS to High Integrity Systems, who sell
\r
63 the code with commercial support, indemnification, and middleware, under
\r
64 the OpenRTOS brand: http://www.OpenRTOS.com. High Integrity Systems also
\r
65 provide a safety engineered and independently SIL3 certified version under
\r
66 the SafeRTOS brand: http://www.SafeRTOS.com.
\r
72 + usCriticalNesting now has a volatile qualifier.
\r
75 /* Standard includes. */
\r
79 /* Scheduler includes. */
\r
80 #include "FreeRTOS.h"
\r
83 /*-----------------------------------------------------------
\r
84 * Implementation of functions defined in portable.h for the MSP430 port.
\r
85 *----------------------------------------------------------*/
\r
87 /* Constants required for hardware setup. The tick ISR runs off the ACLK,
\r
89 #define portACLK_FREQUENCY_HZ ( ( portTickType ) 32768 )
\r
90 #define portINITIAL_CRITICAL_NESTING ( ( unsigned short ) 10 )
\r
91 #define portFLAGS_INT_ENABLED ( ( portSTACK_TYPE ) 0x08 )
\r
93 /* We require the address of the pxCurrentTCB variable, but don't want to know
\r
94 any details of its type. */
\r
95 typedef void tskTCB;
\r
96 extern volatile tskTCB * volatile pxCurrentTCB;
\r
98 /* Most ports implement critical sections by placing the interrupt flags on
\r
99 the stack before disabling interrupts. Exiting the critical section is then
\r
100 simply a case of popping the flags from the stack. As mspgcc does not use
\r
101 a frame pointer this cannot be done as modifying the stack will clobber all
\r
102 the stack variables. Instead each task maintains a count of the critical
\r
103 section nesting depth. Each time a critical section is entered the count is
\r
104 incremented. Each time a critical section is left the count is decremented -
\r
105 with interrupts only being re-enabled if the count is zero.
\r
107 usCriticalNesting will get set to zero when the scheduler starts, but must
\r
108 not be initialised to zero as this will cause problems during the startup
\r
110 volatile unsigned short usCriticalNesting = portINITIAL_CRITICAL_NESTING;
\r
111 /*-----------------------------------------------------------*/
\r
114 * Macro to save a task context to the task stack. This simply pushes all the
\r
115 * general purpose msp430 registers onto the stack, followed by the
\r
116 * usCriticalNesting value used by the task. Finally the resultant stack
\r
117 * pointer value is saved into the task control block so it can be retrieved
\r
118 * the next time the task executes.
\r
120 #define portSAVE_CONTEXT() \
\r
121 asm volatile ( "push r4 \n\t" \
\r
133 "mov.w usCriticalNesting, r14 \n\t" \
\r
135 "mov.w pxCurrentTCB, r12 \n\t" \
\r
136 "mov.w r1, @r12 \n\t" \
\r
140 * Macro to restore a task context from the task stack. This is effectively
\r
141 * the reverse of portSAVE_CONTEXT(). First the stack pointer value is
\r
142 * loaded from the task control block. Next the value for usCriticalNesting
\r
143 * used by the task is retrieved from the stack - followed by the value of all
\r
144 * the general purpose msp430 registers.
\r
146 * The bic instruction ensures there are no low power bits set in the status
\r
147 * register that is about to be popped from the stack.
\r
149 #define portRESTORE_CONTEXT() \
\r
150 asm volatile ( "mov.w pxCurrentTCB, r12 \n\t" \
\r
151 "mov.w @r12, r1 \n\t" \
\r
153 "mov.w r15, usCriticalNesting \n\t" \
\r
166 "bic #(0xf0),0(r1) \n\t" \
\r
169 /*-----------------------------------------------------------*/
\r
172 * Sets up the periodic ISR used for the RTOS tick. This uses timer 0, but
\r
173 * could have alternatively used the watchdog timer or timer 1.
\r
175 static void prvSetupTimerInterrupt( void );
\r
176 /*-----------------------------------------------------------*/
\r
179 * Initialise the stack of a task to look exactly as if a call to
\r
180 * portSAVE_CONTEXT had been called.
\r
182 * See the header file portable.h.
\r
184 portSTACK_TYPE *pxPortInitialiseStack( portSTACK_TYPE *pxTopOfStack, pdTASK_CODE pxCode, void *pvParameters )
\r
187 Place a few bytes of known values on the bottom of the stack.
\r
188 This is just useful for debugging and can be included if required.
\r
190 *pxTopOfStack = ( portSTACK_TYPE ) 0x1111;
\r
192 *pxTopOfStack = ( portSTACK_TYPE ) 0x2222;
\r
194 *pxTopOfStack = ( portSTACK_TYPE ) 0x3333;
\r
198 /* The msp430 automatically pushes the PC then SR onto the stack before
\r
199 executing an ISR. We want the stack to look just as if this has happened
\r
200 so place a pointer to the start of the task on the stack first - followed
\r
201 by the flags we want the task to use when it starts up. */
\r
202 *pxTopOfStack = ( portSTACK_TYPE ) pxCode;
\r
204 *pxTopOfStack = portFLAGS_INT_ENABLED;
\r
207 /* Next the general purpose registers. */
\r
208 *pxTopOfStack = ( portSTACK_TYPE ) 0x4444;
\r
210 *pxTopOfStack = ( portSTACK_TYPE ) 0x5555;
\r
212 *pxTopOfStack = ( portSTACK_TYPE ) 0x6666;
\r
214 *pxTopOfStack = ( portSTACK_TYPE ) 0x7777;
\r
216 *pxTopOfStack = ( portSTACK_TYPE ) 0x8888;
\r
218 *pxTopOfStack = ( portSTACK_TYPE ) 0x9999;
\r
220 *pxTopOfStack = ( portSTACK_TYPE ) 0xaaaa;
\r
222 *pxTopOfStack = ( portSTACK_TYPE ) 0xbbbb;
\r
224 *pxTopOfStack = ( portSTACK_TYPE ) 0xcccc;
\r
226 *pxTopOfStack = ( portSTACK_TYPE ) 0xdddd;
\r
228 *pxTopOfStack = ( portSTACK_TYPE ) 0xeeee;
\r
231 /* When the task starts is will expect to find the function parameter in
\r
233 *pxTopOfStack = ( portSTACK_TYPE ) pvParameters;
\r
236 /* The code generated by the mspgcc compiler does not maintain separate
\r
237 stack and frame pointers. The portENTER_CRITICAL macro cannot therefore
\r
238 use the stack as per other ports. Instead a variable is used to keep
\r
239 track of the critical section nesting. This variable has to be stored
\r
240 as part of the task context and is initially set to zero. */
\r
241 *pxTopOfStack = ( portSTACK_TYPE ) portNO_CRITICAL_SECTION_NESTING;
\r
243 /* Return a pointer to the top of the stack we have generated so this can
\r
244 be stored in the task control block for the task. */
\r
245 return pxTopOfStack;
\r
247 /*-----------------------------------------------------------*/
\r
249 portBASE_TYPE xPortStartScheduler( void )
\r
251 /* Setup the hardware to generate the tick. Interrupts are disabled when
\r
252 this function is called. */
\r
253 prvSetupTimerInterrupt();
\r
255 /* Restore the context of the first task that is going to run. */
\r
256 portRESTORE_CONTEXT();
\r
258 /* Should not get here as the tasks are now running! */
\r
261 /*-----------------------------------------------------------*/
\r
263 void vPortEndScheduler( void )
\r
265 /* It is unlikely that the MSP430 port will get stopped. If required simply
\r
266 disable the tick interrupt here. */
\r
268 /*-----------------------------------------------------------*/
\r
271 * Manual context switch called by portYIELD or taskYIELD.
\r
273 * The first thing we do is save the registers so we can use a naked attribute.
\r
275 void vPortYield( void ) __attribute__ ( ( naked ) );
\r
276 void vPortYield( void )
\r
278 /* We want the stack of the task being saved to look exactly as if the task
\r
279 was saved during a pre-emptive RTOS tick ISR. Before calling an ISR the
\r
280 msp430 places the status register onto the stack. As this is a function
\r
281 call and not an ISR we have to do this manually. */
\r
282 asm volatile ( "push r2" );
\r
285 /* Save the context of the current task. */
\r
286 portSAVE_CONTEXT();
\r
288 /* Switch to the highest priority task that is ready to run. */
\r
289 vTaskSwitchContext();
\r
291 /* Restore the context of the new task. */
\r
292 portRESTORE_CONTEXT();
\r
294 /*-----------------------------------------------------------*/
\r
297 * Hardware initialisation to generate the RTOS tick. This uses timer 0
\r
298 * but could alternatively use the watchdog timer or timer 1.
\r
300 static void prvSetupTimerInterrupt( void )
\r
302 /* Ensure the timer is stopped. */
\r
305 /* Run the timer of the ACLK. */
\r
308 /* Clear everything to start with. */
\r
311 /* Set the compare match value according to the tick rate we want. */
\r
312 TACCR0 = portACLK_FREQUENCY_HZ / configTICK_RATE_HZ;
\r
314 /* Enable the interrupts. */
\r
317 /* Start up clean. */
\r
323 /*-----------------------------------------------------------*/
\r
326 * The interrupt service routine used depends on whether the pre-emptive
\r
327 * scheduler is being used or not.
\r
330 #if configUSE_PREEMPTION == 1
\r
333 * Tick ISR for preemptive scheduler. We can use a naked attribute as
\r
334 * the context is saved at the start of vPortYieldFromTick(). The tick
\r
335 * count is incremented after the context is saved.
\r
337 interrupt (TIMERA0_VECTOR) prvTickISR( void ) __attribute__ ( ( naked ) );
\r
338 interrupt (TIMERA0_VECTOR) prvTickISR( void )
\r
340 /* Save the context of the interrupted task. */
\r
341 portSAVE_CONTEXT();
\r
343 /* Increment the tick count then switch to the highest priority task
\r
344 that is ready to run. */
\r
345 vTaskIncrementTick();
\r
346 vTaskSwitchContext();
\r
348 /* Restore the context of the new task. */
\r
349 portRESTORE_CONTEXT();
\r
355 * Tick ISR for the cooperative scheduler. All this does is increment the
\r
356 * tick count. We don't need to switch context, this can only be done by
\r
357 * manual calls to taskYIELD();
\r
359 interrupt (TIMERA0_VECTOR) prvTickISR( void );
\r
360 interrupt (TIMERA0_VECTOR) prvTickISR( void )
\r
362 vTaskIncrementTick();
\r