You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current memanalyzer tool is available on platforms that have .NET support which increases the dependency of external tools and libraries. Because we already have dependency on python (esptool.py depends on it) and it is available on all supported OSes (Windows, FreeBSD, Linux, MacOS X) it would be a good idea to create a python script that produces output as memanalyzer and allows us to do more fine grained calculations as free heap, heap start address, stack start address, available memory space between heap and stack, etc.
#Memory / Section info:
------------------------------------------------------------------------------
Section| Description| Start (hex)| End (hex)|Used space
------------------------------------------------------------------------------
data| Initialized Data (RAM)| 3FFE8000| 3FFE8374| 884
rodata| ReadOnly Data (RAM)| 3FFE8378| 3FFEA0B8| 7488
bss| Uninitialized Data (RAM)| 3FFEA0B8| 3FFF0F70| 28344 (+8)
text| Cached Code (IRAM)| 40100000| 40105D46| 23878
irom0_text| Uncached Code (SPI)| 40209000| 40244AFA| 244474 (+32)
Total Used RAM : 36716
Free RAM : 45204
Free IRam : 8908
------------------------------------------------------------------------------
Plus we will have consistent output for all supported OSes. As a start we can use PR #753 from @cmarrin.
The text was updated successfully, but these errors were encountered:
The current memanalyzer tool is available on platforms that have .NET support which increases the dependency of external tools and libraries. Because we already have dependency on python (esptool.py depends on it) and it is available on all supported OSes (Windows, FreeBSD, Linux, MacOS X) it would be a good idea to create a python script that produces output as
memanalyzer
and allows us to do more fine grained calculations as free heap, heap start address, stack start address, available memory space between heap and stack, etc.Plus we will have consistent output for all supported OSes. As a start we can use PR #753 from @cmarrin.
The text was updated successfully, but these errors were encountered: