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/TMS570LS0232: there is a error when CCS compile C codes

Part Number: TMS570LS0232
Other Parts Discussed in Thread: HALCOGEN

Tool/software: Code Composer Studio

Hello, TI Engineers

When we compile our project, compiler report the error "#10099-D program will not fit into available memory. Placement with alignment fails for section ".cinit" size 0x461. Available memory ranges: sys_link.cmd /TMS570LS0232/source line 79C/C++ Problem".

I hope TI engineers could help me for solving the problem.

Thanks!

Regards!

Xinyu

  • Hello Xinyu,

    Where do you place.cinit section in sys_link.cmd? The flash size on LS0232 is 128KB. How big is your project?

  • Hello, Wang

    In fact, we do not know what is the use of .cinit file? It should be produced by HALCoGen. If we just comment on some codes, the program could be downloaded into TMS570. The HEX file could be 79 KB. So we do not  know why.

    Thanks!

    Regards!

    Xinyu 

  • Hello Wang,

    In fact, I think this file was produced when we used CCS to design our project.

    And codes of safety function should be included in the memory. How size is it?

    Thanks!

    Regards!

    Xinyu

     

  • Hello Xinyu,

    The following sections in linker.cmd are used for:
    .text -- Used for program code.
    .bss -- Used for uninitialized objects (global variables).
    .data -- Used for initialized non-const objects (global variables).
    .const -- Used for initialized const objects (string constants, variables declared const).
    .cinit -- Used to initialize C global variables at startup.
    .stack -- Used for the function call stack.

    The .cinit section, which contains the autoinitialization table for C/C++ programs, should not be removed from your linker.cmd file.