• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 54 subscribers
  • Views 457 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.

CCS/LAUNCHXL-CC1310: Segment and Code size

Keith Barkley
Guru 43135 points

Part Number: LAUNCHXL-CC1310
Other Parts Discussed in Thread: CC1310

Tool/software: Code Composer Studio

I have mentioned in another thread that I have started a new project with the CC1310.

I started with an Easylink TiRTOS project and set up two tasks. I had set the task stack size to 8192 since I am using Display_printf(), anyway, I got linker errors about my project not fitting. When I reduced the task stack size to 1024 the error went away.

What is the best way to determine the size of the various segments during a build to see if I am getting close to the limits?

  • 0
    TI__Guru**** 253240 points

    Near the top of the linker map file is a table similar to this one ...

    MEMORY CONFIGURATION

         name            origin    length      used     unused   attr    fill
----------------------  --------  ---------  --------  --------  ----  --------
  FLASH                 00000000   00058000  00002d15  000552eb  R  X
  GPRAM                 11000000   00002000  00000000  00002000  RW X
  SRAM                  20000000   00014000  00000bb0  00013450  RW X

    The first column is the name of a memory range from the MEMORY directive in the linker command file.  The closer the unused column is to 0, the nearer that memory range is to being exhausted.

    Thanks and regards,

    -George

  • 0 in reply to George Mock
    Guru 43135 points

    Thanks, I knew it was simple, I have just never needed it before.