davedoors wrote on Friday, August 12, 2011:
> Hello estimated colleagues. I am considering the use of FreeRTOS for an upcoming
> project (switching from ThreadX)
Why do you want to switch from ThreadX?
> and I have a few questions regarding its features
> that I need answered before I proceed. Can any of you check the following list
> and tell me whether these features are available? Your help is greatly
The information you want is all on the web site. Start here
http://www.freertos.org/FreeRTOS_Features.html Normally, if a feature is not explicitly provided, you can use other features to achieve the same effect.
> -Fixed size memory management
Apparently there used to be, but people found it too complicated. See
> -Signal a task without requiring a semaphore
> -Send messages to a task without needing a message queue
If you mean a posix style signal, then no.
Remember in FreeRTOS code size is king. Queues are used as the base primitive for all task to task and task to interrupt coms, and queues have event management built in.
> -Is it ROMable?
Yes. What isn’t?
> -ASCII names for each kernel object?
Tasks and timers by default. Queues and the various semaphore types can be added to a registry with an ascii name.
> -Task registers
> -Built-in performance measurement
> -User definable hook functions
Task switch hooks (definable per task), idle hooks, tick hooks, malloc fail hooks, stack overflow hooks.
> -Time stamps on posts
You can post a structure that has a time stamp you add yourself.
> -Built-in Kernel Awareness support
The kernel is aware of itself, yes.
> -optimizable scheduler
There are features that allow memory use to be inspected and so optimised. The kernel is configurable too, and you have all the source code.
> -tick handling at task level
> -Number of services?