TMS320F28032: program will not fit into available memory

Howard,

I think the syntax should be : 

RUN = RAML0 | RAML1

or

RUN >> RAML0 | RAML1,

The same problem happens after changing the syntax.

I want to point out that RAML0 and RAML1 are not adjacent.

Are you getting same error or it is different error? Can you create a big section which is good for the size and then try it? May be there is some issue in automatic splitting between the sections.

The same error. 

If I rewrite the CMD file and create a bigger single section, it's good.

Why can't the CCS automatically split my code into two sections? The two sections in total is large enough.

Howard,

I have seen similar issue. I will follow it up with CCS team.

Santosh,

any update on this question?

I see multiple things wrong.  I'd like to address them one at a time.

According to the error message in the first post, the size of the output section IsrRamfuncs is 0x902 words, the size of the memory range RAML0 is 0x900 words, and the size of the RAML1 memory range is 0x100 words.  Is the IsrRamfuncs output section made up of a single input section from one file?  If you don't understand that question, please read the first part of the article Linker Command File Primer to understand the difference between the terms output section and input section.

Thanks and regards,

-George

Hi George:

Is my question, in my project, the IsrRamfuncs is our program code but run in RAM code define like  #pragma  CODE_SECTION(my function, "IsrRamfuncs"); but the "IsrRamfuncs" is so big , over 0x900, the origianl CMD configuration of RAML0 is only 0x900 length, in other RAM places, RAML1 is 0x100 length can be use, i don't want change the RAM space configuration, how can i load the IsrRamfuncs into the union of RAML0 and RAML1?

This thread was started by Howard Zhou.  I presume you are working with Howard on the same problem.

There is a solution to your problem.  But it requires some significant changes.

I presume the output section IsrRamfuncs contains multiple functions that are defined in the same source file.  For that source file, please add the compiler build option --gen_func_subsections.  This option causes the compiler to put each function into a separate section with names similar to IsrRamfuncs:_name_of_function.  These separate sections can then be allocated to different memory ranges.

In the linker command file, remove the code shown in the first post, and replace it with something similar to ...

    IsrRamfuncs : LOAD = FLASHD,
                  RUN >> RAML0 | RAML1,
                  table(BINIT),
                  PAGE = 0

   .binit       : > FLASHD

This creates an output section named IsrRamfuncs.  It is composed of all the input sections which start with the name IsrRamfuncs, such as IsrRamfuncs:_name_of_function.  It it loaded into the FLASHD memory range.  The run allocation is split across the memory ranges RAML0 and RAML1, in that order.  The split occurs on input section boundaries.  In this specific case, that means the split occurs on function boundaries.  

In the previous system, the method to copy from load memory to run memory is similar to ...

memcpy(&RamfuncsRunStart, &RamfuncsLoadStart, (size_t)&RamfuncsLoadSize); 

This method presumes both the run allocation and the load allocation are a single contiguous block of memory.  Because the run allocation is split, that doesn't work.  Please find this line in the source and comment it out.

The line table(BINIT) uses a feature of the linker called copy tables.  These copy tables are how the functions are copied from flash to RAM.  To learn more about them, please search the C28x assembly tools manual for the sub-chapter titled Using Linker-Generated Copy Tables.  In summary, a copy table can handle a split allocation of the load memory, the run memory, or both.  The BINIT argument means the BINIT copy table is used to perform this copy.  The BINIT copy table is automatically handled by the startup code in the compiler RTS library.  If that startup code is replaced with a different implementation, then this solution does not work.

The BINIT copy table is in the output section named .binit.  This an initialized section like .text.  The last line allocates this section to flash memory.

Thanks and regards,

-George