MSP430 linker: how to force _c_int00 to be loaded at 0x1600?

Charles,

I can recreate the behavior you reported concerning linker warning: "no matching section"

Here is my analysis on what is happening:

As you probably know, the compiler tools now do an automatic RTS library selection so the user does not have to worry about picking the correct RTS. When you create a new project in CCS, it defaults to automatic runtime library selection.

If you take a look at the link command line in CCS console window when your project is being , it should be something like:

"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/msp430/bin/cl430" -vmsp -g --diag_warning=225 --printf_support=minimal -z -m"F149_test.map" --stack_size=80 --heap_size=80 --use_hw_mpy=16 --warn_sections -i"C:/Program Files/Texas Instruments/ccsv4/msp430/include" -i"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/msp430/lib" -i"C:/Program Files/Texas Instruments/ccsv4/tools/compiler/msp430/include" --reread_libs --rom_model -o "F149_test.out"  "./fet140_1.obj" -l"libc.a" "../lnk_msp430f149.cmd"

The --l”libc.a” is passed before the linker command file but is not getting resolved correctly for the linker, thereby resulting in the warning "no matching section" when it encounters it in the linker command file. I will submit this to our defect tracking system to get fixed for a future release.

There are a couple of ways to work around this:

1) Add rts430.lib to the --library option (C/C++ Build->Linker->File Search Path) and make sure it’s the first library in the list (so rts430.lib appears before libc.a in the command line)

2) Add libc.a and lnk_msp430f149.cmd to the link order list (CCS Build->Link Order tab) and make sure the linker command file is first on the list

 Please let us know if this helps resolve the warning.