... | ... | @@ -23,7 +23,7 @@ These tasks are run in background when no other task is running. |
|
|
|
|
|
They are implemented as threads, each one requiring a stack, thus consuming memory.
|
|
|
|
|
|
The number of tasks available to the user and their stack size can be set in `prj.conf` using respectively `CONFIG_OWNTECH_SCHEDULING_MAX_ASYNCHRONOUS_TASKS` and `CONFIG_OWNTECH_SCHEDULING_ASYNCHRONOUS_TASKS_STACK_SIZE`. Te more tasks available, the more stacks will be configured, consumuing memory. If you know precisely how many tasks of this kind your code use, it is thus a good thing to adapt the maximum number of tasks to this value in order to reduce memory usage. The default number of available tasks is 3, and stack size is 512.
|
|
|
The number of tasks available to the user and their stack size can be set in `prj.conf` using respectively `CONFIG_OWNTECH_SCHEDULING_MAX_ASYNCHRONOUS_TASKS` and `CONFIG_OWNTECH_SCHEDULING_ASYNCHRONOUS_TASKS_STACK_SIZE`. The more tasks available, the more stacks will be configured, consumuing memory. If you know precisely how many tasks of this kind your code use, it is thus a good thing to adapt the maximum number of tasks to this value in order to reduce memory usage. The default number of available tasks is 3, and stack size is 512.
|
|
|
|
|
|
If you do not plan to use such tasks, you can set `CONFIG_OWNTECH_SCHEDULING_ENABLE_ASYNCHRONOUS_TASKS` to `n`, fully disabling the functionality and freeing associated memory.
|
|
|
|
... | ... | |