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 2006 Threads] Task switchPosted by Nobody/Anonymous on May 4, 2006 Hi,
i use the RTOS 3.2.2 with an Atmel SAM7. In code there are 3 tasks with the same priority and they can use the same hardware (for example SPI Interface ). If a task want's to use the hardware it checks a flag and use the the hardware (with setting and clearing of the flag) or it waits until the flag is cleared. This works fine without any problems. Depending on the hardware the waiting time can be very short and i don't want to use vTaskDelay(1).
Is it better to use vTaskSwitchContext() instead or is it not recommended.
Thanks for the help.
Regards
Rainer
RE: Task switchPosted by Nobody/Anonymous on May 4, 2006 I think maybe you should use a semaphore instead of a flag to avoid race conditions.
Never call vTaskSwitchContext()!!!!!! Use taskYIELD() instead.
You could raise the priority of the task that has the semaphore, then lower it again before it gives it back. This would prevent the other tasks from having to poll the flag.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|