2 FreeRTOS V7.4.0 - Copyright (C) 2013 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
33 >>>>>>NOTE<<<<<< The modification to the GPL is included to allow you to
\r
34 distribute a combined work that includes FreeRTOS without being obliged to
\r
35 provide the source code for proprietary components outside of the FreeRTOS
\r
38 FreeRTOS is distributed in the hope that it will be useful, but WITHOUT ANY
\r
39 WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS
\r
40 FOR A PARTICULAR PURPOSE. See the GNU General Public License for more
\r
41 details. You should have received a copy of the GNU General Public License
\r
42 and the FreeRTOS license exception along with FreeRTOS; if not itcan be
\r
43 viewed here: http://www.freertos.org/a00114.html and also obtained by
\r
44 writing to Real Time Engineers Ltd., contact details for whom are available
\r
45 on the FreeRTOS WEB site.
\r
49 ***************************************************************************
\r
51 * Having a problem? Start by reading the FAQ "My application does *
\r
52 * not run, what could be wrong?" *
\r
54 * http://www.FreeRTOS.org/FAQHelp.html *
\r
56 ***************************************************************************
\r
59 http://www.FreeRTOS.org - Documentation, books, training, latest versions,
\r
60 license and Real Time Engineers Ltd. contact details.
\r
62 http://www.FreeRTOS.org/plus - A selection of FreeRTOS ecosystem products,
\r
63 including FreeRTOS+Trace - an indispensable productivity tool, and our new
\r
64 fully thread aware and reentrant UDP/IP stack.
\r
66 http://www.OpenRTOS.com - Real Time Engineers ltd license FreeRTOS to High
\r
67 Integrity Systems, who sell the code with commercial support,
\r
68 indemnification and middleware, under the OpenRTOS brand.
\r
70 http://www.SafeRTOS.com - High Integrity Systems also provide a safety
\r
71 engineered and independently SIL3 certified version for use in safety and
\r
72 mission critical applications that require provable dependability.
\r
78 typedef void tskTCB;
\r
79 extern volatile tskTCB * volatile pxCurrentTCB;
\r
80 extern void vTaskSwitchContext( void );
\r
83 * Saves the stack pointer for one task into its TCB, calls
\r
84 * vTaskSwitchContext() to update the TCB being used, then restores the stack
\r
85 * from the new TCB read to run the task.
\r
87 void portSWITCH_CONTEXT( void );
\r
90 * Load the stack pointer from the TCB of the task which is going to be first
\r
91 * to execute. Then force an IRET so the registers and IP are popped off the
\r
94 void portFIRST_CONTEXT( void );
\r
96 /* There are slightly different versions depending on whether you are building
\r
97 to include debugger information. If debugger information is used then there
\r
98 are a couple of extra bytes left of the ISR stack (presumably for use by the
\r
99 debugger). The true stack pointer is then stored in the bp register. We add
\r
100 2 to the stack pointer to remove the extra bytes before we restore our context. */
\r
102 #define portSWITCH_CONTEXT() \
\r
103 asm { mov ax, seg pxCurrentTCB } \
\r
104 asm { mov ds, ax } \
\r
105 asm { les bx, pxCurrentTCB } /* Save the stack pointer into the TCB. */ \
\r
106 asm { mov es:0x2[ bx ], ss } \
\r
107 asm { mov es:[ bx ], sp } \
\r
108 asm { call far ptr vTaskSwitchContext } /* Perform the switch. */ \
\r
109 asm { mov ax, seg pxCurrentTCB } /* Restore the stack pointer from the TCB. */ \
\r
110 asm { mov ds, ax } \
\r
111 asm { les bx, dword ptr pxCurrentTCB } \
\r
112 asm { mov ss, es:[ bx + 2 ] } \
\r
113 asm { mov sp, es:[ bx ] }
\r
115 #define portFIRST_CONTEXT() \
\r
116 __asm { mov ax, seg pxCurrentTCB } \
\r
117 __asm { mov ds, ax } \
\r
118 __asm { les bx, dword ptr pxCurrentTCB } \
\r
119 __asm { mov ss, es:[ bx + 2 ] } \
\r
120 __asm { mov sp, es:[ bx ] } \
\r
projects / freertos / blob