2 FreeRTOS V9.0.0 - Copyright (C) 2016 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
71 extern volatile TCB_t * volatile pxCurrentTCB;
\r
72 extern void vTaskSwitchContext( void );
\r
75 * Saves the stack pointer for one task into its TCB, calls
\r
76 * vTaskSwitchContext() to update the TCB being used, then restores the stack
\r
77 * from the new TCB read to run the task.
\r
79 void portSWITCH_CONTEXT( void );
\r
82 * Load the stack pointer from the TCB of the task which is going to be first
\r
83 * to execute. Then force an IRET so the registers and IP are popped off the
\r
86 void portFIRST_CONTEXT( void );
\r
88 /* There are slightly different versions depending on whether you are building
\r
89 to include debugger information. If debugger information is used then there
\r
90 are a couple of extra bytes left of the ISR stack (presumably for use by the
\r
91 debugger). The true stack pointer is then stored in the bp register. We add
\r
92 2 to the stack pointer to remove the extra bytes before we restore our context. */
\r
96 #pragma aux portSWITCH_CONTEXT = "mov ax, seg pxCurrentTCB" \
\r
98 "les bx, pxCurrentTCB" /* Save the stack pointer into the TCB. */ \
\r
99 "mov es:0x2[ bx ], ss" \
\r
100 "mov es:[ bx ], sp" \
\r
101 "call vTaskSwitchContext" /* Perform the switch. */ \
\r
102 "mov ax, seg pxCurrentTCB" /* Restore the stack pointer from the TCB. */ \
\r
104 "les bx, dword ptr pxCurrentTCB" \
\r
105 "mov ss, es:[ bx + 2 ]" \
\r
106 "mov sp, es:[ bx ]" \
\r
107 "mov bp, sp" /* Prepair the bp register for the restoration of the SP in the compiler generated portion of the ISR */ \
\r
112 #pragma aux portFIRST_CONTEXT = "mov ax, seg pxCurrentTCB" \
\r
114 "les bx, dword ptr pxCurrentTCB" \
\r
115 "mov ss, es:[ bx + 2 ]" \
\r
116 "mov sp, es:[ bx ]" \
\r
117 "add sp, 0x0002" /* Remove the extra bytes that exist in debug builds before restoring the context. */ \
\r
126 #pragma aux portSWITCH_CONTEXT = "mov ax, seg pxCurrentTCB" \
\r
128 "les bx, pxCurrentTCB" /* Save the stack pointer into the TCB. */ \
\r
129 "mov es:0x2[ bx ], ss" \
\r
130 "mov es:[ bx ], sp" \
\r
131 "call vTaskSwitchContext" /* Perform the switch. */ \
\r
132 "mov ax, seg pxCurrentTCB" /* Restore the stack pointer from the TCB. */ \
\r
134 "les bx, dword ptr pxCurrentTCB" \
\r
135 "mov ss, es:[ bx + 2 ]" \
\r
136 "mov sp, es:[ bx ]"
\r
139 #pragma aux portFIRST_CONTEXT = "mov ax, seg pxCurrentTCB" \
\r
141 "les bx, dword ptr pxCurrentTCB" \
\r
142 "mov ss, es:[ bx + 2 ]" \
\r
143 "mov sp, es:[ bx ]" \
\r
projects / freertos / blob