You're right Sergey! I've finally got the point. Unfortunately it's the
first time I'm playing with these linker
scripts, so it took some time to figure it out. However, since I checked
that the redefined memory regions
are actually the same both in my script and in the system script, I
assume that I can leave the situation as it is,
I mean, passing both scripts to the linker, right? In this way I could
avoid editing my script...
Something I learned and that could be useful for other users too:
- Using gcc-4.1 is fine to compile the mspgcc toolchain (somewhere it's
advised to use only <3.4)
- The best way to compile everything is by using:
http://mspgcc.cvs.sourceforge.net/mspgcc/packaging/README-MAINTAINER.txt?view=markup
- However, also the script provided here works fine:
http://www.nabble.com/buildscript-for-the-mspgcc-toolchain-under-linux-td18111541.html
Thanks!
/opt/mspgcc/bin/msp430-ld:/opt/mspgcc/msp430/lib/ldscripts/msp430x1612.xn:6:
warning: redeclaration of memory region 'text'
/opt/mspgcc/bin/msp430-ld:/opt/mspgcc/msp430/lib/ldscripts/msp430x1612.xn:7:
warning: redeclaration of memory region 'data'
Excuse me, I paid no attention to your command line in your first post. As I see
you tell the compiler to use your own script:
msp430-gcc -Wl,-T"../../System/lddefault.x"
I think you must remove -T option to allow gcc use default script for your
F1612, or edit your lddefault.x using msp430x1612.xn as an example (add missing
symbols and initX/finiX sections).
Sergey.
