dbdd722239
Pass the --print-memory-usage to the linker on the first link if the toolchain supports it. Don't use this option with the second link because seeing it twice could confuse users and using it on the second link would suppress it when the first link has a ram/flash-usage issue. Note that the memory regions are symbolic concepts defined by the linker scripts and do not necessarily map directly to the real physical address space. Take also note that some platforms do two passes of the linker so the results do not match exactly to the final elf file. See also rom_report, ram_report and https://sourceware.org/binutils/docs/ld/MEMORY.html This is particularly useful when the linker fails due to excessive flash/ram usage. When a section does not fit into a memory region the linker will exit with an error code and will state how big the overflow was. But it doesn't state what the memory region size is, or what memory regions exist, which is good to know when debugging overflow issues. Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| generated | ||
| CMakeLists.txt | ||
| empty_file.c | ||
| Kconfig | ||
| printk.c | ||
| reboot.c | ||