I use MicroCode Studio Plus... I think it tells you the memory used in the Status Bar.
Where? I don't see it.
I use MicroCode Studio Plus... I think it tells you the memory used in the Status Bar.
Where? I don't see it.
Bottom left hand corner after you compile.
Success:blablabla bytes used.
Dave
Always wear safety glasses while programming.
Oh, there it is! That's telling you how much flash/program memory you're using, right? Is there a way to see or monitor your RAM useage?
That's right, its program data not RAM. Unfortunately I do not know of a clean way to read how much ram you are using. But someone taught me a trick of:
And if it is too big to fit, make it smaller. The size allowed in the program will be the amount of RAM you have left.Code:test var byte[96]
http://www.scalerobotics.com
http://www.picbasic.co.uk/forum/showthread.php?t=10381
Talks about RAM.
I never did fix the little program in the thread though![]()
Dave
Always wear safety glasses while programming.
Hi Hank,
Each character within double quotes of the debug statement eats three bytes of program memory. Counting the number of characters in that single line you posted makes for 70 characters or 210 bytes worth of program space.
The Debug statement itself seems to eat 52 bytes but it's a "one time deal" ie, it doesn't cost you 52 bytes each time you use DEBUG. (It might cost you a byte or two depending on where in the program they are placed.)
There may be ways around this (search for Strings in codespace) but if you just need "a couple" of more bytes then try to reduce the number of characters in your DEBUG statements.
If you do look at the Strings in codespace threads I'd be interested in what you come up with. I'm pretty much having the same issue but using ArrayWrite. The problem with Strings in codespace are they are strings (constants) and I haven't yet figured out how to mix them with numeric values "printed" with the DEC modifier etc.
/Henrik.
Bookmarks