Reply by Hugh Molesworth●October 10, 20022002-10-10
Try "for (i=0; i < 14; i++)" instead.
Hope that helps.
>Does anyone know of a way to check how deep one is in it's stack?
I'm using
iar ew430 full version.
The problem is that I've got a function that's been called and id
doesn't
run like it should. For debug purposes I just inserted a little loop
for (i=0; i > 14; i++)
printf("value of i= %d \r\n",i);
but for some reason this function doesn't run at all. Could this have
something to do with the stack size??
Thanks Martijn
> Does anyone know of a way to check how deep one is in it's stack?
Yes, modify cstartup.s43 to completely fill all of RAM with some
recognizable pattern. This needs to be done before any C run time
system is set up. Then, using C-spy, when you debug into the code
that starts to behave funny, take a look at the RAM in the memory
window and find out if your stack has eaten away at your data area.
JJS
Reply by Martijn Broens●October 10, 20022002-10-10
Hi All,
Does anyone know of a way to check how deep one is in it's stack? I'm
using
iar ew430 full version.
The problem is that I've got a function that's been called and id
doesn't
run like it should. For debug purposes I just inserted a little loop
for (i=0; i > 14; i++)
printf("value of i= %d \r\n",i);
but for some reason this function doesn't run at all. Could this have
something to do with the stack size??
Thanks Martijn