Timeline for How do I find out at compile time how much of an STM32's Flash memory and dynamic memory (SRAM) is used up?
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Dec 6, 2021 at 20:49 | history | suggested | Gabriel Staples | CC BY-SA 4.0 | bold the final answer to make it stick out |
| Dec 6, 2021 at 20:04 | review | Suggested edits | |||
| S Dec 6, 2021 at 20:49 | |||||
| Sep 26, 2020 at 23:54 | comment | added | Gabriel Staples | I just added a detailed analysis in my new answers here: electronics.stackexchange.com/a/523439/26234 and here: stackoverflow.com/a/64080798/4561887. | |
| Sep 26, 2020 at 20:59 | review | Suggested edits | |||
| Sep 27, 2020 at 10:22 | |||||
| Sep 26, 2020 at 1:41 | comment | added | Gabriel Staples | I've posted a question here: stackoverflow.com/q/64073080/4561887. | |
| Sep 26, 2020 at 0:39 | comment | added | Gabriel Staples | Also, regarding your statement: (In environments where a program must be loaded into memory before running, it would be the total memory footprint of the program.) ....you mean like on a regular computer, right? I'm trying to see these values for a program on a regular computer now, instead of on a microcontroller. So, size name_of_executable seems to be the answer. Ex: size a.out. | |
| Sep 26, 2020 at 0:33 | comment | added | Gabriel Staples | My question above still stands: where is .rodata in all this? | |
| Apr 2, 2019 at 23:49 | comment | added | Gabriel Staples | I'm looking at The GNU linker user manual, by Steve Chamberlain and Ian Lance Taylor, as well as looking in my linker script .ld file. Pg. 42 (pdf pg 48) of the manual (screenshot here) shows "four output sections", namely, .text, .rodata, .data., and .bss. Is data shown above by arm-none-eabi-size the sum of what is in .rodata and .data in the linker script? | |
| Mar 22, 2018 at 9:54 | comment | added | 0___________ | @GabrielStaples - elf contains much more system, symbolic etc configuration. If you enable high level of the debugging information your .elf file may be many MB long :). | |
| Mar 22, 2018 at 9:52 | comment | added | 0___________ | @duskwuff it is actually not very accurate. Many STM32 uC have more than one RAM (most of F3, many F4, all F4 & H7). It does not take it into the consideration. Another problem - the stack, it does not take it into the account. | |
| Mar 22, 2018 at 0:06 | comment | added | user39382 | Oops, I thought it was the size of the file, but it's actually just the sum of the text/data/bss sections. It should still be ignored. :) | |
| Mar 22, 2018 at 0:05 | history | edited | user39382 | CC BY-SA 3.0 | added 84 characters in body |
| Mar 22, 2018 at 0:02 | comment | added | Gabriel Staples | Also, for those who may have overlooked this fact (myself included initially), the command to see these size values is right in the System Workbench output: arm-none-eabi-size STM32F103RB_Nucleo.elf | |
| Mar 22, 2018 at 0:00 | comment | added | Gabriel Staples | So, despite the fact you said that dec and hex are the size of my ELF file, my ELF file is actually 616876 bytes. Any idea why? | |
| Mar 21, 2018 at 23:43 | vote | accept | Gabriel Staples | ||
| Aug 20 at 4:42 | |||||
| Mar 21, 2018 at 23:36 | history | answered | user39382 | CC BY-SA 3.0 |