Hi Bordyn,

in general the stack was placed after the last used idata space. So all remaining idata available as stack.
In my applications I define the stack size to 16 bytes, which is sufficient for most applications. So I get a linker error, if the remaining idata was to less.

To calculate the real needed stack, you must determine the longest chain of subroutine calls. But I know no tool, which can do it automatically.

To check the real stack usage, I initialize the whole stack with a known pattern (e.g. 77h). With a RAM dump I can see, how many bytes are changed. A value of 8 or more unchaged bytes seems very good.


Peter