Forum Discussion
Altera_Forum
Honored Contributor
8 years agoCris72,
I think your observation about the onchip ram is correct. In my application, I only have symbols defined in the onchip ram at 0xffff0000 and don't allocate any data or code in that space. That allocation is done in the linker script. I guess that's the reason why the .axf file and resulting .bin file don't contain data/code that needs to be initialized in that space. You can check for the condition you mention in the .axf file, with the following command: arm-altera-eabi-objdump -x <name of axf file> In my case, I get these sizes for the various sections in my .axf file. Note that the size is zero for the oc_ram sections. Sections: Idx Name size VMA LMA File off Algn 0 .text 0001df74 00100040 00100040 00010040 2**6 CONTENTS, ALLOC, LOAD, READONLY, CODE 1 .eh_frame 00000004 0011dfb4 0011dfb4 0002dfb4 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 2 .ARM.exidx 00000008 0011dfb8 0011dfb8 0002dfb8 2**2 CONTENTS, ALLOC, LOAD, READONLY, DATA 3 .rodata 00000f08 0011dfc0 0011dfc0 0002dfc0 2**3 CONTENTS, ALLOC, LOAD, CODE 4 .cs3.boot_rom 00000000 fffd0000 fffd0000 0002f9c0 2**3 CONTENTS 5 .cs3.boot_rom.bss 00000000 fffd0000 fffd0000 0002f9c0 2**0 CONTENTS 6 .cs3.oc_ram 00000000 ffff0000 ffff0000 0002f9c0 2**3 CONTENTS 7 .cs3.oc_ram.bss 00000000 ffff0000 ffff0000 0002f9c0 2**0 CONTENTS ....