[meta-ti] BeagleBone Black fails to boot with u-boot 2014.07, linux-yocto 3.14.5

[Maciej Borzecki]

Hi all,

I'm having trouble booting BBB with current meta-ti 
(f7b1140774e6c8c8aecde41388d40d9d407df6ff). The problem looks similar to this 
bug report:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=6165

Console output is as follows:
Booting from mmc ...
## Booting kernel from Legacy Image at 80007fc0 ...
   Image Name:   Linux-3.14.5-yocto-standard
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5098048 Bytes = 4.9 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 80f80000
   Booting using the fdt blob at 0x80f80000
   XIP Kernel Image ... OK
OK
   Using Device Tree in place at 80f80000, end 80f8a207

Starting kernel ...


The original issue with kernel overlapping fdt was fixed with this patch to 
OE-core: 
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=2cae5f78ad2982c7ca0c22c085b71a1d2184a1b0 
However, current meta-ti contains u-boot in version 2014.07, overriding 
2013.07 from poky master. I'm assuming that the patch eventually made it into 
denx tree.

Another problem is that uImage contains the following info:
Image Name:   Linux-3.14.5-yocto-standard
Created:      Mon Aug 11 16:59:42 2014
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:    5098048 Bytes = 4978.56 kB = 4.86 MB
Load Address: 80008000
Entry Point:  80008000

I'm not sure what is the order in which the addresses are applied. Is it 
kernel -> default env -> uEnv.txt?

Adding uEnv.txt with these contents fixes the problem:
loadaddr=0x82000000
kernel_addr_r=0x82000000
fdtaddr=0x88000000
fdt_addr_r=0x88000000
rdaddr=0x88080000
ramdisk_addr_r=0x88080000
bootm_size=0x10000000

Please advise how to fix it without falling back to uEnv.

-- 
Maciej Borzęcki 
Senior Software Engineer Open-RnD Sp. z o.o. 
www.open-rnd.pl, Facebook, Twitter 
mobile: +48 telefon, fax: +48 42 657 9079 

Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub 
poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do 
których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo 
zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku 
uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie 
nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. 

This message, including any attachments hereto, may contain privileged or 
confidential information and is sent solely for the attention and use of the 
intended addressee(s). If you are not an intended addressee, you may neither 
use this message nor copy or deliver it to anyone. In such case, you should 
immediately destroy this message and kindly notify the sender by reply email. 
Thank you.