Linker ignoring stack size setting.

Timothy Canham

Other Parts Discussed in Thread: TMDX570LC43HDK, HALCOGEN

This is CCS 6.1.3.00034 on Windows 10.

Target is TMS570LC43XX on the TMDX570LC43HDK.

I am setting the stack size in the Build->ARM Linker->Basic Options->"Set C system stack size" to a larger value (say, 0xC800), but when I look at the map file, it always says:

MEMORY CONFIGURATION

name origin length used unused attr fill
---------------------- -------- --------- -------- -------- ---- --------
VECTORS 00000000 00000020 00000020 00000000 X
FLASH0 00000020 001fffe0 000306ce 001cf912 R X
FLASH1 00200000 00200000 00000000 00200000 R X
STACKS 08000000 00001500 00000000 00001500 RW
RAM 08001500 0007eb00 000109cf 0006e131 RW

When I run the debugger, it shows the initial value of the stack pointer as 08001000, or 4K. It counts down as I call into functions as expected. It doesn't seem to matter what I set the stack size to, it's always 4K. I even set it to 2K to see if there is some hidden max value, but it was still 4K.

over 9 years ago

0 desouza over 9 years ago

TI__Guru**** 171094 points

Hi,

Check the reference below:
processors.wiki.ti.com/.../Linker_Command_File_Primer

The option you are seeing in the linker map file is a straight copy of the MEMORY directive of the linker CMD file.

The stack defined by the option -stack (or --stack_size) is placed in the section .stack under the SECTIONS directive. That is most probably being allocated to the RAM segment of the MEMORY directive.

Just a remark: sometimes the linker CMD file also contains a -stack (or --stack_size) entry, which may override the parameter passed to the GUI. Despite this is very common in example code for certain device families, I don't think it is the case.

Hope this helps,
Rafael

0 Timothy Canham over 9 years ago in reply to desouza

Intellectual 440 points

"That is most probably being allocated to the RAM segment of the MEMORY directive. "

The stack pointer address in the debugger is actually in the 0x1500 to 0x0 range, which would put it in the STACKS region in the configuration. That's why I don't think it's going into RAM.

0 Timothy Canham over 9 years ago in reply to Timothy Canham

Intellectual 440 points

Where is the linker CMD file located?

0 Timothy Canham over 9 years ago in reply to Timothy Canham

Intellectual 440 points

Think I found it. It is in a directory created by HalCoGen. It looks like it is overriding the linker. I can change it in the HalCoGen project file I guess.

0 AartiG over 9 years ago in reply to Timothy Canham

TI__Guru**** 173310 points

Yes, for Halcogen the stack sizes are set in the halcogen project. So you can modify it directly in the HalcoGen tool (under the RAM tab), or edit the sys_core.asm file generated by Halcogen that contains the stack pointer initializations.

0 Timothy Canham over 9 years ago in reply to AartiG

Intellectual 440 points

So the summary for those in the forum is that the linker setting in the GUI is ignored if there is a linker command file. If you are using HalCoGen, it is placed in the source directory and is called HL_sys_link.cmd. HalCoGen will allow you to modify the memory allocations in the tool and will adjust the remaining sections for you.

Code Composer Studio™︎

Code Composer Studio forum

Linker ignoring stack size setting.