|
|||||||||||||||
FreeRTOS Support ArchiveThe FreeRTOS support forum is used to obtain active support directly from Real Time Engineers Ltd. In return for using our top quality software and services for free, we request you play fair and do your bit to help others too! Sign up to receive notifications of new support topics then help where you can.
Loading
[AVR] portYIELD_FROM_ISR should be providedPosted by BeginEnd on April 18, 2013 I think that there should be macro portYIELD_FROM_ISR and function vPortYieldFromISR() added to ATMega323 port. This is becouse vPortYield() uses "ret" to return, but if current contex was switched in vPortTickFromISR(), restored SREG do not have global interrupt flag set. RE: [AVR] portYIELD_FROM_ISR should be providedPosted by Richard on April 18, 2013 This (extremely old) port is explained in on the following (extremely old) web pages. I have only linked to the two relevant pages: http://www.freertos.org/implementation/a00016.html http://www.freertos.org/implementation/a00017.html SREG is saved and restored as part of the task context. When a task that is switched out from an interrupt is next executed it will be switched back into the interrupt (from exactly where it was switched out) - where it will execute its end of interrupt code setting SREG back to its required value. Likewise if a task is switched in from inside an interrupt it will start executing from wherever it was switched out - which may or may not be in an interrupt but its SREG will also be correct for wherever it ends up. Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|
|||||||||||||||
NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.
Meet Richard Barry and learn about running FreeRTOS on RISC-V at FOSDEM 2019
Version 10.1.1 of the FreeRTOS kernel is available for immediate download. MIT licensed.
View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.
FreeRTOS and other embedded software careers at AWS.
