[meta-ti] Fwd: Kernel not found (hangs at boot) -- meta-ti and Pandaboard ES

[Jeremiah Foster]

Hello,

I'm trying to build a system with the meta-ti and meta-ivi layers that runs
on the Pandaboard ES. Below you'll find the output of my current attempts,
which stops when it comes time to boot the kernel;

----

Board: OMAP4 Panda
I2C:   ready
DRAM:  1 GiB
WARNING: Caches not enabled
MMC:   OMAP SD/MMC: 0
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   No ethernet found.
Hit any key to stop autoboot:  0
reading uEnv.txt

** Unable to read "uEnv.txt" from mmc 0:1 **
reading boot.scr

** Unable to read "boot.scr" from mmc 0:1 **
reading uImage

6698608 bytes read
Booting from mmc0 ...
## Booting kernel from Legacy Image at 82000000 ...
   Image Name:   Linux-3.4.22
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    6698544 Bytes = 6.4 MiB
   Load Address: 80008000
   Entry Point:  80008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

----

I wonder if I'm using the right kernel? Is there a different or specific
SHA hash I should use for the Pandaboard ES?

In the above output from my attempted boot, it looks as if I've got my MLO
correct at least since it can find the uImage and seems to attempt to boot
from that, i.e. Linux-3.4.22. So from that output I'm under the impression
that my MMC partition is correctly formatted and that the MLO binary is
functioning correctly, what needs to happen is I need to get a kernel that
boots.

I'll do some research into these issues on the web.

Many thanks for pointers from those on this list with more experience.

Regards,

Jeremiah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-ti/attachments/20130826/950ab72e/attachment.html>