You'll want to specify the processor when compiling and linking.

msp430-gcc -mmcu=xxx main.o -o main.elf

replace xxx with the processor that you are using like msp430f149
--------------------------------------------------------------------------------------------
Thanks Adam,
    I guess that I am still missing something basic.

             $  msp430-as -Wall -mP  -mmcu=msp430g2211  main.s -o main.o >
main.lst
    /ASM $ msp430-gcc -mmcu=msp430g2211 main.o -o main.elf
/usr/lib/gcc/msp430/4.5.3/../../../../msp430/bin/ld: main.elf section
`.text' will not fit in region `rom'
/usr/lib/gcc/msp430/4.5.3/../../../../msp430/bin/ld: section .vectors loaded
at [000000000000ffe0,000000000000ffff] overlaps section .text loaded at
[000000000000f800,000000000001f839]
/usr/lib/gcc/msp430/4.5.3/../../../../msp430/bin/ld: region `rom' overflowed
by 63578 bytes
collect2: ld returned 1 exit status

I also have     .arch            msp430g2211    ;In the source.

    There was something I did not fully understand from TI about msp430x
having address space over 64k, however this g2211 has space over that even
though it's not populated.  I'd wonder that with todays technology why the
430x has paging rather than a new architecture with 20 bit addressing.  I
was quite good at assembly with the older 64k machines Z80, 6502 etc. 
Thanks Ian. 
-- 
View this message in context: 
http://old.nabble.com/Linking-problem-tp34515353p34516626.html
Sent from the MSP430 gcc - Users mailing list archive at Nabble.com.


------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users

Reply via email to