Classic/Legacy CodeWarriorのトピックDeclare constant in ROM

Declare constant in ROM

brunolalb — Sat, 26 Nov 2011 02:33:19 GMT

Hi,
I'm working in a project with a MC56F8006 and an OLED Display, so I have to allocate about 1 KB of "screens" for my display. I'm trying to allocate this 1 KB in internal flash memory, because they won't be changed ever (they are constants). I'm currently declaring it as "static const UWord8 screenN[] = { lots of bytes};", but it seems to be occupying the RAM segment, since I ran out of RAM, even though I have only about 500 bytes of variables.

I found some people saying to declare the screens as "__pmem static UWord8 screenN[] = { lots of bytes };" and use level 4 optimizations. It made my code compile, but got several warnings regarding the linker command file, for example: "F_Pbss_start_addr defined in the Linker Command File is not word-aligned, address in bytes is 7609."

I don't know what else to do. I searched everything and still haven't got a straight answer. How do I declare a array of bytes in flash memory so it doesn't occupy my RAM memory?

Regards,
Bruno

Re: Declare constant in ROM

giacomopetrini — Thu, 15 Dec 2011 21:05:42 GMT

Hi,

In a project I just declared this:

__pmem const UInt8 CRC8_table[256] = {//lot of bytes};

and work correctly. (the const is not mandatory I think).

Try to compile with "Level 2 optimization" or less. I've found out that sometimes compiling with Level 3 or above gives some strange result when using variables in program memory.

By the way you should check the "Targeting 56800E" pdf, it gives some insight on how to use the __pmem command and what are the limitation on putting data in program memory.

You can also try the "Pool Strings" and "Reuse Strings" checkbox in Language Settings (In theTarget Settings Panel), they can maybe shrink the memory footprint of the strings...

Hope this helps

Bye Giacomo

Re: Declare constant in ROM

willihoffmann — Fri, 07 Nov 2014 13:12:00 GMT

It's quite an old post, so I think the problem should have been solved now, but for anyone else having this error and not knowing where the problem is: if you are using byte-arrays, make sure to have an even amount of bytes, so you don't break word alignment.