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] [March 2012 Threads] IAR FreeRTOS stack checkingPosted by Shawn Gardner on March 8, 2012 Hello,
I am using IAR EWARM 6.30.6 with the FreeRTOS and OpenRTOS plugin (v2.0.0.0) and developing on a TI Stellaris EK-LM3S9D92 board. How do I get the stack checking to turn on. Right now the "On" and "Off" menu items are dimmed out. Also, in the Tasks window's "Min Free Stack", every task is "Off". In my code I have:
#define configCHECK_FOR_STACK_OVERFLOW2
I also noticed that the "Top of Stack" is not really the top of the stack for my setup because when single stepping, I see the SP go higher when popping the stack than what is listed in the column "Top of Stack".
Thanks in advance!
RE: IAR FreeRTOS stack checkingPosted by Richard on March 10, 2012 “How do I get the stack checking to turn on. Right now the "On" and "Off" menu items are dimmed out.” Try right clicking on the column in the table itself. There is a forum for state viewer support on the highintegritysystems.com web site. “I also noticed that the "Top of Stack" is not really the top of the stack for my setup because when single stepping, I see the SP go higher when popping the stack than what is listed in the column "Top of Stack". ” On the ARM the stack grows down from high memory. I would therefore expect to see the start of stack being a lower value than the current top of stack, and the stack pointer to grow away from the start of stack (as functions are entered) value by becoming a larger number, and shrink toward the start of stack value (as functions are exited) by becoming a smaller number. I think that is the behaviour your are reporting, and therefore the expected behaviour. Regards.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|