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] [February 2014 Threads] separate interrupt stack on IAR MSP430X port?Posted by gmenhennitt on February 5, 2014 Can somebody please tell me whether the IAR MSP430X port uses a separate stack for interrupts?
In http://sourceforge.net/p/freertos/discussion/382005/thread/e0f63bdf/?limit=25#bdcf, Richard said that "all the newer ports maintain a separate interrupt stack". Is the MSP430X such a newer one? I had a look at the port's code and I can't see any evidence of a separate stack. Also, setting a breakpoint in an interrupt routine looks like it's using the task stack.
Thanks,
Graham
separate interrupt stack on IAR MSP430X port?Posted by rtel on February 5, 2014 No it doesn't. Generally a separate interrupt stack is most useful when interrupt nesting is supported. When interrupt nesting can occur the stack can get quite big, and it is therefore wasteful to allocate enough stack to each task to contain a fully nested interrupt stack. The MPS430 port, being a small micro, does not include interrupt nesting support (from memory) so there would be little to be gained from adding the extra run time overhead of managing a separate stack for interrupts.
Regards.
separate interrupt stack on IAR MSP430X port?Posted by gmenhennitt on February 5, 2014 Thanks. Even though there aren't nested interrupts, there can be some stack used just for a single interrupt. I realise that doing too much in an ISR is bad practice, but I do call a few stack levels. It would have been nice - oh, well.
Thanks,
Graham
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|