/*\r
- FreeRTOS V8.0.0:rc1 - Copyright (C) 2014 Real Time Engineers Ltd.\r
- All rights reserved\r
-\r
-\r
- ***************************************************************************\r
- * *\r
- * FreeRTOS tutorial books are available in pdf and paperback. *\r
- * Complete, revised, and edited pdf reference manuals are also *\r
- * available. *\r
- * *\r
- * Purchasing FreeRTOS documentation will not only help you, by *\r
- * ensuring you get running as quickly as possible and with an *\r
- * in-depth knowledge of how to use FreeRTOS, it will also help *\r
- * the FreeRTOS project to continue with its mission of providing *\r
- * professional grade, cross platform, de facto standard solutions *\r
- * for microcontrollers - completely free of charge! *\r
- * *\r
- * >>> See http://www.FreeRTOS.org/Documentation for details. <<< *\r
- * *\r
- * Thank you for using FreeRTOS, and thank you for your support! *\r
- * *\r
- ***************************************************************************\r
-\r
-\r
- This file is part of the FreeRTOS distribution.\r
-\r
- FreeRTOS is free software; you can redistribute it and/or modify it under\r
- the terms of the GNU General Public License (version 2) as published by the\r
- Free Software Foundation AND MODIFIED BY the FreeRTOS exception.\r
- >>>NOTE<<< The modification to the GPL is included to allow you to\r
- distribute a combined work that includes FreeRTOS without being obliged to\r
- provide the source code for proprietary components outside of the FreeRTOS\r
- kernel. FreeRTOS is distributed in the hope that it will be useful, but\r
- WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY\r
- or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for\r
- more details. You should have received a copy of the GNU General Public\r
- License and the FreeRTOS license exception along with FreeRTOS; if not it\r
- can be viewed here: http://www.freertos.org/a00114.html and also obtained\r
- by writing to Richard Barry, contact details for whom are available on the\r
- FreeRTOS WEB site.\r
-\r
- 1 tab == 4 spaces!\r
-\r
- http://www.FreeRTOS.org - Documentation, latest information, license and\r
- contact details.\r
-\r
- http://www.SafeRTOS.com - A version that is certified for use in safety\r
- critical systems.\r
-\r
- http://www.OpenRTOS.com - Commercial support, development, porting,\r
- licensing and training services.\r
-*/\r
+ * FreeRTOS Kernel V10.3.0\r
+ * Copyright (C) 2020 Amazon.com, Inc. or its affiliates. All Rights Reserved.\r
+ *\r
+ * Permission is hereby granted, free of charge, to any person obtaining a copy of\r
+ * this software and associated documentation files (the "Software"), to deal in\r
+ * the Software without restriction, including without limitation the rights to\r
+ * use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of\r
+ * the Software, and to permit persons to whom the Software is furnished to do so,\r
+ * subject to the following conditions:\r
+ *\r
+ * The above copyright notice and this permission notice shall be included in all\r
+ * copies or substantial portions of the Software.\r
+ *\r
+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR\r
+ * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS\r
+ * FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR\r
+ * COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER\r
+ * IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN\r
+ * CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.\r
+ *\r
+ * http://www.FreeRTOS.org\r
+ * http://aws.amazon.com/freertos\r
+ *\r
+ * 1 tab == 4 spaces!\r
+ */\r
\r
.text\r
.arm\r
.global FreeRTOS_IRQ_Handler\r
.global FreeRTOS_SWI_Handler\r
.global vPortRestoreTaskContext\r
- .global vPortInstallFreeRTOSVectorTable\r
\r
\r
\r
\r
.macro portRESTORE_CONTEXT\r
\r
- /* Switch to system mode. */\r
- CPS #SYS_MODE\r
-\r
/* Set the SP to point to the stack of the task being restored. */\r
LDR R0, pxCurrentTCBConst\r
LDR R1, [R0]\r
\r
\r
/******************************************************************************\r
- * SVC handler is used to start the scheduler and yield a task.\r
+ * SVC handler is used to start the scheduler.\r
*****************************************************************************/\r
.align 4\r
.type FreeRTOS_SWI_Handler, %function\r
portSAVE_CONTEXT\r
LDR R0, vTaskSwitchContextConst\r
BLX R0\r
+ portRESTORE_CONTEXT\r
+\r
\r
+/******************************************************************************\r
+ * vPortRestoreTaskContext is used to start the scheduler.\r
+ *****************************************************************************/\r
.type vPortRestoreTaskContext, %function\r
vPortRestoreTaskContext:\r
+ /* Switch to system mode. */\r
+ CPS #SYS_MODE\r
portRESTORE_CONTEXT\r
\r
.align 4\r
LDR r0, [r2]\r
\r
/* Ensure bit 2 of the stack pointer is clear. r2 holds the bit 2 value for\r
- future use. */\r
+ future use. _RB_ Does this ever actually need to be done provided the start\r
+ of the stack is 8-byte aligned? */\r
MOV r2, sp\r
AND r2, r2, #4\r
SUB sp, sp, r2\r
\r
- /* Call the interrupt handler. */\r
- PUSH {r0-r3, lr}\r
+ /* Call the interrupt handler. r4 pushed to maintain alignment. */\r
+ PUSH {r0-r4, lr}\r
LDR r1, vApplicationIRQHandlerConst\r
BLX r1\r
- POP {r0-r3, lr}\r
+ POP {r0-r4, lr}\r
ADD sp, sp, r2\r
\r
CPSID i\r
next. */\r
portRESTORE_CONTEXT\r
\r
+\r
+/******************************************************************************\r
+ * If the application provides an implementation of vApplicationIRQHandler(),\r
+ * then it will get called directly without saving the FPU registers on\r
+ * interrupt entry, and this weak implementation of\r
+ * vApplicationIRQHandler() will not get called.\r
+ *\r
+ * If the application provides its own implementation of\r
+ * vApplicationFPUSafeIRQHandler() then this implementation of\r
+ * vApplicationIRQHandler() will be called, save the FPU registers, and then\r
+ * call vApplicationFPUSafeIRQHandler().\r
+ *\r
+ * Therefore, if the application writer wants FPU registers to be saved on\r
+ * interrupt entry their IRQ handler must be called\r
+ * vApplicationFPUSafeIRQHandler(), and if the application writer does not want\r
+ * FPU registers to be saved on interrupt entry their IRQ handler must be\r
+ * called vApplicationIRQHandler().\r
+ *****************************************************************************/\r
+\r
+.align 4\r
+.weak vApplicationIRQHandler\r
+.type vApplicationIRQHandler, %function\r
+vApplicationIRQHandler:\r
+ PUSH {LR}\r
+ FMRX R1, FPSCR\r
+ VPUSH {D0-D15}\r
+ VPUSH {D16-D31}\r
+ PUSH {R1}\r
+\r
+ LDR r1, vApplicationFPUSafeIRQHandlerConst\r
+ BLX r1\r
+\r
+ POP {R0}\r
+ VPOP {D16-D31}\r
+ VPOP {D0-D15}\r
+ VMSR FPSCR, R0\r
+\r
+ POP {PC}\r
+\r
+\r
ulICCIARConst: .word ulICCIAR\r
ulICCEOIRConst: .word ulICCEOIR\r
ulICCPMRConst: .word ulICCPMR\r
vTaskSwitchContextConst: .word vTaskSwitchContext\r
vApplicationIRQHandlerConst: .word vApplicationIRQHandler\r
ulPortInterruptNestingConst: .word ulPortInterruptNesting\r
+vApplicationFPUSafeIRQHandlerConst: .word vApplicationFPUSafeIRQHandler\r
\r
.end\r
\r
projects / freertos / blobdiff