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.

Huge .bin file

Other Parts Discussed in Thread: TM4C123FE6PM, TM4C123FH6PM

Hey guys

 

I've defined following post-build step to generate a .bin file (nothing out of the ordanary):

"${CCE_INSTALL_ROOT}/utils/tiobj2bin/tiobj2bin.bat" "${BuildArtifactFileName}" "../../bin/${BuildArtifactFileBaseName}.bin" "${CG_TOOL_ROOT}/bin/armofd.exe" "${CG_TOOL_ROOT}/bin/armhex.exe" "${CCE_INSTALL_ROOT}/utils/tiobj2bin/mkhex4bin.exe"

Generally it works, but a 512 MB binary file is being created. The reason for this is a stack fill value specified in the linker command file.

MEMORY

{
FLASH (RX) : origin = 0x00000000, length = 0x00020000
SRAM (RWX) : origin = 0x20000000, length = 0x00008000
}

SECTIONS
{
.intvecs: > 0x00000000
.text : > FLASH
.const : > FLASH
.cinit : > FLASH
.pinit : > FLASH
.init_array : > FLASH

.vtable : > 0x20000000
.data : > SRAM
.bss : > SRAM
.sysmem : > SRAM
.stack : > SRAM (HIGH), fill = 0xDEADDEAD
}

Is there a method to specify which sections don't belong in the binary output file? Perhaps something similar to the paged memory of the TMS320 controllers.