RTOS Source Code Download Instructions

1. Please keep up to date by joining the announcements mailing list for infrequent comprehensive notifications. We respect your privacy, so do not provide email addresses to any third party. Every email sent contains unsubscribe instructions.

2. 
   Download the latest official release or a previous release from SourceForge, both of which are available as a standard zip file (.zip), and as a self extracting zip file (.exe). Alternatively obtain the source files directly from SVN.

   The FreeRTOS kernel is also available from AWS and via Github as part of the Amazon FreeRTOS operating system, and from various partner distributions.

3. Unzip the source code into a suitable directory – taking care to ensure the directory structure within the zip file is maintained. Please read the source code organisation and quick start guide pages to understand the directory structure and get up and running quickly.

4. The monitored support forum, known issue list, FAQ and version change description, all provide additional resources.

FreeRTOS Announcements Mailing List

You can also now follow FreeRTOS on Twitter for instant notifications.

Known Issues with the Current Release

Legacy Issues

• 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.

• AVR32 demos

  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.