Sign in

username:

password:



Not a member?

Search msp430



Search tips

Subscribe to msp430



Ads

Discussion Groups

Discussion Groups | MSP430 | Re: Linking

The purpose of this group is to foster exchange of information on the Texas Instruments MSP430 family of microcontrollers and related tools. Everyone welcome, all levels of familiarity/expertise.

Re: Linking - old_cow_yellow - Jul 6 21:12:28 2008

You could have told the pre-processor things like:
#define Bitmap1 0xfe, 0xfe
#define Bitmap2 0xff, 0xff, 0x56

Then it will expand things like:
PDigits20x32: DC8 Bitmap1, Bitmap2, Bitmap1

--- In m...@yahoogroups.com, "vincbr900" wrote:
>
> Hi,
> I have a project where I use a small graphic display.
> I have a range of bitmaps and a hash table to avoid repetition.
> I tried this in C but the compiler resolves the hash table at run
> time and I run out of RAM (as PDigits20x32 is placed in RAM), so I
> tried assembly hoping the linker would resolve at compile time,
> placing PDigits20x32 in ROM.
> MODULE PDigits20x32
> PUBLIC PDigits20x32
> Bitmap1:
> DC8 0xfe, 0xfe, ...
> ...
> Bitmap19:
> DC8 0xff, 0xff, ...
>
> //extern const unsigned char *PDigits20x32[digit0..9][4];
> PDigits20x32:
> DC16 Bitmap1, Bitmap2, Bitmap2, Bitmap3 // 0
> DC16 Bitmap4, Bitmap4, Bitmap4, Bitmap4 // 1
> ...
> DC16 Bitmap18, Bitmap19, Bitmap9, Bitmap10 // 9
> endmod
> end
>
> However, the linker complains bitterly. How can I resolve my hash
> table without using precious RAM?
>
> Thanks, Vincent
>

------------------------------------



(You need to be a member of msp430 -- send a blank email to msp430-subscribe@yahoogroups.com )