On 17 August 2012 23:30, Aaron Lindsay <aclindsa@gmail.com> wrote:

Vishal,

Ah, I'm building everything from source. so am just pulling in
whatever u-boot version pinned-manifest.xml points to. I have tried
copying over u-boot.{img|bin} from the boot.tar.bz2 and MLO available
from Linaro's build to the boot.tar.bz2 created when I use the
linaro_android_build_cmds.sh script. This appears to get me past the
device tree message, but unfortunately, never makes it past
"Uncompressing Linux... done, booting the kernel." I suspect this is
due to some communication error between uboot and the kernel, but am
not sure what.

You need to pick the MLO also from the prebuilt boot.tar.bz2 . MLO and uboot together make the pair which works for aosp to boot. I am confused here . If you build from source these prebuilt MLO and uboot are part of the source and they get copied into the boottarball . I am not sure why is it not happening in your build.

Does Linaro's build process do anything else (besides using a
pre-built uboot) differently from what I would get by simply running
linaro_android_build_cmds.sh?

linaro_android_build_cmds.sh build should be able to build the exact images as generated on android build . Let me know if the right uboot binary is not copied when using linaro_android_build_cmds.sh .

Thanks for the help!

-Aaron

On Fri, Aug 17, 2012 at 3:09 AM, Vishal Bhoj <vishal.bhoj@linaro.org> wrote:
> Hi Aaron,
>
> I have tested build 184 and it boots up fine . It appears that you have
> picked the wrong bootloader while creating the image . The logs shows uboot
> version as "U-Boot 2012.04.01 (Aug 15 2012 - 16:44:44)" which surely won't
> work with AOSP kernel . We use a prebuilt uboot in these aosp builds which
> are picked from TI's repositories . Please use the tarballs and the
> linaro-android-media-create to create the images and let us know if you
> still run into the issue.
>
> Regards,
> Vishal
>
>
> On 17 August 2012 00:52, Aaron Lindsay <aclindsa@gmail.com> wrote:
>>
>> I am attempting to build Linaro's latest stable AOSP build for the
>> pandaboard
>> (https://android-build.linaro.org/builds/~linaro-android/panda-master-gcc44-aosp-stable-blob/#build=184).
>> It appears to build fine, but unfortunately when I load it on the SD
>> card and attempt to boot the pandaboard, I get the message:
>>
>> "ERROR: Did not find a cmdline Flattened Device Tree
>> Could not find a valid device tree"
>>
>> I've attached the full log up through this error. I have followed the
>> directions from the page I linked above. Please let me know if you
>> need more information from me about my build environment, other logs,
>> etc. and I'll be happy to supply them.
>>
>> Thanks!
>>
>> -Aaron Lindsay