Memory use - how much do you use?

[keymuu]

Hi!

Using:
PBP 2.50b
Microcode Studio 3.0.0.5
Microchip USB HID bootloader v2.2
PIC18F4550

When you compile via Microcode Studio you can see how much space your code will take. I think it would be very informative if you could also see how much there still is space to increase your code before you code memory is full. So, instead of seeing "Success: 22384 bytes used" you would see "Success: 22384/32768 bytes used" or something like that...

But you use data memory also! It would be technically easy to add the use of it also on the same line where the use of the used code is shown, however, this is not how things are today.

Where can one see how much you use data space?
In 4550 there is 2k.
Where is that data of used memory hidden? In a linker file or where? Tried to search around but could not find it. I know I'm kind of a blind guy

Thank you in advance...

[Melanie]

If you compile using something like Microchips Assembler (which you would do for things like the 18F series), then looking at the end of the generated .LST file you will find a couple of lines like...

Program Memory Bytes Used: 15998
Program Memory Bytes Free: 386

[keymuu]

If you compile using something like Microchips Assembler (which you would do for things like the 18F series), then looking at the end of the generated .LST file you will find a couple of lines like...

Program Memory Bytes Used: 15998
Program Memory Bytes Free: 386

Thank you Melanie

But where can I see how much my variables need/consume space? Perhaps the same way as program memory bytes used are showed...

[Charles Linquis]

I don't know if it is valid, but it seems to work for me -

To figure how much free RAM I have, I create a dummy aray variable and compile.

dummy var byte (1000)

If there is no compile error, I figure I have at least 1000 bytes of free memory. I delete the line and go on.


I use MCLoader often in my programs. It occupies some space in high memory. I used to find that I would compile a program and get no errors, only to find that when I actually loaded the code in the part (that already had MCLoader in it), I got an over-run error. I solved that problem by including the following lines at the very end of my program -

ASM
     ORG 0x1fcee        ; a few bytes below MCLoader when used in a 128K part
     nop
ENDASM

You can put any address you want after the ORG statement. If your program gets bigger than that, you will get a compile error. I have found this technique to be useful in lots of ways.

[mackrackit]

This might help.
It is a little program I have been playing with that reads the LST file and pulls some info from it.

It is a work in progress so it may not be 100% accurate and it seems to work better on 18Fs.
Some of those LST file can be quite large.

Click on the link below and save. The is nothing to install. Just click and run.
http://www.mac.mf3x3.com/downloads/lst/LST_V.exe

<img src="http://www.picbasic.co.uk/forum/attachment.php?attachmentid=3098&stc=1&d=123165757 1">

[keymuu]

This might help.
It is a little program I have been playing with that reads the LST file and pulls some info from it.

It is a work in progress so it may not be 100% accurate and it seems to work better on 18Fs.
Some of those LST file can be quite large.

Click on the link below and save. There is nothing to install. Just click and run.
http://www.mac.mf3x3.com/downloads/lst/LST_V.exe

Thank you Charles and Dave!

The List View seems to work just perfectly ...
I just don't understand why not PBP do show more info especially when it would be quite easy to incorporate all that info into the compilation output... Perhaps the time is not ready yet?

Thank you all for the help on this matter