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] [January 2007 Threads] portENTER_CRITICAL() ------ vTaskSuspendAll()Posted by Nobody/Anonymous on January 10, 2007 what happens if I change all "portENTER_CRITICAL()" to "vTaskSupendAll()"?? will this be a risk? the problem is that I don't want to block that many interrupts.
RE: portENTER_CRITICAL() ------ vTaskSuspendAll()Posted by Nobody/Anonymous on January 10, 2007 I think you could change some, but not all. The ones in QueueSend and QueueReceive have quite a specific interaction with TaskSuspendAll for example. Also task delete I think would not work. Basically each would have to be looked at in turn. It would not necessarily improve efficiency though. For very short critical sections the enter/exit critical are preferable.
RE: portENTER_CRITICAL() ------ vTaskSuspendAll()Posted by embeddedc on January 10, 2007 You cannot yield from within a vTaskSupsendAll() vTaskResumeAll() pair. When you do this the yield is pended until the vTaskResumeAll() call.
RE: portENTER_CRITICAL() ------ vTaskSuspendAPosted by Nobody/Anonymous on January 10, 2007 ok than I think that I will only use it for my functions. thanks for the fast response!
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|