Yes, but .infomem is a predefined section where I can't choose a different address.
Currently I'm using a "self-defined" section and initialize the consts with 0xff. This works nearly in the same way as not programming the flash on the used addresses - although it looks like a little bit ugly. Stripping the hex-file is also an interesting idea. Thanks for your help, matthias _____ Von: [email protected] [mailto:[email protected]] Im Auftrag von [email protected] Gesendet: Donnerstag, 15. Mai 2008 10:42 An: [email protected] Betreff: Re: [Mspgcc-users] define an uninitialized flash secetion @mfend: You could use __attribute__((section(".infomem"))) const some_strct SomeInfo = or __attribute__((section(".infomemnobits"))) const some_strct SomeInfo = { 0, 1, "FooBar", 2, 3, 4 }; A search 4 "infomemnobits" should lead you to some docs about gnu linker ld http://sourceware.org/binutils/docs-2.18/ld/MSP430.html#MSP430 where these names are explained and what they do. On the other side you could also use msp430-objcopy -O ihex -R .infomem $(NAME).elf $(NAME).hex in the makefile to strip a section from your final hexfile. Regards, Helmut [email protected] wrote on 14.05.2008 16:36:26: > > Today's Topics: > > 1. define an uninitialized flash secetion (mfend) > 2. Re: define an uninitialized flash secetion (Roman Lim) > 3. Re: define an uninitialized flash secetion (mfend) > ----------------------------------------------------------------------
