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] [May 2006 Threads] taskYIELD from non-ISR routine on an MSP430Posted 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.
Thanks RJ
RE: taskYIELD from non-ISR routine on an MSP430Posted 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.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|