stupid Array error: Error [1300] stack frame too l

[Validius]

It is choking on this declaration: `int table[255];`

I'm making it a lookup table.

[devicenull]

rom const int table[256];

Use that instead. Also, do you actually need int's? Do you values go above 255? Using unsigned char's would be more memory efficient

[Validius]

Originally Posted by devicenull

rom const int table[256];

Use that instead. Also, do you actually need int's? Do you values go above 255? Using unsigned char's would be more memory efficient

Yea, i was thinking about it and an unsigned char would work better. *runs to make a typedef*

[Validius]

Originally Posted by devicenull

rom const int table[256];

Use that instead. Also, do you actually need int's? Do you values go above 255? Using unsigned char's would be more memory efficient

what does the 'rom' part of it mean?

[Eldarion]

Originally Posted by Validius

what does the 'rom' part of it mean?

I believe it places the array into the FLASH memory, not RAM.

[Mark McLeod]

The linker will only allow you to define a total of 256 bytes of global (or static) variables within any single project file. Variables are located in Data space where the values can be changed whenever you like.

If you want to create "char table[255]", it'll need to be defined in a file off by itself that doesn't have any other global or static declarations and referenced as an extern. "int table[255]" is too large to be defined anywhere but within the much larger Program space.

Using the keyword "rom" forces the array to be defined in (Read Only Memory) Program space rather than the Data memory, then you can be as large as you have program space for, but the values are fixed like your code statements and cannot be assigned or changed while your program is running. You have to pre-define the array values, e.g.,

rom const int table[255]={1,2,3,4,...255};

See pdf page 22 (document page 14) of the MPLAB C18 C Compiler User's Guide for a description of rom vs ram.
Also discussed in this thread.

[dcbrown]

See the appropriate sections in C18 Users Guide (see pointer in reply #45):

2.3 Storage Classes
2.4 Storage Qualifiers

2.4.3 ram/rom Qualifiers

Because the PICmicro microcontrollers use separate program memory and data
memory address busses in their design, MPLAB C18 requires extensions to distinguish between data located in program memory and data located in data memory. The ANSI/ISO C standard allows for code and data to be in separate address spaces, but this is not sufficient to locate data in the code space as well. To this purpose, MPLAB C18 introduces the rom and ram qualifiers. The rom qualifier denotes that the object is located in program memory, whereas the ram qualifier denotes that the object is located in data memory.
Pointers can point to either data memory (ram pointers) or program memory (rom pointers). Pointers are assumed to be ram pointers unless declared as rom. The size of a pointer is dependent on the type of the pointer and is documented in Table 2-4. ...

Reading both sections of the user guide should provide a better understanding of storage declaration options available.

I'm assuming this is in MPLab. The same thing can be done in EasyC either using the "User Code" option. See EasyC discussion in EasyC Wish List thread.

Regards,
DCBrown

[Mark McLeod]

Originally Posted by dcbrown

See the appropriate sections in C18 Users Guide (see pointer in reply #17):

Post #45 is the up-to-date 2006 version.