Download the latest official release or a previous release of FreeRTOS from SourceForge as a standard zip (.zip) or a self-extracting zip file (.exe). The source code is also available directly from SVN and now also GitHub. Unzip the source code while making sure to maintain the folder structure. Please read the documentation referenced below to understand the directory structure and get started quickly!
Getting started with the FreeRTOS kernel
Choose, compile, and build a FreeRTOS kernel demoLearn More
Getting started with an IoT Reference Integration
IoT Reference Integrations are pre-integrated FreeRTOS projects ported to microcontroller-based evaluation boards that demonstrate end to end connectivity to the cloud. IoT Reference Integrations help save months of development effort and accelerate time to market.Learn More
Getting started with FreeRTOS Libraries
FreeRTOS provides a collection of MIT licensed libraries available for use in resource-constrained devices across all industries. FreeRTOS libraries are tested and optimized for use with the FreeRTOS kernel.Learn More
Interact with and get support from the FreeRTOS community and Amazon Web Services (AWS)Learn More
Frequently Asked QuestionsLearn More
Known Issues with the Current Release
Also see security patches.
Coldfire V2 CodeWarrior port
The Coldfire V2 CodeWarrior code will not run with the latest (Eclipse) based CodeWarrior tools. A fix is posted on the support forum (post 4), and will be incorporated into the main release in due course.
Coldfire V1 CodeWarrior port
The Coldfire V1 CodeWarrior projects will not automatically update to later CodeWarrior versions unless all unnecessary files are deleted from the FreeRTOS/Source directory first. See this support thread for more information.
MSP430 CrossWorks and GCC demos
The CrossWorks demo has not yet been updated to use CrossWorks V2.0 or later. The GCC demo has not yet been updated to use the latest MSPGCC compiler version.
The IAR Embedded Workbench demos for the AVR32 will not currently build if you are using a later version of the IAR tool chain. The issue is caused by changes to macro names within the compiler header files.
Silicon Labs SDCC ports
Unfortunately these will not work with the latest compiler versions. The compiler version used to generate the port is now rather old, but is stated on the port documentation page.