diff options
| author | Eli Weiss <eliwss0@gmail.com> | 2021-11-30 13:22:47 -0600 |
|---|---|---|
| committer | JF <JF002@users.noreply.github.com> | 2021-12-30 20:57:26 +0100 |
| commit | c8214bc666a5daf1b0c1c323ae4af7cb5ae2510b (patch) | |
| tree | e74e60c59863f10daa91c152f6d00fec784ed4b5 /doc | |
| parent | f66fcdd3ca64fcbecfa264a506b7973b47ba1213 (diff) | |
Update MemoryAnalysis.md
Cleaned up MemoryAnalysis.md for greater readability
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/MemoryAnalysis.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/MemoryAnalysis.md b/doc/MemoryAnalysis.md index 20bb9283..376f98f6 100644 --- a/doc/MemoryAnalysis.md +++ b/doc/MemoryAnalysis.md @@ -60,7 +60,7 @@ Puncover is really easy to install: - Launch a browser at http://localhost:5000/ ### Analysis -Using the MAP file and tools, we can easily see what symbols are using most of the flash memory. In this case, with no surprise, fonts and graphics are the largest use of flash memory. +Using the MAP file and tools, we can easily see what symbols are using most of the flash memory. In this case, unsuprisingly, fonts and graphics are the largest use of flash memory.  @@ -245,7 +245,7 @@ Using this technique, I was able to trace all malloc calls at boot (boot -> digi - https://www.embedded.com/mastering-stack-and-heap-for-system-reliability-part-3-avoiding-heap-errors/ ## LVGL -I did a deep analysis of the usage of the buffer dedicated for lvgl (managed by lv_mem). +I did a deep analysis of the usage of the buffer dedicated to lvgl (managed by lv_mem). This buffer is used by lvgl to allocated memory for drivers (display/touch), screens, themes, and all widgets created by the apps. The usage of this buffer can be monitored using this code : @@ -256,7 +256,7 @@ lv_mem_monitor(&mon); NRF_LOG_INFO("\t Free %d / %d -- max %d", mon.free_size, mon.total_size, mon.max_used); ``` -The most interesting metric is `mon.max_used` which specifies the maximum number of bytes that were used from this buffer since the initialization of lvgl. +The most interesting metric is `mon.max_used` which specifies the maximum number of bytes used from this buffer since the initialization of lvgl. According to my measurements, initializing the theme, display/touch driver and screens cost **4752** bytes! Then, initializing the digital clock face costs **1541 bytes**. For example a simple lv_label needs **~140 bytes** of memory. |