How to understand the output of the toolchain's size tool?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to understand the output of the toolchain's size tool?

775 Views
kongdetao
Contributor III

Following is the output of the size tool.

My question is: Why the sections below the .stack are all started from the address 0x0?

D:\code\BCM1x_A_Sample\Debug\BCM1x_A_Sample.elf :
section size addr
.interrupts 0x400 0x0
.flash_config 0x10 0x400
.text 0x16b90 0x410
.interrupts_ram 0x400 0x1ffe0000
.data 0xcf4 0x1ffe0400
.code 0x0 0x1ffe10f4
.bss 0x14e68 0x20000000
.heap 0x400 0x20014e68
.stack 0x400 0x2001ec00
.ARM.attributes 0x30 0x0
.debug_info 0x8776d 0x0
.debug_abbrev 0x8368 0x0
.debug_aranges 0x3868 0x0
.debug_ranges 0x38e0 0x0
.debug_macro 0x1f15c 0x0
.debug_line 0x21ca9 0x0
.debug_str 0xb5a6b 0x0
.comment 0xa0 0x0
.debug_frame 0xe57c 0x0
Total 0x1c91d5

0 Kudos
3 Replies

607 Views
jiri_kral
NXP Employee
NXP Employee

Hi, 

the size utility is standard GNU size - here is more detailed description - GNU Binary Utilities: size  

Anyway - what is your S32DS version and MCU?

Jiri 

0 Kudos

607 Views
kongdetao
Contributor III

Thanks firstly!

I can understand the size tool's help info.

But, my question is:

     Why the  following sections all start from the address 0x0? 

.ARM.attributes 0x30 0x0
.debug_info 0x8776d 0x0
.debug_abbrev 0x8368 0x0
.debug_aranges 0x3868 0x0
.debug_ranges 0x38e0 0x0
.debug_macro 0x1f15c 0x0

0 Kudos

607 Views
BlackNight
NXP Employee
NXP Employee

These are pseudo (not real code) sections. the include debug information which won't occupy any memory on your device. The 0x0 is simply a pseudo start address.

I hop this helps,

Erich

0 Kudos