sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

boards/xtensa/esp32: Update Kconfig helps when it comes to running from

Browse Source 
IRAM.

Signed-off-by: Abdelatif Guettouche <abdelatif.guettouche@espressif.com>
This commit is contained in:
Abdelatif Guettouche 2021-04-06 23:22:42 +02:00 committed by Xiang Xiao
parent a7f7796db1
commit 19f3523499
3 changed files with 6 additions and 48 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
boards/xtensa/esp32/esp32-devkitc/Kconfig
View File

@ -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

18
boards/xtensa/esp32/esp32-ethernet-kit/Kconfig
View File

@ -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

18
boards/xtensa/esp32/esp32-wrover-kit/Kconfig
View File

@ -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