Re: Using custom linker scripts with mspgcc

Thomas Taranowski <[email protected]>
Newsgroups gmane.comp.hardware.texas-instruments.msp430.gcc.user
Message-ID <CAH0ocax4QevM7dU1OWZbLtbYTisV2zH8-BEMdZ5=6b7RT3F_Zw@mail.gmail.com>
Of course a few minutes after posting I discovered the solution.
There is an msp430.x that defines the majority of the common sections,
which also includes the memory.x and periph.x.  I put them all into
the same directory, then linked with the following options for
success:
 -T msp430.x

Thomas Taranowski | 425-442-9209 | skype: thomas.taranowski | baringforge.com



On Sat, Jun 22, 2013 at 11:39 PM, Thomas Taranowski <[email protected]> wrote:
> I'm trying to integrate some custom linker sections using mspgcc using
> the following faq:
> http://mspgcc.sourceforge.net/faq/x71.html
>
> Which tells me to do this:
> msp430-gcc -Wl,--section-start -Wl,-T linker_script.x [other options and files]
>
> However, when I do that, I get the following error:
> /usr/local/msp430/bin/../lib/gcc/msp430/4.7.0/../../../../msp430/bin/ld:
> invalid argument to option "--section-start"
>
> if I leave that off, I get:
> /usr/local/msp430/bin/../lib/gcc/msp430/4.7.0/../../../../msp430/bin/ld:
> internal error emsp430.c 123
>
> Which leads me to believe that either the --section-start is special
> for the msp430-gcc, or the linker isn't accepting the multiple -T
> options, and accumulating as expected.
>
> Any ideas on what I could be doing wrong?  Examples of what other
> folks are doing might be helpful.
>
> mspgcc version:
> msp430-gcc (GCC) 4.7.0 20120322 (mspgcc dev 20120911)
>
>
> The linker command line I'm using:
> /usr/local/msp430/bin/msp430-gcc   -mmcu=msp430fr5969
> -ffunction-sections -fdata-sections -DGCC_MSP430 -Wextra
> -fno-exceptions -fno-rtti -fno-enforce-eh-specs -lfp -lm -g
> -mmcu=msp430fr5969 -Wl,--section-start -Wl,-T
> /home/tom/fsw/build_tools/ldscripts/t3g/memory.x -Wl,-T
> /home/tom/fsw/build_tools/ldscripts/t3g/periph.x
> CMakeFiles/i2c_write_test_main.dir/local/i2c_write_test_main.cpp.obj
> -o ../../../product/msp430fr5969-msp430-gnu/Debug/bin/i2c_write_test_main
>  -L/home/tom/fsw/product/msp430fr5969-msp430-gnu/Debug/lib
> -L/home/tom/fsw/product/msp430fr5969-msp430-gnu/Debug/usr/lib
> ../../../product/msp430fr5969-msp430-gnu/Debug/lib/libt3_manager.a
> -Wl,--start-group
> ../../../product/msp430fr5969-msp430-gnu/Debug/lib/libcore.a
> ../../../product/msp430fr5969-msp430-gnu/Debug/lib/libbsp_msp430.a
> ../../../product/msp430fr5969-msp430-gnu/Debug/lib/libevent_log.a
> ../../../product/msp430fr5969-msp430-gnu/Debug/lib/libi2c_driver.a
> -Wl,--end-group
>
>
>
>
>
> Thomas Taranowski | 425-442-9209 | skype: thomas.taranowski | baringforge.com

------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.