esp_common: allow placing panic handler into IRAM on ESP32-S2

components/esp_common/Kconfig

@@ -227,7 +227,6 @@ menu "Common ESP-related"
     config ESP_PANIC_HANDLER_IRAM
         bool "Place panic handler code in IRAM"
         default n
-        depends on IDF_TARGET_ESP32  # pending ESP32-S2 support
         help
             If this option is disabled (default), the panic handler code is placed in flash not IRAM.
             This means that if ESP-IDF crashes while flash cache is disabled, the panic handler will

docs/en/api-guides/fatal-errors.rst

@@ -62,9 +62,7 @@ Behavior of panic handler is affected by two other configuration options.
 
 - If :doc:`Core Dump <core_dump>` feature is enabled, then system state (task stacks and registers) will be dumped either to Flash or UART, for later analysis.
 
-.. only:: esp32
-
-    - If :ref:`CONFIG_ESP_PANIC_HANDLER_IRAM` is disabled (disabled by default), the panic handler code is placed in flash memory not IRAM. This means that if ESP-IDF crashes while flash cache is disabled, the panic handler will automatically re-enable flash cache before running GDB Stub or Core Dump. This adds some minor risk, if the flash cache status is also corrupted during the crash.
+- If :ref:`CONFIG_ESP_PANIC_HANDLER_IRAM` is disabled (disabled by default), the panic handler code is placed in flash memory not IRAM. This means that if ESP-IDF crashes while flash cache is disabled, the panic handler will automatically re-enable flash cache before running GDB Stub or Core Dump. This adds some minor risk, if the flash cache status is also corrupted during the crash.
 
   If this option is enabled, the panic handler code is placed in IRAM. This allows the panic handler to run without needing to re-enable cache first. This may be necessary to debug some complex issues with crashes while flash cache is disabled (for example, when writing to SPI flash).
 

tools/test_apps/system/build_test/sdkconfig.ci.panic_handler_iram

@@ -0,0 +1 @@
+CONFIG_ESP_PANIC_HANDLER_IRAM=y