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.

error #10099-D: program will not fit into available memory

Other Parts Discussed in Thread: MSP430G2553, ENERGIA

Hello 

I am new to the TI launchpad and I am unable to get the hello World example to compile and run, Blink works fine tho. From what I can tell I should have enough memory on the MSP430G2553 Chip that came with the Launchpad but its not working. I have set the -printf_support=minimal and tried noFloat, but its still not working.

Below you can find the code and the error, Any Help Would Be Great!

Thanks Chris

This is the code

#include <stdio.h>
void main(void) {
	printf("Hello World!\n");
}

And this is the error I get

'Building target: hello world.out'
'Invoking: MSP430 Linker'
"C:/ti/ccsv5/tools/compiler/msp430/bin/cl430" -vmsp --abi=eabi -g --define=__MSP430G2553__ --diag_warning=225 --display_error_number --printf_support=minimal -z -m"hello world.map" --stack_size=80 --heap_size=80 -i"C:/ti/ccsv5/ccs_base/msp430/include" -i"C:/ti/ccsv5/tools/compiler/msp430/lib" -i"C:/ti/ccsv5/tools/compiler/msp430/include" --reread_libs --warn_sections --rom_model -o "hello world.out" "./hello.obj" -l"libc.a" "../lnk_msp430g2553.cmd"
<Linking>
warning #10247-D: creating output section ".data" without a SECTIONS
specification
"../lnk_msp430g2553.cmd", line 63: error #10099-D: program will not fit into
available memory. run placement with alignment fails for section ".cio"
size 0x120 . Available memory ranges:
RAM size: 0x200 unused: 0x2e max hole: 0x2c
error #10010: errors encountered during linking; "hello world.out" not built

 
  • Hi Chris,

    I think this is an issue with the example.  I have see the exact same thing.  Let me look into this and see if there is a work around.

    Best Regards,

    Lisa

  • Hi Chris,

    it appears that even though you can select this as an example, the "Hello World" example is not supported on some launchpad devices as they simply really do not have the space for printf support.

    Sorry to have to disappoint.

    Best Regards,
    Lisa

  • Hi, Lisa

    I just start with the launchpad and I have the same. There is plenty of space for it, there must be something else. The Mc is the MSP340G2553 with 16kb and 512 bytes. So in the G serie the best. 

    Best Regarts,

    Jan

  • Dear all,

    After some modifications with "--printf_support=minimal" in de linker command the flash memory was reduced but this was not the problem, but the .cio takes 0x120 bytes from the RAM. In fact there is no reason to do that. We need 1kB of RAM!! The reason is that the Stdio routines are used as one package with a big bufferspace in RAM. I am worry about two things, the linker don’t extract the printf function from the library, so the whole package is used. If you have limited flash memory then it is waste of memory, and together with the package it reserve to much RAM memory. So we need an other library package, or some modifications, or options in the linker to set. I try to find a modification to reduce the amount of RAM and who to manipulate the linker. It will be great if somebody know a .obj library with a printf function with much less RAM. 

    Best regards

    Jan

  • I totally agree. How can you have a platform like this and not support printf() even a very simple one.
    This is essential for simple logging/tracing it is critical, specially for things that can't be done via the debugger.
    Please, any suggestions would be appreciated. Even things like, ripping out functions out of the C library that aren't used.
    I was able to get console output with Energia for not with CCS v6.1.