Robert, there is no difference in handling. So create your special section and put the variables into it as you would do it with the flash.
Cheers Knut > -----Original Message----- > From: > avr-gcc-list-bounces+knut.schwichtenberg=siemens....@nongnu.or > g > [mailto:avr-gcc-list-bounces+knut.schwichtenberg=siemens....@n ongnu.org] On Behalf Of Robert von Knobloch > Sent: Monday, May 11, 2009 11:39 AM > To: avr-gcc-list@nongnu.org > Subject: [avr-gcc-list] Allocating variables to a fixed address > > Is there any way of 'fixing' a few, specific global variables > at a known > location? > In flash, I can use a '.section' to do this. Is there an > equivalent for ram? > I notice that the compiler puts static variables before globals, which > make it impossible to predict where the globals will be. > I am writing modular software and to be version independant, I must > define a simple API. > I have flash under control, but now ram is the problem. > > Best regards, > > Robert von Knobloch > > > _______________________________________________ > AVR-GCC-list mailing list > AVR-GCC-list@nongnu.org > http://lists.nongnu.org/mailman/listinfo/avr-gcc-list > _______________________________________________ AVR-GCC-list mailing list AVR-GCC-list@nongnu.org http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
