Quality RTOS & Embedded Software

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


taskYIELD from non-ISR routine on an MSP430

Posted by Nobody/Anonymous on May 3, 2006
Dear dispensers of wisdom,

The implementation of taskYIELD for the MSP430 GCC port calls vPortYield.
To make the stack look like the task was pre-empted by an ISR, vPortYield does the following:

asm volatile ("push r2"); // Save status register
_DINT(); // Disable interrupt.
portSAVE_CONTEXT(); // Save the context etc.

However, since taskYIELD is not called from an ISR, the Program Counter is not saved (register r0).

So if this context is restored, how could the task resume from the yield point.


RE: taskYIELD from non-ISR routine on an MSP430

Posted by Nobody/Anonymous on May 3, 2006
I guess it would be saved automatically as the function call return. The saving of r2 is probably the only difference between the function call stack frame and an interrupt stack frame.

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

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

Latest News

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

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.

FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

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