Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State TI Thinks Resolved
  • Locked Locked
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 713 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Original question:

CCS/AM5718: Building custom board for RTOS

CCS/AM5718: Why do stack and heap size differ from project propteries and the linker.cmd file

Stefan Thorlacius
Intellectual 570 points
Part Number: AM5718

Tool/software: Code Composer Studio

Hi

Why do stack and heap size differ from project propteries and the linker.cmd file

Should not seetings in the project properties be reflected in the linker.cmd file ?

In app.cfg there are a "third setup" of these sizes!

  

 * The BIOS module will create the default heap for the system.
 * Specify the size of this default heap.
 */
BIOS.heapSize = 0x1000;
/*
 * Build a custom SYS/BIOS library from sources.
 */
BIOS.libType = BIOS.LibType_Custom;
/* System stack size (used by ISRs and Swis) */
Program.stack = 0x2000;

   

Regards

  • 0
    TI__Guru**** 173310 points

    Stefan Thorlacius said:

    Should not seetings in the project properties be reflected in the linker.cmd file ?

    In app.cfg there are a "third setup" of these sizes!

    For projects that use TI-RTOS or RTSC components, the linker.cmd is auto-generated from the BIOS configuration file (.cfg). So the stack and heap sizes specified in the .cfg will be reflected in the linker.cmd and they are the ones used by the project. They will over-ride the GNU linker settings set in CCS Project Properties.

    The linker settings in Project Properties are typically used for a bare-metal/non RTOS projects.