Hi wizards,
I've noticed a big chunk of 0's (about 1200 bytes worth) in the generated code/hex file. It occurs where the "trampoline" starts, but there does not appear to be anything really residing there. The map in this area looks like:
.progmem.data 0x0000200a 0xe9 obj/CmdMfg.o 0x000020f4 . = ALIGN (0x2) *fill* 0x000020f3 0x1 00 0x000020f4 __trampolines_start = . *(.trampolines) .trampolines 0x000020f4 0x0 linker stubs *(.trampolines*) 0x000020f4 __trampolines_end = . *(.jumptables) *(.jumptables*) *(.lowtext) *(.lowtext*) 0x000020f4 __ctors_start = . *(.ctors) 0x000020f4 __ctors_end = . 0x000020f4 __dtors_start = . *(.dtors) 0x000020f4 __dtors_end = . SORT(*)(.ctors) SORT(*)(.dtors) *(.init0) .init0 0x000025a4 0x0 c:/winavr/bin/../lib/gcc/avr/4.1.1/../../../../avr/lib/avr6/crtm2560.o 0x000025a4 __init
So what is happening between 0x000020f4 and 0x000025a4? Can I get rid of it, or does it serve a purpose?
I'm using the latest toolset and building for the ATmega2560. The makefile was generated from Mfile, then expanded a little (yeah, yeah, sorry about that).
Thanks for pointers!
Stu