ccs c not enough ram for all variables

ilker07 · Joined: 03 Jun 2022 Posts: 74

array.c

Ttelmah · Joined: 11 Mar 2010 Posts: 19967

57600 elements. 16bits each = 921600 bits of memory. your chip only has
1024000 bits of memory in total. So you would not have much space for any
other code if this was accepted!.
However a const array is not allowed to be larger than a single page in
program memory. So you might be able to get it to compile by splitting
the table.
Honestly if you need a data array this large, put it in en external EEPROM,
and keep your program memory for code.

ilker07 · Joined: 03 Jun 2022 Posts: 74

Ttelmah · Joined: 11 Mar 2010 Posts: 19967

The key problem is that you won't have enough memory in the PIC to actually
do the code, if you are using this much of it's ROM for data.
You can write raw data into the ROM using #import, and access this with
the read_program_memory function, but it will just use too much of the
ROM for the chip to be able then to control the display chip.
An external memory avoids this problem, and if you use a fast SPI interfaced
chip, a read could be done in a couple of instruction cycles.

temtronic · Posted: Wed Oct 26, 2022 5:43 am

sigh, I'm getting old..

First thing I thought of was YIKES 57,600 x 6 numbers to type in...over 1/3 of a million key presses.....with my bum finger and 'swapping of ekys' (getting worse these days.. ) there's no way the array would be 100% accurate....probably cause no end of grief IF the program actually worked !!

I agree, use an external EEPROM and when you've created the array 'file', back it up on HD and flash drive SEVERAL times !! If direct access is too slow, you could use a 'buffer', say a page at a time ?

Ttelmah · Joined: 11 Mar 2010 Posts: 19967

If he simply creates an array with a few elements, and then makes it
larger by putting a bigger number into the [], he will see how the memory
usage rises, and where the limit is.

[30000] will merrily compile and use 46% of the chips ROM. Take it above
just over 32700, and the compiler will no longer accept it, since it will not
fit into a ROM bank (65536 bytes). There is tiny bit of access code that
has to be put into the same bank as the array, which limits the maximum
to about 32750 elements.
Split it into two 28800 element arrays, and it will compile, but the chip
then has less than 12% space left. Under 4000 instructions. Not likely to
be enough to do anything with a chip as complex as a display controller.
Also this space is split between two banks, so the largest piece of code
can only be a couple of thousand instructions.

You need to rethink this. It is just not going to work.