Hi,
we're currently developing the firmware for our embedded product based on the ESP32. While the general development experience is very pleasant, we noticed that the firmware binary is very large, rapidly approaching 1 MB (966 kB at the moment).
How can we debug this? Is there a way to see if debug symbols are included in the binary or if there are large libraries we don't actually need?
Thank you for any suggestions!
David
ESP-IDF binary size
Re: ESP-IDF binary size
These make targets might help:
make size - Display the static memory footprint of the app
make size-components, size-files - Finer-grained memory footprints
make size - Display the static memory footprint of the app
make size-components, size-files - Finer-grained memory footprints
-
- Posts: 79
- Joined: Tue Apr 26, 2016 5:10 am
Re: ESP-IDF binary size
Another thing to consider: (for release firmware at least)
Consider changing the log level from verbose, debug or info, to either warning or error.
Removing the additional logs will reduce the binary size significantly, especially if lots of logging is used in your program or in the IDF components that you are using.
Consider changing the log level from verbose, debug or info, to either warning or error.
Removing the additional logs will reduce the binary size significantly, especially if lots of logging is used in your program or in the IDF components that you are using.
Who is online
Users browsing this forum: Baidu [Spider] and 110 guests