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: program will not fit into available memory. placement with alignment/blocking fails for section



I work with the HVPM_Sensorless_2833x exapmle project, I added some functions to new .c file named "Functions.c" and there is building error about the ram size:

---

"../F28335_RAM_HVPM_Sensorless.CMD", line 124: error: program will not fit into
available memory. placement with alignment/blocking fails for section

>> Compilation failure
".text" size 0x1c26 page 0. Available memory ranges:
RAML1 size: 0x1800 unused: 0x1800 max hole: 0x1800
error: errors encountered during linking; "HVPM_Sensorless_2833x.out" not
built
gmake: *** [HVPM_Sensorless_2833x.out] Error 1
gmake: Target `all' not remade because of errors.

**** Build Finished ****

--

It shows that the problem is in the "F28335_RAM_HVPM_Sensorless.CMD" file and the line is "   .text            : > RAML1,     PAGE = 0"

My code is not too large and I have not got big arrays, I think problem is about the page size, code must use other RAM pages, builder must use other pages but it does not? (when I delete some functions, it builds) (I use RAM boot, the project does not have FLASH boot)

I attached the .cmd file. 

/*

//###########################################################################
//
// FILE:    F28335_RAM_HVPM_Sensorless.cmd.cmd
//
// TITLE:   Linker Command File For 28335 examples that run out of RAM
//
//          This ONLY includes all SARAM blocks on the 28335 device.
//          This does not include flash or OTP. 
//
//          Keep in mind that L0 and L1 are protected by the code
//          security module.
//
//          What this means is in most cases you will want to move to 
//          another memory map file which has more memory defined.  
//
//###########################################################################
// $TI Release: DSP2833x Header Files V1.03 $
// $Release Date: 6.4.2010 $
//###########################################################################
*/

/* ======================================================
// For Code Composer Studio V2.2 and later
// ---------------------------------------
// In addition to this memory linker command file, 
// add the header linker command file directly to the project. 
// The header linker command file is required to link the
// peripheral structures to the proper locations within 
// the memory map.
//
// The header linker files are found in <base>\DSP2833x_Headers\cmd
//   
// For BIOS applications add:      DSP2833x_Headers_BIOS.cmd
// For nonBIOS applications add:   DSP2833x_Headers_nonBIOS.cmd    
========================================================= */

/* ======================================================
// For Code Composer Studio prior to V2.2
// --------------------------------------
// 1) Use one of the following -l statements to include the 
// header linker command file in the project. The header linker
// file is required to link the peripheral structures to the proper 
// locations within the memory map                                    */

/* Uncomment this line to include file only for non-BIOS applications */
/* -l DSP2833x_Headers_nonBIOS.cmd */

/* Uncomment this line to include file only for BIOS applications */
/* -l DSP2833x_Headers_BIOS.cmd */

/* 2) In your project add the path to <base>\DSP2833x_headers\cmd to the
   library search path under project->build options, linker tab, 
   library search path (-i).
/*========================================================= */

/* Define the memory block start/length for the F28335  
   PAGE 0 will be used to organize program sections
   PAGE 1 will be used to organize data sections

   Notes: 
         Memory blocks on F28335 are uniform (ie same
         physical memory) in both PAGE 0 and PAGE 1.  
         That is the same memory region should not be
         defined for both PAGE 0 and PAGE 1.
         Doing so will result in corruption of program 
         and/or data. 
         
         L0/L1/L2 and L3 memory blocks are mirrored - that is
         they can be accessed in high memory or low memory.
         For simplicity only one instance is used in this
         linker file. 
         
         Contiguous SARAM memory blocks can be combined 
         if required to create a larger memory block. 
*/

--diag_suppress=16002 
MEMORY
{
PAGE 0 :
   /* BEGIN is used for the "boot to SARAM" bootloader mode      */
   /* BOOT_RSVD is used by the boot ROM for stack.               */
   /* This section is only reserved to keep the BOOT ROM from    */
   /* corrupting this area during the debug process              */
   
   BEGIN      : origin = 0x000000, length = 0x000002     /* Boot to M0 will go here                      */
   BOOT_RSVD  : origin = 0x000002, length = 0x00004E     /* Part of M0, BOOT rom will use this for stack */               
   RAMM0      : origin = 0x000050, length = 0x0003B0

   RAML0      : origin = 0x008000, length = 0x001000    
   RAML1      : origin = 0x009000, length = 0x001800    
   RAML2      : origin = 0x00B000, length = 0x001000    
   RAML3      : origin = 0x00C000, length = 0x001000 
   ZONE7A     : origin = 0x200000, length = 0x00FC00    /* XINTF zone 7 - program space */ 
   CSM_RSVD   : origin = 0x33FF80, length = 0x000076     /* Part of FLASHA.  Program with all 0x0000 when CSM is in use. */
   CSM_PWL    : origin = 0x33FFF8, length = 0x000008     /* Part of FLASHA.  CSM password locations in FLASHA            */
   ADC_CAL    : origin = 0x380080, length = 0x000009
   RESET      : origin = 0x3FFFC0, length = 0x000002
   IQTABLES   : origin = 0x3FE000, length = 0x000b50
   IQTABLES2  : origin = 0x3FEB50, length = 0x00008c
   FPUTABLES  : origin = 0x3FEBDC, length = 0x0006A0
   BOOTROM    : origin = 0x3FF27C, length = 0x000D44               

         
PAGE 1 : 
   RAMM1      : origin = 0x000400, length = 0x000400     /* on-chip RAM block M1 */
   RAML4      : origin = 0x00C000, length = 0x001000    
   RAML5      : origin = 0x00D000, length = 0x001000    
   RAML6      : origin = 0x00E000, length = 0x001000    
   RAML7      : origin = 0x00F000, length = 0x001000 
   ZONE7B     : origin = 0x20FC00, length = 0x000400     /* XINTF zone 7 - data space */
}
 
 
SECTIONS
{
   /* Setup for "boot to SARAM" mode: 
      The codestart section (found in DSP28_CodeStartBranch.asm)
      re-directs execution to the start of user code.  */
   codestart        : > BEGIN,     PAGE = 0
   ramfuncs         : > RAML0,     PAGE = 0  
   .text            : > RAML1,     PAGE = 0
   .cinit           : > RAML0,     PAGE = 0
   .pinit           : > RAML0,     PAGE = 0
   .switch          : > RAML0,     PAGE = 0
   
   .stack           : > RAMM1,     PAGE = 1
   .ebss            : > RAML4,     PAGE = 1
   .econst          : > RAML5,     PAGE = 1      
   .esysmem         : > RAMM1,     PAGE = 1

 /* IQmath inclues the assembly routines in the IQmath library
      IQmathTables is used by division, IQsin, IQcos, IQatan, IQatan2
                   this is in boot ROM so we make it NOLOAD.  Using
                   the ROM version saves space at the cost of 1 cycle
                   per access (boot ROM is 1 wait).
      IQmathTablesRam is used by IQasin, IQacos, and IQexp
                   on 2833x and 2823x the IQNexpTable is in ROM so it
                   is placed in its own section.  If IQexp or IQNexp is
                   not called by the program, this will cause a linker
                   warning.
   */

   IQmath           : > RAML2,   PAGE = 0
   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)

   }
   */
   
   FPUmathTables    : > FPUTABLES, PAGE = 0, TYPE = NOLOAD


     
   DMARAML4         : > RAML4,     PAGE = 1
   DMARAML5         : > RAML5,     PAGE = 1
   DMARAML6         : > RAML6,     PAGE = 1
   DMARAML7         : > RAML7,     PAGE = 1
   
   ZONE7DATA        : > ZONE7B,    PAGE = 1  

   .reset           : > RESET,     PAGE = 0, TYPE = DSECT /* not used                    */
   csm_rsvd         : > CSM_RSVD   PAGE = 0, TYPE = DSECT /* not used for SARAM examples */
   csmpasswds       : > CSM_PWL    PAGE = 0, TYPE = DSECT /* not used for SARAM examples */
   
   /* Allocate ADC_cal function (pre-programmed by factory into TI reserved memory) */
   .adc_cal     : load = ADC_CAL,   PAGE = 0, TYPE = NOLOAD
     
}

SECTIONS
{
	DLOG: 			> RAML4,PAGE = 1
}



/*
//===========================================================================
// End of file.
//===========================================================================
*/

Regards

  • Hello!

    Try to edit two lines of your CMD file thus:

    .text : >> RAML1 | RAML2,  PAGE = 0

    ------------------------------

    ------------------------------

    IQmath : > RAML3,  PAGE = 0

    Regards,

    Igor

  • The new form of cmd file looks like below but problem continues. I think it tries to use RAML1 or RAML2, can it use both of these areas at the same time? If I load the program to the FLASH memory does it fix? For now program is not suitable for loading to the FLASH, i must learn how to boot from FLASH. Also I must use an array that will contain 10,000 byte (10kbyte) (I do not use for now), can internal RAM satisfies it? I have also external SRAM but i do not want to use external one.

    ---

    .text : > RAML1|RAML2, PAGE = 0
    .cinit : > RAML0, PAGE = 0
    .pinit : > RAML0, PAGE = 0
    .switch : > RAML0, PAGE = 0

    .stack : > RAMM1, PAGE = 1
    .ebss : > RAML4, PAGE = 1
    .econst : > RAML5, PAGE = 1
    .esysmem : > RAMM1, PAGE = 1

    IQmath : > RAML3, PAGE = 0

    ---

    The result of build is:

    "../F28335_RAM_HVPM_Sensorless.CMD", line 124: error: program will not fit into
    available memory. placement with alignment/blocking fails for section

    ".text" size 0x1c26 page 0. Available memory ranges:
    >> Compilation failure
    RAML1 size: 0x1800 unused: 0x1800 max hole: 0x1800
    RAML2 size: 0x1000 unused: 0x1000 max hole: 0x1000
    error: errors encountered during linking; "HVPM_Sensorless_2833x.out" not
    built
    gmake: *** [HVPM_Sensorless_2833x.out] Error 1
    gmake: Target `all' not remade because of errors.

  • The syntax shown by Igor will split the section among multiple memory ranges.
    .text : >> RAML1 | RAML2,  PAGE = 0

  • Thanks to both of you, using >> solved the problem. But now I have another problem, I defined an array of 10000 memebers of int16 (int16 array[10000]) for data logging, now it gives similar error for;

    .ebss            : > RAML4,     PAGE = 1

    Build result:

    ---

    "../F28335_RAM_HVPM_Sensorless.CMD", line 130: error: program will not fit into
    available memory. run placement with alignment/blocking fails for section

    ".ebss" size 0x290e page 1. Available memory ranges:
    >> Compilation failure
    RAML4 size: 0x1000 unused: 0xce0 max hole: 0xce0
    error: errors encountered during linking; "HVPM_Sensorless_2833x.out" not
    built
    gmake: *** [HVPM_Sensorless_2833x.out] Error 1
    gmake: Target `all' not remade because of errors.

    **** Build Finished ****

  • Hello!

    You can try to act with the same way by association of splitted memory partitions:

    .ebss : >> RAML4|RAML5|RAML6, PAGE = 1
    .econst : >> RAML4|RAML5|RAML6, PAGE = 1

    But you can't do that endlessly, because of RAM size is very limited and perhaps you will need to go to FLASH configuration of project further. In general I would recommend you this link for common understanding http://processors.wiki.ti.com/index.php/C28x_Compiler_-_Understanding_Linking

    Also (Attention please!) you have to be careful with large arrays when you apply splitting memory http://e2e.ti.com/support/microcontrollers/c2000/f/171/p/284770/993827.aspx#993827

    Regards,

    Igor

  • Hello Igor,

    Thanks for your help, i will try to FLASH configuration but i want to ask something more, i changed the .cmd as you adviced. Total space is 0x2ca2 and requirement is 0x2912, i mean 0x2ca2 > 0x2912 but builder still gives error;

    .stack : > RAMM1, PAGE = 1
    .ebss : >> RAML4|RAML5|RAML6, PAGE = 1
    .econst : >> RAML4|RAML5|RAML6, PAGE = 1
    .esysmem : > RAMM1, PAGE = 1

    Build result:

    "../F28335_RAM_HVPM_Sensorless.CMD", line 130: error: program will not fit into

    available memory. run placement with alignment/blocking fails for section
    >> Compilation failure
    ".ebss" size 0x2912 page 1. Available memory ranges:
    RAML4 size: 0x1000 unused: 0xca2 max hole: 0xc8a
    RAML5 size: 0x1000 unused: 0x1000 max hole: 0x1000
    RAML6 size: 0x1000 unused: 0x1000 max hole: 0x1000
    error: errors encountered during linking; "HVPM_Sensorless_2833x.out" not
    built
    gmake: *** [HVPM_Sensorless_2833x.out] Error 1
    gmake: Target `all' not remade because of errors.

    **** Build Finished ****

  • Yes, Gokhan,

    splitting is not always convenient. At these cases instead the following 

    RAML4 : origin = 0x00C000, length = 0x001000
    RAML5 : origin = 0x00D000, length = 0x001000
    RAML6 : origin = 0x00E000, length = 0x001000

    better to use for example:

    RAML456 : origin = 0x00C000, length = 0x003000

    If you  will decide to use Flash memory somewhen then i would recommend you this AR 4527.TI_Running_from_Flash_spra958l.pdf.

    Regards,

    Igor 

  • Me too faced the same problem, 

    I increased the length of Memory containing .ebss section to manifold that is required and it worked.

    Kind Regards

    Karuna Mudliyar