From 19f3523499f3d74a3cbb90ae181eb3b93c18a7f6 Mon Sep 17 00:00:00 2001 From: Abdelatif Guettouche Date: Tue, 6 Apr 2021 23:22:42 +0200 Subject: [PATCH] boards/xtensa/esp32: Update Kconfig helps when it comes to running from IRAM. Signed-off-by: Abdelatif Guettouche --- boards/xtensa/esp32/esp32-devkitc/Kconfig | 18 ++---------------- boards/xtensa/esp32/esp32-ethernet-kit/Kconfig | 18 ++---------------- boards/xtensa/esp32/esp32-wrover-kit/Kconfig | 18 ++---------------- 3 files changed, 6 insertions(+), 48 deletions(-) diff --git a/boards/xtensa/esp32/esp32-devkitc/Kconfig b/boards/xtensa/esp32/esp32-devkitc/Kconfig index e93d362c45..e537922f1f 100644 --- a/boards/xtensa/esp32/esp32-devkitc/Kconfig +++ b/boards/xtensa/esp32/esp32-devkitc/Kconfig @@ -21,22 +21,8 @@ config ESP32_DEVKITC_RUN_IRAM bool "Run from IRAM" default n ---help--- - The default configuration is set up run from IRAM. However, the - current (2016-11-14) OpenOCD for ESP32 does not support writing to - FLASH. This option sets up the linker scripts to support execution - from IRAM. In this case, OpenOCD can be used to load directly into - IRAM. - - At this stage the nuttx image is small enough to be entirely memory- - resident. Once board support is more mature you can add flash cache - mapping code to run from SPI flash after initial boot. There are at - least two possible approaches you could take: You can add the flash - cache mapping code into nuttx directly, so it is self-contained - - early nuttx initialization runs from IRAM and enables flash cache, - and then off you go. Or you can use the esp-idf software bootloader - and partition table scheme and have nuttx be an esp-idf "app" which - allows interoperability with the esp-idf system but makes you - reliant on the esp-idf design for these parts. Both are possible. + This loads all of NuttX inside IRAM. Used to test somewhat small + images that can fit entirely in IRAM. source boards/xtensa/esp32/common/Kconfig diff --git a/boards/xtensa/esp32/esp32-ethernet-kit/Kconfig b/boards/xtensa/esp32/esp32-ethernet-kit/Kconfig index 6b4f996cfd..14b948f51c 100644 --- a/boards/xtensa/esp32/esp32-ethernet-kit/Kconfig +++ b/boards/xtensa/esp32/esp32-ethernet-kit/Kconfig @@ -21,22 +21,8 @@ config ESP32_ETHERNETKIT_RUN_IRAM bool "Run from IRAM" default n ---help--- - The default configuration is set up run from IRAM. However, the - current (2016-11-14) OpenOCD for ESP32 does not support writing to - FLASH. This option sets up the linker scripts to support execution - from IRAM. In this case, OpenOCD can be used to load directly into - IRAM. - - At this stage the nuttx image is small enough to be entirely memory- - resident. Once board support is more mature you can add flash cache - mapping code to run from SPI flash after initial boot. There are at - least two possible approaches you could take: You can add the flash - cache mapping code into nuttx directly, so it is self-contained - - early nuttx initialization runs from IRAM and enables flash cache, - and then off you go. Or you can use the esp-idf software bootloader - and partition table scheme and have nuttx be an esp-idf "app" which - allows interoperability with the esp-idf system but makes you - reliant on the esp-idf design for these parts. Both are possible. + This loads all of NuttX inside IRAM. Used to test somewhat small + images that can fit entirely in IRAM. source boards/xtensa/esp32/common/Kconfig diff --git a/boards/xtensa/esp32/esp32-wrover-kit/Kconfig b/boards/xtensa/esp32/esp32-wrover-kit/Kconfig index 6e16fb881a..5e2142dd92 100644 --- a/boards/xtensa/esp32/esp32-wrover-kit/Kconfig +++ b/boards/xtensa/esp32/esp32-wrover-kit/Kconfig @@ -21,22 +21,8 @@ config ESP32_WROVERKIT_RUN_IRAM bool "Run from IRAM" default n ---help--- - The default configuration is set up run from IRAM. However, the - current (2016-11-14) OpenOCD for ESP32 does not support writing to - FLASH. This option sets up the linker scripts to support execution - from IRAM. In this case, OpenOCD can be used to load directly into - IRAM. - - At this stage the nuttx image is small enough to be entirely memory- - resident. Once board support is more mature you can add flash cache - mapping code to run from SPI flash after initial boot. There are at - least two possible approaches you could take: You can add the flash - cache mapping code into nuttx directly, so it is self-contained - - early nuttx initialization runs from IRAM and enables flash cache, - and then off you go. Or you can use the esp-idf software bootloader - and partition table scheme and have nuttx be an esp-idf "app" which - allows interoperability with the esp-idf system but makes you - reliant on the esp-idf design for these parts. Both are possible. + This loads all of NuttX inside IRAM. Used to test somewhat small + images that can fit entirely in IRAM. source boards/xtensa/esp32/common/Kconfig