AnsweredAssumed Answered

BSS section problems KDS3.0 with kv4x

Question asked by Roberto Zanichelli on Feb 10, 2017
Latest reply on Feb 16, 2017 by Roberto Zanichelli

Good morning,

I've a problem related to linker allocation of memory sections, the linker keep putting variables in .bss memory section even if they are initialized and different from 0. 

The #pragma section instruction on the arm site (that i've seen in a similar discussion)  seems to have no effect. 

 

 

COMPILER OUTPUT:


Invoking: Cross ARM C++ Linker

.....
..../kds_v3/toolchain/bin/../lib/gcc/arm-none-eabi/4.8.4/../../../../arm-none-eabi/bin/ld.exe: myelf.elf section `.bss' will not fit in region `m_data'
..../kds_v3/toolchain/bin/../lib/gcc/arm-none-eabi/4.8.4/../../../../arm-none-eabi/bin/ld.exe: region `m_data' overflowed by 92 bytes
collect2.exe: error: ld returned 1 exit status

 

 

i want to know if there is an effective and proved solution to avoid bss occupation because every global variable that i use has it's own initialization function that is called inside the code so i don't see the need of the compiler to do it before my initialization.

Thaks for help,

i hope you help me to clarify this.

Outcomes