Minimizing RAM Usage
In some cases, a firmware application’s available RAM may run low or run out entirely. In these cases, it’s necessary to tune the memory usage of the firmware application.
In general, firmware should aim to leave some “headroom” of free internal RAM in order to deal with extraordinary situations or changes in RAM usage in future updates.
Before optimizing ESP-IDF RAM usage, it’s necessary to understand the basics of ESP32-C3 memory types, the difference between static and dynamic memory usage in C, and the way ESP-IDF uses stack and heap. This information can all be found in Heap Memory Allocation.
Measuring Static Memory Usage
Measuring Dynamic Memory Usage
ESP-IDF contains a range of heap APIs for measuring free heap at runtime. See Heap Memory Debugging.
In embedded systems, heap fragmentation can be a significant issue alongside total RAM usage. The heap measurement APIs provide ways to measure the “largest free block”. Monitoring this value along with the total number of free bytes can give a quick indication of whether heap fragmentation is becoming an issue.
Reducing Static Memory Usage
Reducing the static memory usage of the application increases the amount of RAM available for heap at runtime, and vice versa.
Generally speaking, minimizing static memory usage requires monitoring the .data and .bss sizes. For tools to do this, see Measuring Static Sizes.
Internal ESP-IDF functions do not make heavy use of static RAM allocation in C. In many instances (including: Wi-Fi library, Bluetooth controller) “static” buffers are still allocated from heap, but the allocation is done once when the feature is initialized and will be freed if the feature is deinitialized. This is done in order to maximize the amount of free memory at different points in the application life-cycle.
To minimize static memory use:
Declare structures, buffers, or other variables
constwhenever possible. Constant data can be stored in flash not RAM. This may require changing functions in the firmware to take
const *arguments instead of mutable pointer arguments. These changes can also reduce the stack usage of some functions.
If using Bluedroid, setting the option CONFIG_BT_BLE_DYNAMIC_ENV_MEMORY will cause Bluedroid to allocate memory on initialization and free it on deinitialization. This doesn’t necessarily reduce the peak memory usage, but changes it from static memory usage to runtime memory usage.
Reducing Stack Sizes
In FreeRTOS, task stacks are usually allocated from the heap. The stack size for each task is fixed (passed as an argument to
xTaskCreate()). Each task can use up to its allocated stack size, but using more than this will cause an otherwise valid program to crash with a stack overflow or heap corruption.
Therefore, determining the optimum sizes of each task stack can substantially reduce RAM usage.
To determine optimum task stack sizes:
Combine tasks. The best task stack size is 0 bytes, achieved by combining a task with another existing task. Anywhere that the firmware can be structured to perform multiple functions sequentially in a single task will increase free memory. In some cases, using a “worker task” pattern where jobs are serialized into a FreeRTOS queue (or similar) and then processed by generic worker tasks may help.
Consolidate task functions. String formatting functions (like
printf) are particularly heavy users of stack, so any task which doesn’t ever call these can usually have its stack size reduced.
Enabling Newlib nano formatting will reduce the stack usage of any task that calls
printf()or other C string formatting functions.
Avoid allocating large variables on the stack. In C, any large struct or array allocated as an “automatic” variable (i.e. default scope of a C declaration) will use space on the stack. Minimize the sizes of these, allocate them statically and/or see if you can save memory by allocating them from the heap only when they are needed.
Avoid deep recursive function calls. Individual recursive function calls don’t always add a lot of stack usage each time they are called, but if each function includes large stack-based variables then the overhead can get quite high.
At runtime, call the function
uxTaskGetStackHighWaterMark()with the handle of any task where you think there is unused stack memory. This function returns the minimum lifetime free stack memory in bytes. The easiest time to call this is from the task itself: call
uxTaskGetStackHighWaterMark(NULL)to get the current task’s high water mark after the time that the task has achieved its peak stack usage (i.e. if there is a main loop, execute the main loop a number of times with all possible states and then call
uxTaskGetStackHighWaterMark()). Often, it’s possible to subtract almost the entire value returned here from the total stack size of a task, but allow some safety margin to account for unexpected small increases in stack usage at runtime.
uxTaskGetSystemState()at runtime to get a summary of all tasks in the system. This includes their individual stack “high watermark” values.
When debugger watchpoints are not being used, set the CONFIG_FREERTOS_WATCHPOINT_END_OF_STACK option to trigger an immediate panic if a task writes the word at the end of its assigned stack. This is slightly more reliable than the default CONFIG_FREERTOS_CHECK_STACKOVERFLOW option of “Check using canary bytes”, because the panic happens immediately, not on the next RTOS context switch. Neither option is perfect, it’s possible in some cases for stack pointer to skip the watchpoint or canary bytes and corrupt another region of RAM, instead.
Internal Stack Sizes
ESP-IDF allocates a number of internal tasks for housekeeping purposes or operating system functions. Some are created during the startup process, and some are created at runtime when particular features are initialized.
The default stack sizes for these tasks are usually set conservatively high, to allow all common usage patterns. Many of the stack sizes are configurable, and it may be possible to reduce them to match the real runtime stack usage of the task.
If internal task stack sizes are set too small, ESP-IDF will crash unpredictably. Even if the root cause is task stack overflow, this is not always clear when debugging. It is recommended that internal stack sizes are only reduced carefully (if at all), with close attention to “high water mark” free space under load. If reporting an issue that occurs when internal task stack sizes have been reduced, please always include this information and the specific configuration that is being used.
FreeRTOS Timer Task to handle FreeRTOS timer callbacks has stack size CONFIG_FREERTOS_TIMER_TASK_STACK_DEPTH.
The Ethernet driver creates a task for the MAC to receive Ethernet frames. If using the default config
ETH_MAC_DEFAULT_CONFIGthen the task stack size is 4 KB. This setting can be changed by passing a custom
eth_mac_config_tstruct when initializing the Ethernet MAC.
FreeRTOS idle task stack size is configured by CONFIG_FREERTOS_IDLE_TASK_STACKSIZE.
To see how to optimize RAM usage when using
mDNS, please check Performance Optimization.
Aside from built-in system features such as esp-timer, if an ESP-IDF feature is not initialized by the firmware then no associated task is created. In those cases, the stack usage is zero and the stack size configuration for the task is not relevant.
Reducing Heap Usage
For functions that assist in analyzing heap usage at runtime, see Heap Memory Debugging.
Normally, optimizing heap usage consists of analyzing the usage and removing calls to
malloc() that aren’t being used, reducing the corresponding sizes, or freeing previously allocated buffers earlier.
There are some ESP-IDF configuration options that can reduce heap usage at runtime:
lwIP documentation has a section to configure Minimum RAM usage.
Wi-Fi Buffer Usage describes options to either reduce numbers of “static” buffers or reduce the maximum number of “dynamic” buffers in use, in order to minimize memory usage at possible cost of performance. Note that “static” Wi-Fi buffers are still allocated from heap when Wi-Fi is initialized and will be freed if Wi-Fi is deinitialized.
Several Mbed TLS configuration options can be used to reduce heap memory usage. See the Mbed TLS docs for details.
There are other configuration options that will increase heap usage at runtime if changed from the defaults. These are not listed here, but the help text for the configuration item will mention if there is some memory impact.
Optimizing IRAM Usage
The available DRAM at runtime (for heap usage) is also reduced by the static IRAM usage. Therefore, one way to increase available DRAM is to reduce IRAM usage.
If the app allocates more static IRAM than is available then the app will fail to build and linker errors such as
section `.iram0.text' will not fit in region `iram0_0_seg',
IRAM0 segment data does not fit and
region `iram0_0_seg' overflowed by 84 bytes will be seen. If this happens, it is necessary to find ways to reduce static IRAM usage in order to link the application.
The following options will reduce IRAM usage of some ESP-IDF features:
Enable CONFIG_FREERTOS_PLACE_FUNCTIONS_INTO_FLASH. Provided these functions are not (incorrectly) used from ISRs, this option is safe to enable in all configurations.
Enable CONFIG_FREERTOS_PLACE_SNAPSHOT_FUNS_INTO_FLASH. Enabling this option will place snapshot-related functions, such as
uxTaskGetSnapshotAll, in flash.
Enable CONFIG_RINGBUF_PLACE_FUNCTIONS_INTO_FLASH. Provided these functions are not (incorrectly) used from ISRs, this option is safe to enable in all configurations.
Enable CONFIG_RINGBUF_PLACE_ISR_FUNCTIONS_INTO_FLASH. This option is not safe to use if the ISR ringbuf functions are used from an IRAM interrupt context, e.g. if CONFIG_UART_ISR_IN_IRAM is enabled. For the IDF drivers where this is the case you will get an error at run-time when installing the driver in question.
CONFIG_SPI_FLASH_ROM_IMPL enabling this option will free some IRAM but will mean that esp_flash bugfixes and new flash chip support is not available.
Disabling CONFIG_SPI_MASTER_ISR_IN_IRAM prevents spi_master interrupts from being serviced while writing to flash, and may otherwise reduce spi_master performance, but will save some IRAM.
Setting CONFIG_HAL_DEFAULT_ASSERTION_LEVEL to disable assertion for HAL component will save some IRAM especially for HAL code who calls HAL_ASSERT a lot and resides in IRAM.
Flash Suspend Feature
When using ESP Flash APIs and other APIs based on the former (NVS, Partition APIs, etc.), the Cache will be disabled. During this period of time, any code executed must reside in internal RAM (see Concurrency Constraints for Flash on SPI1). Hence, interrupt handlers that are not in internal RAM will not be executed.
To achieve this, ESP-IDF Drivers usually have the following two options: - an option to place the driver’s internal ISR handler in internal RAM - an option to place some control functions in internal RAM.
User ISR callbacks (and involved variables) have to be in internal RAM if they are also used in interrupt contexts.
Placing additional code into IRAM will exacerbate the IRAM usage. For this reason, there is CONFIG_SPI_FLASH_AUTO_SUSPEND, which can alleviate the aforementioned kinds of IRAM usage. By enabling this feature, cache won’t be disabled when ESP Flash and ESP-Flash-based APIs are used. Therefore, code and data in Flash can be executed or accessed normally, but with some minor delay. See Flash Auto Suspend for more details about this feature.
Regarding the flash suspend feature usage, and corresponding response time delay, please also see this example system/flash_suspend .
Moving frequently-called functions from IRAM to flash may increase their execution time.
Other configuration options exist that will increase IRAM usage by moving some functionality into IRAM, usually for performance, but the default option is not to do this. These are not listed here. The IRAM size impact of enabling these options is usually noted in the configuration item help text.