[meta-ti] booting 2.6.32 kernel and rootfs

[Robert Nelson]

On Fri, Jul 5, 2013 at 11:16 PM, Sudhangathan B S
<sudhangathan at gmail.com> wrote:
> On my way to integrate Leopard imaging camera drivers into the beagle board
> image, I successfully built a minimal image with necessary camera drivers in
> the image, this is all after I integrated meta-ti layer with yocto.
> I finally put the files in the card and powered up the beagle board.
>
> This is what i'm getting..
>
> U-Boot SPL 2011.09-01172-gfdbe8b9-dirty (Jul 05 2013 - 20:38:26)
> Texas Instruments Revision detection unimplemented
> OMAP SD/MMC: 0
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2011.09-01172-gfdbe8b9-dirty (Jul 05 2013 - 20:38:26)
>
> OMAP36XX/37XX-GP ES1.2, CPU-OPP2, L3-165MHz, Max CPU Clock 1 Ghz
> OMAP3 Beagle board + LPDDR/NAND
> I2C:   ready
> DRAM:  512 MiB
> WARNING: Caches not enabled
> NAND:  0 MiB
> MMC:   OMAP SD/MMC: 0
> *** Warning - readenv() failed, using default environment
>
> In:    serial
> Out:   serial
> Err:   serial
> Beagle xM Rev C
> No EEPROM on expansion board
> No EEPROM on expansion board
> Die ID #689000029ff80000016842c81202f014
> Net:   Net Initialization Skipped
> No ethernet found.
> Hit any key to stop autoboot:  0
> The user button is currently NOT pressed.
> SD/MMC found on device 0
> reading uEnv.txt
>
> ** Unable to read "uEnv.txt" from mmc 0:1 **
> Loading file "/boot/uImage" from mmc device 0:2 (xxa2)
> 3148568 bytes read
> Booting from mmc ...
> ## Booting kernel from Legacy Image at 80200000 ...
>    Image Name:   Linux-2.6.32
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    3148504 Bytes = 3 MiB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
>
> Starting kernel ...
>
> Uncompressing
> Linux............................................................................................................................................................................................................
> done, booting the kernel.
>
> AND NOTHING AFTER THIS... Any clue how to proceed..?

Back in the 2.6.32 days, the "omap" serial driver did not exist.. So
if your still setting up console as /dev/ttyO2 change it to
/dev/ttyS2..

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/