|
|||||||||||||||
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
AVR32: portEnterCritical vs DisableInterruptsPosted by Jeff Henshaw on June 19, 2009 vportEnterCritical() disables all interrupts and then increments ulCriticalNesting. My question is when should I use one versus the other? I'm not sure what ulCriticalNesting is for, there's a number of things in the AVR32 port that don't match the documentation. Probably because the AVR32 is kinda weird. :-) Also, any issues using vportEnterCritical() before the scheduler is running? Thanks ! RE: AVR32: portEnterCritical vs DisableInterrPosted by Richard on June 19, 2009 The only method of disabling and enabling interrupts that should be used are calls to taskENTER_CRITICAL() and taskEXIT_CRITICAL() as these maintain a nesting count. You should not manipulate ulCriticalNesting directly, it is purely for use of the kernel. It is fine to use the macros before the scheduler has started, but interrupts will remain disabled until the scheduler has been started. Also note that some ports don't disable all interrupts, but only those up to the priority used by the kernel. Regards.
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.
