The FreeRTOS kernel is now an MIT licensed AWS open source project, and these pages are being updated accordingly.

Quality RTOS & Embedded Software

About Contact Support FAQ Download

Menu

Quick Start

Supported MCUs

PDF Books

Trace Tools

Ecosystem

Quick Start Guide

Support Forum

⇓ Download Source ⇓

FreeRTOS+ Ecosystem

FreeRTOS+TCP:
Thread safe TCP/IP stack

SafeRTOS:
TUV certified RTOS

OpenRTOS:
Commercial Licensed RTOS

Fail Safe File System:
Ensures data integrity

FreeRTOS BSPs:
3rd party driver packages

Trace & Visualisation:
Tracealyzer for FreeRTOS

CLI:
Command line interface

WolfSSL SSL / TLS:
Networking security protocols

RTOS Training:
Delivered online or on-site

IO:
read(), write(), ioctl() interface

FreeRTOS+ Lab Projects

FreeRTOS+POSIX:
POSIX threading API

FreeRTOS+FAT:
Thread aware file system

Homepage | FAQ

FreeRTOS FAQ - How to get the most from the FreeRTOS support forum

This is a subsection of the full FAQ

Commercially licensed versions of FreeRTOS (OpenRTOS) come with professional support packages. While these are not available for FreeRTOS, FreeRTOS users can access the active and free support forum. I would encourage all users to assist by replying to support request posts that they feel confident in answering.

The Right Way to Post a Support Request

The support forum is a fantastic resource for FreeRTOS users, but how much you get out of it will depend on how you use it.

Note 1

The first thing to consider is - whether it is the right place to ask your question at all. The forum is there to support the FreeRTOS kernel and nothing else. For example, please don't post questions regarding the configuration of unrelated microcontroller peripherals or registers, or how to use your tools, or the best way to design your application.

Note 2

Next consider the subject of your post carefully. The more accurate it is the more likely you will receive a fast response. If possible, name the microcontroller you are using in the subject line. This will allow a more targeted audience. For example “tick interrupt not firing on MSP430” as a subject will alert all MSP430 experts that they may be able to assist. While a post with a subject like “newbie - please help” will probably not even get looked at by the majority of viewers.

Note 3

The body of the post must provide the information required to actually allow people to answer the question. This may include:

The microcontroller you are using - please state right from the outset if you are using a simulator.
The compiler you are using.
The version of FreeRTOS you are using.
Whether the standard (FreeRTOS provided) demos will execute on your hardware or not.
When your question relates to a demo project - whether you have modified the demo project code or project files in any way, and if so, how?

Note 4 - actually submitting a post

Finally, the body text must be fully descriptive but in the most concise way possible as long posts can be off putting. Where possible:

Post short snippets of code. Use the ‘codify' tags to ensure the formatting is maintained.
Detail what you have already investigated so people know you are not just being lazy. This will also prevent replies suggesting things you have tried already. For example, have you already searched the forum, have you read the microcontroller user manuals, etc.?
Describe exactly the issue you are facing.
If appropriate, also include instructions on how to replicate the issue.