From 7687c5200cf0a1b621f474db6a00ee49269c7426 Mon Sep 17 00:00:00 2001 From: Vikram Date: Wed, 24 May 2023 17:48:33 +0530 Subject: [PATCH] Added description to disable coredump logs to ram_usage.rst Signed-off-by: Vikram --- docs/en/api-guides/performance/ram-usage.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/en/api-guides/performance/ram-usage.rst b/docs/en/api-guides/performance/ram-usage.rst index 5d8b8ab44dc..a24c695c50f 100644 --- a/docs/en/api-guides/performance/ram-usage.rst +++ b/docs/en/api-guides/performance/ram-usage.rst @@ -39,6 +39,7 @@ To minimize static memory use: - Declare structures, buffers, or other variables ``const`` whenever 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. :SOC_BT_SUPPORTED: - If using Bluedroid, setting the option :ref:`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. + - If :doc:`Coredump ` component is enabled, `ESP_COREDUMP_LOG` macros will use ~5KB internal memory to place strings into DRAM. By disabling :ref:`CONFIG_ESP_COREDUMP_LOGS` option, these logs are disabled and the memory is reclaimed. .. _optimize-stack-sizes: