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.

Not fit into available memory in F28055. Why?



Dear all,

Type #10099-D program will not fit into available memory. placement with alignment/blocking fails for section ".text" size 0x2021 page 0.

Available memory ranges: F2805x_FLASH_SimpleVSD_PRD.cmd /SimpleVSD_PRD line 140 C/C++ Problem

I  met this error in CCSv6, although I have increase the size of flash for .text section as following:

SECTIONS
{

/* Allocate program areas: */
.cinit : > FLASHA, PAGE = 0
.pinit : > FLASHA, PAGE = 0
/*.text : > FLASHC, PAGE = 0 */ (Before error occured)
.text : > FLASHC | FLASHE | FLASHF | FLASHG | FLASHH, PAGE = 0 /* Increasing the size of *text */
codestart : > BEGIN PAGE = 0
ramfuncs : LOAD = FLASHD,
RUN = RAML0 | RAML1,
LOAD_START(_RamfuncsLoadStart),
LOAD_END(_RamfuncsLoadEnd),
RUN_START(_RamfuncsRunStart),
PAGE = 0


dcsm_otp_z1 : > DCSM_OTP_Z1_P0 PAGE = 0
dcsm_otp_z2 : > DCSM_OTP_Z2_P0 PAGE = 0

dcsm_zsel_z1 : > DCSM_ZSEL_Z1_P0 PAGE = 0
dcsm_rsvd_z1 : > Z1_DCSM_RSVD PAGE = 0
dcsm_zsel_z2 : > DCSM_ZSEL_Z2_P0 PAGE = 0
dcsm_rsvd_z2 : > Z2_DCSM_RSVD PAGE = 0

/* Allocate uninitalized data sections: */
.stack : > RAMM0 PAGE = 1
.ebss : > RAML2 PAGE = 1
.esysmem : > RAML2 PAGE = 1

/* Initalized sections go in Flash */
/* For SDFlash to program these, they must be allocated to page 0 */
.econst : > FLASHA PAGE = 0
.switch : > FLASHA PAGE = 0

/* Allocate IQ math areas: */
IQmath : > FLASHA PAGE = 0 /* Math Code */
IQmathTables : > IQTABLES, PAGE = 0, TYPE = NOLOAD

/* Uncomment the section below if calling the IQNexp() or IQexp()
functions from the IQMath.lib library in order to utilize the
relevant IQ Math table in Boot ROM (This saves space and Boot ROM
is 1 wait-state). If this section is not uncommented, IQmathTables2
will be loaded into other memory (SARAM, Flash, etc.) and will take
up space, but 0 wait-state is possible.
*/
/*
IQmathTables2 : > IQTABLES2, PAGE = 0, TYPE = NOLOAD
{

IQmath.lib<IQNexpTable.obj> (IQmathTablesRam)

}
*/
/* Uncomment the section below if calling the IQNasin() or IQasin()
functions from the IQMath.lib library in order to utilize the
relevant IQ Math table in Boot ROM (This saves space and Boot ROM
is 1 wait-state). If this section is not uncommented, IQmathTables2
will be loaded into other memory (SARAM, Flash, etc.) and will take
up space, but 0 wait-state is possible.
*/
/*
IQmathTables3 : > IQTABLES3, PAGE = 0, TYPE = NOLOAD
{

IQmath.lib<IQNasinTable.obj> (IQmathTablesRam)

}
*/

/* .reset is a standard section used by the compiler. It contains the */
/* the address of the start of _c_int00 for C Code. /*
/* When using the boot ROM this section and the CPU vector */
/* table is not needed. Thus the default type is set here to */
/* DSECT */
.reset : > RESET, PAGE = 0, TYPE = DSECT
vectors : > VECTORS PAGE = 0, TYPE = DSECT

}

 

Please help me!

PS: I am using CCSv6, C/C++ compliler TI v6.4.2

Many thanks in advance.

  • Dear all,

    I have just work around the problem. It's done by changing the size of stack in Linker/Basic Options: from 0x300 to 0x380. After that I added "rts2800.lib" in the File Research Path section.

    And now the linker did not generated the above error.
  • I'm glad you found a solution.  Still, I want to point out that this ...

    Binh Duong Tran said:
    .text : > FLASHC | FLASHE | FLASHF | FLASHG | FLASHH, PAGE = 0 /* Increasing the size of *text */

    ... does not increase the amount of target memory available to text.  Instead, it allocates .text into the first of those memory ranges which can completely contain it.  In your case, it seems that is none of them.  You probably meant to write ...

    .text : >> FLASHC | FLASHE | FLASHF | FLASHG | FLASHH, PAGE = 0
    /*      ^^ Notice the difference */
    

    The >> syntax says to split .text across those memory ranges.  And that increases the amount of memory for .text.  For more detail please see this section of the Linker Command File Primer wiki article.

    Thanks and regards,

    -George

  • Dear George,

    Thank you for your guides. I an not an experient user's CCSv6, so your guides are very useful for me.

    Best regards,

    -Tran