summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2014-01-29 09:08:58 -0600
committerGregory Nutt <gnutt@nuttx.org>2014-01-29 09:08:58 -0600
commit74fcb4526e44b34532a68f383db97d2c29194215 (patch)
tree3901e08acaa179b5b4284ca2303fc1d80d6186ca
parent626d10555f61a24f5d3bf7e84dcf70579cb7ce53 (diff)
downloadnuttx-74fcb4526e44b34532a68f383db97d2c29194215.tar.gz
nuttx-74fcb4526e44b34532a68f383db97d2c29194215.tar.bz2
nuttx-74fcb4526e44b34532a68f383db97d2c29194215.zip
Update dependencies for CONFIG_BOOT_SDRAM_DATA. This should not be available if the system boots from SDRAM (via a bootloader)
-rw-r--r--nuttx/arch/Kconfig16
1 files changed, 11 insertions, 5 deletions
diff --git a/nuttx/arch/Kconfig b/nuttx/arch/Kconfig
index 983950d64..643283403 100644
--- a/nuttx/arch/Kconfig
+++ b/nuttx/arch/Kconfig
@@ -441,11 +441,17 @@ config ARCH_HAVE_SDRAM
config BOOT_SDRAM_DATA
bool "Data in SDRAM"
default n
- depends on ARCH_HAVE_SDRAM
+ depends on ARCH_HAVE_SDRAM && !BOOT_RUNFROMSDRAM
---help---
- This selection should be set if data lies in SDRAM (vs. SRAM). In
- that case, the initialization sequence is a little different: SDRAM
- must be configured before before the .data and .bss sections can be
- initialized.
+ This selection should be set if data lies in SDRAM (vs. SRAM) and if
+ SDRAM was not previously initialized by a loader. Obviously, this
+ does not apply if we booting from SDRAM because SDRAM must have been
+ initialized priority to loading NuttX into SDRAM.
+
+ In the case where SDRAM must be initialized by NuttX, the
+ initialization sequence is a little different: Normally, .data and
+ .bss must be initialized before starting the system. But in this
+ case SDRAM must be configured by board-specific logic before the
+ .data and .bss sections can be initialized.
endmenu # Boot Memory Configuration