summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorHunter, Jon <jon-hunter@ti.com>2013-04-03 09:35:34 +0000
committerTom Rini <trini@ti.com>2013-04-08 11:29:05 -0400
commit47f58a7357c27ad10b7853cdd7cd018692bfbae0 (patch)
tree50e4609b91a7f22cad270d51eced7d47375e212a /include
parent335d9394c9d9d5f9bec12428f5cc2b84d092bdb6 (diff)
downloadu-boot-imx-47f58a7357c27ad10b7853cdd7cd018692bfbae0.zip
u-boot-imx-47f58a7357c27ad10b7853cdd7cd018692bfbae0.tar.gz
u-boot-imx-47f58a7357c27ad10b7853cdd7cd018692bfbae0.tar.bz2
omap2420-h4: Fix booting from NOR flash
The omap2420-h4 board is using a RAM based address as the linker location for code. This is causing several problems when attempting to run the latest u-boot code base on this board from flash. Update the default linker location for code to be in NOR flash. Please note that OMAP maps the NOR flash to address 0x08000000 by default and so use this as the default address for the NOR flash. Also remove legacy code that attempts to calculate where in flash the sdata structure, that holds the memory interface configuration data, is located. By changing the default linker location for code to flash this is no longer necessary. Signed-off-by: Jon Hunter <jon-hunter@ti.com>
Diffstat (limited to 'include')
-rw-r--r--include/configs/omap2420h4.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/include/configs/omap2420h4.h b/include/configs/omap2420h4.h
index 1abf259..cb050ab 100644
--- a/include/configs/omap2420h4.h
+++ b/include/configs/omap2420h4.h
@@ -220,7 +220,7 @@
#define CONFIG_ENV_IS_IN_NAND 1
#define CONFIG_ENV_OFFSET 0x80000 /* environment starts here */
#else
-#define CONFIG_ENV_ADDR (CONFIG_SYS_FLASH_BASE + SZ_128K)
+#define CONFIG_ENV_ADDR (CONFIG_SYS_FLASH_BASE + SZ_256K)
#define CONFIG_ENV_IS_IN_FLASH 1
#define CONFIG_ENV_SECT_SIZE PHYS_FLASH_SECT_SIZE
#define CONFIG_ENV_OFFSET ( CONFIG_SYS_MONITOR_BASE + CONFIG_SYS_MONITOR_LEN ) /* Environment after Monitor */