FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [February 2009 Threads] Memory allocation?Posted by tord lindner on February 25, 2009 HI,
I'm a bit confused about memory allocation, everything created through the API I expect be allocated within the heap, all variables which are within a tasks/functions are on the stack. That is, on the heap again. But, variables declared outside any function are they inside or outside the heap declared in FreeRTOSConfig.h? What about declarations in Main before starting the scheduler?
BR Tord
RE: Memory allocation?Posted by Dave on February 25, 2009 The heap is used to allocate the stacks that are used by the tasks. Therefore stack variables used by the tasks end up in the heap area, really they are on the stack its just that the stack came from the heap.
In main() the compiler will just use the stack as normal. This will be the stack used by main() as specified in the linker script. The compiler knows nothing about FreeRTOS or how it manages memory it just uses the data section and stack as normal.
RE: Memory allocation?Posted by tord lindner on February 25, 2009 So all variables defined outside a function/task goes on the normal stack and the rest in the heap.? normally, are these two "stacks" going form top/button and hopefully never meet in the middle?
BR Tord
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|