|
|||||||||||||||
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
Scheduler behavior when only one task definedPosted by awillson on January 22, 2016 Hello, I looked through various documents and could not find how the scheduler might work, when only one task is defined. For example, take a typical super-loop routine and make it a task, the only task, such that it runs forever and never blocks/suspends. Will the scheduler even need to run after the initial call to vTaskStartScheduler() ? How will it behave? Thanks in advance. Scheduler behavior when only one task definedPosted by davedoors on January 22, 2016 The scheduler behaves the same however many tasks are created. If you create only one task that never blocks and above tskIDLEPRIORITY then only your task will run. If you create it at tskIDLE priority and configUSETIMESLICING is 1 then both your task and the idle task will run. If you create it at tskIDLEPRIORITY and configUSETIMESLICING is 0 then only your task will run, but the idle task might run once first.
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.
