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] [March 2007 Threads] coroutines schedulingPosted by Kirby W. Cartwright on March 7, 2007 People,
I've been looking at either using multitasking or coroutines from the FreeRTOS package.
I developed a test package with a task to blink the LEDs, and also a coroutine to blink the LEDs.
Everything works, but as part of my comparison I wanted to remove everything to do with tasking, and just use the coroutines module and its scheduler. I was not able to totally remove the "tasks.c" file.
Has anyone managed to use the coroutines file and scheduler separately?
Other than that the package is sweet.
Kirby W. Cartwright Sr. Firmware Design Engineer Invensys Climate Controls 8115 US 42 N Plain City, OH 43064 PH: (614)873-9476 FAX: (614)873-9290 mailto:kirby.cartwright@invensyscontrols.com
RE: coroutines schedulingPosted by embeddedc on March 8, 2007 Coroutines run in the idle task so you need at least the parts of the task code to create the idle task. The tick interrupt will still try to save and restore the task context during the interrupt, this might be the only reason why.
I'm not vary familiar with the coroutine functionality, but I think it should be possible to alter the code a bit so the task code is not required. In particular the preemptive tick should not be used, the cooperative tick is just a normal interrupt and does nothing with the context.
You could just set the idle task stack size to be very large and not create any other tasks. Then the only disadvantage would be the build would include some code that was not required. Removing unused symbols would help.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|