Embedded UML Forum » F.A.Q. » Whitepapers/Appnotes » Application Note: Strauss Stack Size Configuration
Application Note: Strauss Stack Size Configuration
2056 Betrachtungen
Seite:
1
Application Note: Strauss Stack Size Configuration
14.11.2008 16:28
Before you can inspect or specify various tasks, you need to understand the task usage in the RTOS adapters:
- the bridge task is is the heartbeat of the Realtime eXecution Framework. The bridge task periodically wakes up and schedules the events for the (other) tasks in the RXF.
- the main task is the task in which any object runs for which you did not specify in Rhapsody that its class is an active class:
- by default, a class is not active. Each object created from this class runs in the main task.
- for an object which is created via an active class, a new task is created.
- by default, a class is not active. Each object created from this class runs in the main task.
In RTOS based frameworks there are multiple places where to configure different stack sizes. Generally, there are different types of stacks:
- Stack used for the function main(), which is just used for initializing and starting the RTOS and creating the main task.
- Stack of the main task, which is used for the main task running all sequential parts of the Rhapsody generated code. Its required stacksize depends on the RXF and code executed on behalf of non-active classes.
- Stack for the bridge task. This stack can be relatively small because little code is executed in this task.
- Stacks for user tasks which are the result of active classes. The stacksize for such a task can be configured individually at the Rhapsody model level or you may use a default stack size
- Interrupt and target mode specific stacks
Stack Size for function main()
This stack setting is called
