summaryrefslogtreecommitdiffstats
path: root/board/ti/omap2420h4/config.mk
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 /board/ti/omap2420h4/config.mk
parent335d9394c9d9d5f9bec12428f5cc2b84d092bdb6 (diff)
downloadtalos-obmc-uboot-47f58a7357c27ad10b7853cdd7cd018692bfbae0.tar.gz
talos-obmc-uboot-47f58a7357c27ad10b7853cdd7cd018692bfbae0.zip
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 'board/ti/omap2420h4/config.mk')
-rw-r--r--board/ti/omap2420h4/config.mk4
1 files changed, 2 insertions, 2 deletions
diff --git a/board/ti/omap2420h4/config.mk b/board/ti/omap2420h4/config.mk
index ca5ebdf96a..e5dff69a15 100644
--- a/board/ti/omap2420h4/config.mk
+++ b/board/ti/omap2420h4/config.mk
@@ -14,7 +14,7 @@
# (mem base + reserved)
# For use with external or internal boots.
-CONFIG_SYS_TEXT_BASE = 0x80e80000
+#CONFIG_SYS_TEXT_BASE = 0x80e80000
# Used with full SRAM boot.
# This is either with a GP system or a signed boot image.
@@ -24,5 +24,5 @@ CONFIG_SYS_TEXT_BASE = 0x80e80000
# Handy to get symbols to debug ROM version.
#CONFIG_SYS_TEXT_BASE = 0x0
-#CONFIG_SYS_TEXT_BASE = 0x08000000
+CONFIG_SYS_TEXT_BASE = 0x08000000
#CONFIG_SYS_TEXT_BASE = 0x04000000
OpenPOWER on IntegriCloud