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] [July 2015 Threads]
In freertosv8.2.1freertossourceportableiararmcm3, I have a question about the __weak void vPortSuppressTicksAndSleep( TickTypet xExpectedIdleTime ) function.
line 408: /* Enter a critical section but don't use the taskENTERCRITICAL()
method as that will mask interrupts that should exit sleep mode. */
__disableinterrupt();
vPortSuppressTicksAndSleep( TickType_t xExpectedIdleTime ) means disable other interrupt except for systick, and use systick to wake up mcu from sleep mode.
but in my opinion, _disableinterrupt() is IAR intrinsic function, and equal with cpsid i. It means any interrupt which priority below 0(logically) will be disabled. So how can systick wake MCU up?
This information is provided in the Cortex-M technical reference manual, from ARM, so is not really a software question - however the answer is that interrupts will still bring the CPU out of sleep mode even when they are globally disabled in the core.
Is your mean that even the systick interrupt is masked, systick also will wake MCU up ? If so, the system will not enter the systick handler, just only bring CPU out of sleep mode. Is it right?
Yes.
Please read the hardware documentation.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.