dav9482 
I have an ATmega328P, which has 2Kb RAM memory.
My current program seems to be at the very limit of the RAM memory; I see that by just declaring one buffer a bit longer, then the program has a strange behavior. (this buffer is actually not used).
What is the best way to debug (keep track of) the RAM memory usage?
Many thanks,
David
Search the forum for "stack" and "painting". I believe there was such a thread. If that does not help, then search without "painting". There have been many threads related to that.
If you do not have recursions, function pointers, do not use avr-libc much, do not do anything fancy in interrupts, etc, then you can try my ezstack utility. Just "ezstack file.elf". If it likes your elf and does not give you any errors, then it should give you the total RAM usage, including stack. You can get the utility from http://home.comcast.net/~ezstack/
Eugene
Levenkay Look at the generated linker map.
Or just look at your source code. Two kilobytes isn't a lot of memory to keep track of; you probably didn't declare a thousand separate static variables, did you? Most applications would have declared a much smaller number of variables, with the remaining space being devoted to a few moderate-to-large arrays. After you've counted up all the variables you explicitly created, how does the total size compare against the known limit of 2K?
If the two figures are miles apart, the likeliest culprit is string variables, as in:
const char *syntaxComplaint = "Could not parse input line\n";
. If that's your trouble, look into having such strings kept exclusively in FLASH.
indianajones11 After compiling, what % of ram usage is given ?
clawson 
