|
|||||||||||||||
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
Setting up context for the schedulerPosted by Joseph Dupre on July 8, 2010 I use timers and interrupts prior to calling vTaskStartScheduler() as part of a startup routine. Aside from calling portDISABLE_INTERRUPTS(), is there any other cleanup required to define the proper context before starting the scheduler??? RE: Setting up context for the schedulerPosted by Dave on July 14, 2010 I'm not sure exactly what the question is, but as long as you don't try doing a context switch before the scheduler has started you should be ok. Normally interrupts will get disabled by calling an API function if the scheduler is not started in any case. RE: Setting up context for the schedulerPosted by Joseph Dupre on July 14, 2010 I'm just asking what the required state be when starting the scheduler for the first time. As far as I know (for an ARM), it's just: 1) interrupts disabled. 2) in supervisor mode. RE: Setting up context for the schedulerPosted by Dave on July 14, 2010 “1) interrupts disabled. That is correct. FreeRTOS will disable interrupts temporarily while the scheduler is being started in any case. Interrupts will be enabled when the first task actually starts executing (by default in any case).
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.
