Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem


vPortSuppressTicksAndSleep semantics

Posted by J Hamilton on June 18, 2013
FreeRTOS 7.4.2, Atmel SAM3U (ARM Cortex-M3), Atmel Studio 6.1
HI there, I am working on modifying the SAM4L low-power tickless idle implementation (from the demo) for the SAM3U and I'm finding the comments around the interrupt disable confusing in the demo version of

// Enter a critical section but don't use the taskENTER_CRITICAL() method as
// that will mask interrupts that should exit sleep mode.
__asm volatile( "cpsid i\n\t"
"dsb\n\t" );

Essentially the same thing shows up in the standard CM3 port code.

If I understand the assembly correctly, this is disabling ALL interrupts (except NMI & faults) so the timer used to wake the processor doesn't get it's interrupt handled until "
cpsie i
" is called later. HOWEVER, the comments indicate that the quoted code will somehow mask off fewer interrupts than
. I looked at the code involved there, and it just changes the BASEPRI register to some intermediate value, which, if I understand correctly, will mask off interrupts with lower priority (higher numeric value on a CM3) than BASEPRI, but not all interrupts (unless it is set to zero).

Am I missing something or are these comments not applicable and misleading?


RE: vPortSuppressTicksAndSleep semantics

Posted by J Hamilton on June 18, 2013
Oops, sorry about the misuse of the code tags. Didn't realize they would format that way.

RE: vPortSuppressTicksAndSleep semantics

Posted by Richard on June 19, 2013
When in a low power mode the Cortex-M3 *will* allow an interrupt to bring the MCU out of sleep mode even when interrupts are globally disabled using the i bit in the CPSR (set by the CPSIE i instruction). The interrupt will not actually be processed by the MCU until interrupts are again re-enabled.

However....only interrupts that are not masked by the BASEPRI setting will do this. Therefore, if you use taskENTER_CRITICAL() interrupts will remain enabled, but the interrupt you want to bring the system out of sleep mode will be masked, and therefore the MCU will not exit sleep mode even though the interrupt fired.


RE: vPortSuppressTicksAndSleep semantics

Posted by J Hamilton on June 20, 2013
Thank you Richard! That clarifies things immensely.

[ Back to the top ]    [ About FreeRTOS ]    [ Privacy ]    [ Sitemap ]    [ ]

Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.

Latest News

FreeRTOS v10.2.0 is available for immediate download. MIT licensed, and including RISC-V and ARMv8-M (Cortex-M33) demos.

NXP tweet showing LPC5500 (ARMv8-M Cortex-M33) running FreeRTOS.

View a recording of the "OTA Update Security and Reliability" webinar, presented by TI and AWS.


FreeRTOS and other embedded software careers at AWS.

FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Cadence Tensilica Cortes

Espressif ESP32

IAR Partner

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers





STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

OpenRTOS and SafeRTOS

Xilinx Microblaze and Zynq partner