diff --git a/arch/arm/src/sama5/Kconfig b/arch/arm/src/sama5/Kconfig
index 553090cffd..17808ebe6b 100644
--- a/arch/arm/src/sama5/Kconfig
+++ b/arch/arm/src/sama5/Kconfig
@@ -3513,7 +3513,6 @@ config SAMA5_BOOT_ISRAM
 
 config SAMA5_BOOT_SDRAM
 	bool "Running from external SDRAM"
-	depends on SAMA5_DDRCS
 
 config SAMA5_BOOT_CS0FLASH
 	bool "Running in external FLASH CS0"
diff --git a/arch/arm/src/sama5/sam_boot.c b/arch/arm/src/sama5/sam_boot.c
index 8d15c646c1..7ae187b147 100644
--- a/arch/arm/src/sama5/sam_boot.c
+++ b/arch/arm/src/sama5/sam_boot.c
@@ -140,13 +140,14 @@ static const struct section_mapping_s section_mapping[] =
    * I have found that in the test environments that I use, I cannot always
    * be assured of that physical address mapping.
    *
-   * So we do both here.  If we are exectuing from FLASH, then we provide
+   * So we do both here.  If we are executing from FLASH, then we provide
    * the MMU to map the physical address of FLASH to address 0x0000:0000;
    * if we are executing from the internal SRAM, then we trust the bootload
    * to setup the AXI MATRIX mapping.
    */
 
-#if defined(CONFIG_ARCH_LOWVECTORS) && !defined(CONFIG_SAMA5_BOOT_ISRAM)
+#if defined(CONFIG_ARCH_LOWVECTORS) && !defined(CONFIG_SAMA5_BOOT_ISRAM) && \
+   !defined(CONFIG_SAMA5_BOOT_SDRAM)
   { CONFIG_FLASH_VSTART,   0x00000000,
     MMU_ROMFLAGS,          1
   },