• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 396 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Heap put in binary

Larry Harmon
Expert 1340 points

Other Parts Discussed in Thread: CODECOMPOSER

I am building firmware with a large HEAP (64 K).  The heap ends up in the resulting binary file, converted from the .out file.

How can I prevent this?  Is there a linker option?

CCS 4.2.1

 

Regards,

Larry

  • 0
    TI__Guru**** 253170 points

    I presume you are using a hex utility, such has hex6x or hex470, to convert the .out file to the binary file.  The best method is to use the -exclude section_name option.  Use the name of the section which contains the heap.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Expert 1340 points

     

    The real problem is that CodeComposer does not always order the sections the way they are specified in the .cmd file.

     

    im my case the command file is specifying:

    SECTIONS
    {
        .intvecs:   > 0x60000000
       
        .text   :   > XSRAM
        .const  :   > XSRAM
       
        .cinit  :   > XSRAM
        .pinit  :   > XSRAM
        .sysmem :   > XSRAM     
     
        .data   :   > SRAM  
        .bss    :   > SRAM
       
        .stack  :   > SRAM (HIGH)
    }

    Even though .sysmem was specified as the last section to go into XSRAM, it was put in the middle

    My solution was to put a (HIGH) statement after the .sysmem: > XSRAM statement to force it to the top.

    Then, since it was uninitialized data it was not pit in the binary