Re: [avr-gcc-list] .data section

[Markus Assfalg]

> They are in the .data section, not in the .text section.  Both
> sections are normally concatenated in the flash image, and the startup
> code then copies over the initialization data to RAM.

This concatenation works with the hexfile but the coff doesn't include
the content of the .data section (should be mapped to .text).

> The .data section ought to be in the COFF file as well, but it's
> probably ignored there, and even worse, once the gcrt1.S code has
> been run, as you observe, unitialized ROM pattern will be copied
> over.

Is it possible to modify the linkerscript to map the .data section into
 .text?

> I don't see an easy solution to this problem.  Now i realize why it's
> a good idea that VMLAB uses the HEX file as input, and ignores
> anything but the debugging information from the COFF file. ;-)

What is VMLAB ?

Thanks

Markus