Grant Edwards schrieb:
Perhaps my usage is unusual, but it seems very counter-intuitive that uninitialized objects placed in the .infomem section are initialized to 0. I expected the the .infomem section to have the "@nobits" attribute, but it is "@progbits".
there is the segment named "infomemnobits", which i think works like you want.
I'm using the infomem segments to contain application configuration data that must survive reset, power-down, andfirmware-upgrades. IOW, the elf/hex files should not reset unintialized infomem objects to 0.
then you probably don't want to have any byte from the information memory in your hex file. as the programming tools usually erase all the segments before writing (and not doing a "read, modify, erase, write") and the MSP430 hardware supports a main erase leaving the entire information memory intact ("msp430-jtag -m" for example uses this)
chris
