Skip to contentSkip to conversation

ARM: OMAP5: Set fdt_high to enable booting with Device tree

PATCH New Sricharan R 2 participants 3 messages Mar 21, 2013 – Mar 22, 2013

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 ARM: OMAP5: Set fdt_high to enable booting with Device tree

While booting with dtblob, if fdt_high is not set to 0xffffffff, the dt blob is relocated to a higher address, which the kernel is not able to use without HIGHMEM.

So set it to 0xffffffff to avoid the issue.

---
 include/configs/omap5_common.h |    1 +
 1 file changed, 1 insertion(+)
include/configs/omap5_common.h +1 -0
index af97564..f0416df 100644
@@ -143,6 +143,7 @@
 #define CONFIG_EXTRA_ENV_SETTINGS \
 	"loadaddr=0x82000000\0" \
 	"console=ttyO2,115200n8\0" \
+	"fdt_high=0xffffffff\0" \
 	"usbtty=cdc_acm\0" \
 	"vram=16M\0" \
 	"mmcdev=0\0" \
Signature · 1 line
1.7.9.5
#1 lore raw

PATCH 1/1 ARM: OMAP5: Set fdt_high to enable booting with Device tree

Quoted 7 lines · Sricharan R

While booting with dtblob, if fdt_high is not set to 0xffffffff, the dt blob is relocated to a higher address, which the kernel is not able to use without HIGHMEM.

So set it to 0xffffffff to avoid the issue.

That's fine, but while we're making this DT-happy, lets add fdtaddr to the env (so there's a good default and safe address to load the DT to) and make the default boot commands load and pass the DT. That means that we need to make sure that you probably need to enable CONFIG_ENV_VARS_UBOOT_CONFIG and perhaps CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG (and see board/ti/am335x/board.c for an example) so that we pick out the right DT file to load.

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130321/56afc72d/attachment.pgp>
#2 lore raw

PATCH 1/1 ARM: OMAP5: Set fdt_high to enable booting with Device tree

Hi Tom,

Quoted 10 lines · Tom Rini
Quoted 7 lines · Sricharan R

While booting with dtblob, if fdt_high is not set to 0xffffffff, the dt blob is relocated to a higher address, which the kernel is not able to use without HIGHMEM.

So set it to 0xffffffff to avoid the issue.

Quoted 8 lines

That's fine, but while we're making this DT-happy, lets add fdtaddr to the env (so there's a good default and safe address to load the DT to) and make the default boot commands load and pass the DT. That means that we need to make sure that you probably need to enable CONFIG_ENV_VARS_UBOOT_CONFIG and perhaps CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG (and see board/ti/am335x/board.c for an example) so that we pick out the right DT file to load.

Thanks for the inputs. So i will have to check if we have eeprom as in your case for runtime configuration.Even otherwise the default should be changed as you said. Plus will also change default as zImage. will post shortly.

Regards,
Sricharan