gavin00 wrote on Thursday, September 08, 2011:
I don’t know how to assign the stack and heap size in FreeRTOSConfig.h
It seems I have to give a very huge heap size, but I don’t dynamically allocate any memory. Is the OS copy my code to HEAP? my code is already in RAM, why do the copy?
The Stack size should be task control block size, am I right? if I am right , then it should be just a couple of KB.
What’s the relation of FreeRTOS HEAP&Stack comparing to the C heap&stack?
gavin00 wrote on Thursday, September 08, 2011:
Sorry, my previous post is wrong.
This is the correct one:
I don’t know how to assign the TASK size and heap size in FreeRTOSConfig.h
It seems I have to give a very huge heap size, but I don’t dynamically allocate any memory. Is the OS copy my code to HEAP? my code is already in RAM, why do the copy?
The TASK size should be task control block size, am I right? if I am right , then it should be just a couple of KB.
What’s the relation of FreeRTOS HEAP&Stack comparing to the C heap&stack?
richard_damon wrote on Thursday, September 08, 2011:
Your PROGRAMS stack and heap size are normally set with compiler/linker options. Since you didn’t say which one you are using, it is hard to help you more on where to set those. If your program is using heap1.c or heap2.c, then size of the memory block that FreeRTOS uses for its heap is configured with a parameter in FreeRTOSConfig.h, this will NOT affect how much memory is allocated to the C library heap. Anything the linker report calls “heap” will be the C library heap, not the FreeRTOS heap which will look just like a chunk of statically declared memory usage (which is how it is implemented)
Your programs starting stack, is normally only used for your startup code, and in some ports, for the interrupt stack. It is NOT used by any of the tasks.
Task stacks are allocated from the FreeRTOS heap, which if you use heap3.c is the C library heap, otherwise it is the separate chunk of memory described previously.
modiallen wrote on Wednesday, August 15, 2012:
Hi richard,
i have here a question:
in code composer is the stack of the linker used for the startup code, i.e the main function? and is it used for the interrupts?
i am using code composer on msp430.
Regards.
davedoors wrote on Thursday, August 16, 2012:
in code composer is the stack of the linker used for the startup code
yes.
and is it used for the interrupts
No. The port does not use interrupt nesting so there is little to gain from that.
modiallen wrote on Wednesday, August 29, 2012:
Hi again,
i read in the dokumentation in another RTOS, that the msp430 dont have a stack for the ISR.
so the stack of every task will be used if the task will be interrupted with an ISR.
because of this, they recommended the user to define the stack of every task a little more bigger than the estimated space for every task.
i think this recommendation will be usefull for freertos-users too.
Best Regards.