FreeRTOS Real Time Kernel (RTOS)

Hello, According to documentation individual task stacks are allocated from the Total Heap size we will be define and allocate in FreeRTOSConfig.h. Is there any possibility, of the addition of all individual task stacks exceeding the amount of total heap allocation? Thank you.

Is there any possibility, of the addition of all individual task stacks exceeding the amount of total heap allocation? Naturally, yes, there is a limited amount of RAM and a user can attempt to create an infinite amount of tasks. heap_1.c and heap_2.c both have a function xPortGetFreeHeapSize() that allows you to query the stack remaining. heap_3.c uses malloc() and free() so FreeRTOS itself cannot obtain the free space. There is also a malloc failed hook function that can be defined that will be called when an allocation fails. Regards.

Further, Can anybody explain how does the allocated Total Heap size is being used? Are there any documentation to follow up? Thank you.

Sorry - I'm not sure I fully understand your question. Have you seen this page: http://www.freertos.org/a00111.html Regards.

anuradha123, The total heap size parameter is used in heap_1 and heap_2 to define the size of the heap to be created. For heap_3 you need to use the method provided by your compiler/linker to set this, and the parameter in FreeRTOS is ignored.

All, Thanks for the replies. But I still did not get any answer to my original question, Further, Can anybody explain how does the allocated Total Heap size is being used? Are there any documentation to follow up? Information provided in FreeRTOS site and manual are inadequate. I am in interested of finding out, in detail how the task stack is being used. Thank you.

Forgive us, but your question was not clear. Each task has its own stack, that is used by the compiler to store things like function call return addresses and local variables. There is nothing different about the stack used by a task than any other stack - for example the stack allocated by the linker for use by the main() function. Regards.

There is nothing different about the stack used by a task than any other stack - for example the stack allocated by the linker for use by the main() function. Does this means that each task behaves like main (in terms stack uses) that particular task stack also caters the requirement of nested function calls etc. Can we get a pictorial depiction of this, some book or online references ?

http://sourceforge.net/projects/freertos/forums/forum/382005/topic/6687087