Binary, produced by MSP430GCC, has strange start address for text segment
After compiling an exemplary C program with msp430-gcc (LTS 20120406 unpatched) for the MSPG2211 I got the following output using the readelf command:
section header
program header
The address space of the MSPG2211 microcontroller is structured as follows:
0x0000 - 0x01FF - Peripherals
0x0200 - 0x027F - RAM
0x1000 - 0x10FF - Flash (information memory)
0x1100 - 0xF7FF - ???
0xF800 - 0xFFFF - Flash (code memory + interrupt vectors)
The text section shown in the section header starts at 0xF800 which is the first address of the code memory.
The text segment, including only the text section, is bigger than the text section and starts already at 0xF76C.
As I understood, the loadable segments gets loaded to the shown physical addresses for program execution.
So why the start address of the text segment lies within an undefined memory region?
Some of the names sections (such as .text) contain data that is actually loaded into the MCU.
The ELF program headers, however, contain only metadata; their address does not matter.
- How to extract only the raw contents of an ELF section?
- How to list on-the-fly all the functions/symbols available in C code on a Linux architecture?
- which part of ELF file must be loaded into the memory?
- Is the statement “Uninitialized global variables get weak symbols” in CSAPP accurate?
- What do R_X86_64_32S and R_X86_64_64 relocation mean?
- What is the difference of weak and unique symbol binding?
- How to MODIFY an ELF file with Python
- Why is elf strip not cross platform
- Override symbols in non-dynamic sections of dynamically linked executable
- Difference between Microsoft compiler and GNU compiler, in terms of output executable file size
- Objcopy --remove-section does not leave an ELF binary the same as the original before --add-section
- How can I make objcopy -Obinary append every text section?
- How would I be able to parse ELF format for my kernel in C?
- Add interpreter to shared object without touching the code
- Problems with rust formatting (x86-unknown-none target)
- Why are some ELF sections mapped to multiple segments
- How can I edit $rip and $rsp in a core file to help a debugger generate a more user friendly expereince?
- Are there always-used and Kernel-specific system call for BSDs and Linux?
- mmap with file as an input, with unaligned offset
- Can I change 'rpath' in an already compiled binary?
- CMAKE error while building the application (No SOURCES given to target)
- pyelftools: retrieve section flags like objdump does for an elf32-littlearm binary
- entry() get into the different address from the entry point I set in the Elf
- readelf -R (--relocated-dump) option
- Troubleshooting Execution Failure of the musl-libc Shared Library
- Getting the error: bash: (program): cannot execute binary file: Exec format error, on both 32-bit and 64-bit Windows
- Analyzing Relocations in ARM for cortex-m4
- What is the difference between executable formats?
- How to parse correctly the `.note.gnu.property` section of an ELF executable?
- Does my C program actually start at _start?