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] [December 2015 Threads] Detecting if a task is done executing what's in the for loop when blockedPosted by pugglewuggle on December 17, 2015 I have a task the blocks on xQueueReceive for portMAX_DELAY and I use several other blocks inside that task to aquire mutexes and such. Is there a reliable way to tell if the task has finished with the for loop and is waiting for the main queue receive vs if the task is waiting on an internal block such as waiting for a mutex? My first thought is to use a volatile bool variable to indicate this, setting to isRunning = true at the beginning and isRunning = false at the end of the for loop but I'm not sure that's the best way. How would you do this? If I did use a volatile bool does the possibility exist that it could ever be inconsistent due to a context switch/half-completed write/read?
Detecting if a task is done executing what's in the for loop when blockedPosted by pugglewuggle on December 17, 2015 Umm looks like the answer is a mutex. Am I on the right track?
Detecting if a task is done executing what's in the for loop when blockedPosted by rtel on December 18, 2015 A volatile boolean would definitely work. There is also a feature request open at the moment that would allow you to query which object a task is blocked on - but that is not implemented yet.
Regards.
Detecting if a task is done executing what's in the for loop when blockedPosted by pugglewuggle on December 18, 2015 Gotcha. Just curious... since volatile is not in itself thread-safe, is it better to use a mutex and have each task lock/unlock when it's done with what it's doing and block until the mutex is available?
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|