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] [May 2008 Threads] Creating tasks after the scheduler is startedPosted by Richard on May 7, 2008 [moved from private email]
Is it possible when the scheduler is running to create another task? In all the demo's I can't find an example when the scheduler is running to create more tasks.
For example: - Normally: First main -> Start Tasks -> Create those Tasks -> Start Scheduler. - What I want: First main -> Start Tasks -> Create those Tasks -> Start Scheduler -> Create Another Task when needed.
RE: Creating tasks after the scheduler is startedPosted by Richard on May 7, 2008 Yes - you can create and tasks after the scheduler has been started. You call xTaskCreate() in the normal way. The file FreeRTOS/Demo/Common/Minimal/death.c demonstrates this (the name comes from the fact that tasks are dynamically created then killed).
The thing to watch out for is memory fragmentation. When you create a task memory is allocated, when you delete a task it is freed, so doing this continuously can result in fragmentation problems. If the memory cannot be allocated then the task cannot be freed. If the tasks you create and delete all have the same stack size, and these are the only dynamically created/deleted objects then this might not be a problem.
Note that if you are using heap_1.c then memory cannot be re-allocated. See http://www.freertos.org/a00111.html for more information.
Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|