|
|||||||||||||||
FreeRTOS Support ArchiveThe 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.
Loading
difference between taskENTER_CRITICAL and tasPosted by Yuhui Lin on July 21, 2010 I'm a little confused about the different between taskENTER_CRITICAL and taskDISABLE_INTERRUPTS. I read the user manual, it said "they working by disabling interrupt......Pre-emptive switch can only occur from interrupt, so as long as interrupt remains disabled, the task called the taskENTER_CRITICAL can guaranteed to remain in running state ". From my understanding, both of them can result in disabled interrupt and context switch. Any tips? RE: difference between taskENTER_CRITICAL and tasPosted by Dave on July 21, 2010 ENTER_CRITICAL() keeps a count of the call nesting and is the only one you should use really. It normally calls DISABLE_INTERRUPTS internally. Some but not all ports can still context switch with interrupts disabled, but not from in a preemptive way because with interrupts being disabled they cannot be preempted. RE: difference between taskENTER_CRITICAL and tasPosted by Yuhui Lin on July 21, 2010 thanks davedoors for your answer, but I am still not very clear. Is there any 'extra benefit' ENTER_CRITICAL could provides, besides disabled interrupt. They seem to be the same to me. I can't tell the differences betweens them. Then I start wonder why do I need two different interface, if they share nearly the same features. I guess there should be something unknown to me. RE: difference between taskENTER_CRITICAL and tasPosted by Richard Damon on July 21, 2010 The big difference is the ENTER/EXIT Critical takes into account nesting, Enable/Disable interrupt do not. Thus ENTER /* Interrupts now disabled */ ENTER EXIT /* Interrupts still disabled */ EXIT /* unwound all the critical sections, so interrupt now enabled */ While with DISABLE you would get DISABLE /* Interrupts now disabled */ DISABLE ENABLE /* Interrupts now reenabled even though we disabled twice */ ENABLE RE: difference between taskENTER_CRITICAL and tasPosted by Yuhui Lin on July 21, 2010 Aha~ thanks~ I got it now. That's the reason I saw push and pop assembly code in one of the porting file for ENTER_CRITICAL and EXIT_CRITICAL RE: difference between taskENTER_CRITICAL and tasPosted by Richard Damon on July 21, 2010 Critical sections should not be storing the "stacking" of them on the stack, but tend to use a counter. Some ports may use push/pop to access a status/control register. One thing to note is that a critical section may not disable ALL interrupts, but may just disable those interrupts at a level which is allowed to interact with the kernel, and this is sometimes done by setting the current interrupt priority level in the hardware.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|
|||||||||||||||
NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.
Meet Richard Barry and learn about running FreeRTOS on RISC-V at FOSDEM 2019
Version 10.1.1 of the FreeRTOS kernel is available for immediate download. MIT licensed.
View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.
FreeRTOS and other embedded software careers at AWS.
