This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CCS/MSP430F5438A: EABI and Legacy Coff

Part Number: MSP430F5438A

Tool/software: Code Composer Studio

Hi,
I am trying to build a program using MSP430F5438A. When I build it using the eabi option, the memory used is Flash1+Flash 2=44.63k & when I build it using Legacy Coff option , the memory used is Flash1 + Flash 2=40k.  So basically, the entire memory of 256k is not used using either option. However, when I build the program using eabi option, I get the following error and am unable to debug the program.

Description Resource Path Location Type
#10010 errors encountered during linking; "22tr 5438 chk.out" not built 22tr 5438 chk C/C++ Problem
#10099-D program will not fit into available memory. placement with alignment fails for section ".cinit" size 0x2b . Available memory ranges: lnk_msp430f5438a.cmd /22tr 5438 chk line 148 C/C++ Problem

Please help me out to know why this happens as I can't predict the exact memory requirements of the program if I get the above error.

Thanks.

  • The linker command file used for MSP430F5438A is lnk_msp430f5438a.cmd, found in a location similar to ...

    C:\ti\ccsv7\ccs_base\msp430\include

    From that file, I can see that the .cinit section is allocated to the FLASH memory range.  The FLASH memory range is 0xA380 bytes, which is just under 41K.  So that is why everything fits when building with COFF ABI, and is a bit too big when building with EABI.  

    To better understand linker command files, please see the article Linker Command File Primer

    To better understand this diagnostic ...

    Tanmay Gadekar said:
    #10099-D program will not fit into available memory. placement with alignment fails for section ".cinit"

    Please make sure you see the entire diagnostic, and not just this truncated part of it.  Do that by looking at the all the build output in the Console view.  Then read more about it in the article Compiler/diagnostic messages/10099.

    Thanks and regards,

    -George