While writing a simple boot loader, I ran into the following issue, originally posted to the tinyos-devel list:
https://www.millennium.berkeley.edu/pipermail/tinyos-devel/2012-February /005074.html > When building an image to be installed along with TOSBoot, the linker > flag --defsym=_reset_vector__=0x4000 is set in > support/make/tosboot.extra. Unfortunately, this causes the linker to > conclude that the startup code from crt0 (initializing the stackpointer, > .data, and .bss sections) is unreachable and thus optimised out. I did > not find any obvious way to avoid this and ended up removing the > --defsym from tosboot.extra and afterwards hand-editing the vector table > in the resulting .ihex images of the applications. I wanted to use the same trick to move the application and still reset into the bootloader. Is there a recommended way to make msp430-ld keep the startup routines (__watchdog_support, __init_stack, __do_copy_data, __do_clear_bss)? In the msp430.x linker script, the init sections are already marked KEEP, but apparently that's not enough. Best, Michiel ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
