Other Parts Discussed in Thread: OMAP-L138, OMAPL138
Hello,
I'm starting up development for a OMAP-L138 system. Having good and lots of experience with OpenEmbedded (e.g. on the OMAP3 overo series), I was planning to use OE for that.
So after configuring OE for the "da850-omapl138-evm" machine, I quickly ended up with a built linux-davinci kernel, reportedly "2.6.32+2.6.33-rc4-r50".
I copied the kernel's uImage to the FAT partition of the SD card, which used to contain the "demo" linux image.
Using the following settings which booted the "demo" image, they should work for my kernel too right?
bootargs=console=ttyS2,115200n8 root=/dev/mmcblk0p2 rootfstype=ext3 rootdelay=2
bootcmd=mmc rescan 0 ; fatload mmc 0 c0700000 uImage ; bootm c0700000
Then after booting, I get this:
Booting with TI UBL
Device OPP (300MHz, 1.2V)
U-Boot 2009.11 (Jan 13 2011 - 01:05:37)
I2C: ready
DRAM: 64 MB
MMC: davinci: 0
In: serial
Out: serial
Err: serial
ARM Clock : 300000000 Hz
DDR Clock : 132000000 Hz
Net: Ethernet PHY: GENERIC @ 0x00
Hit any key to stop autoboot: 0
reading uImage
2115688 bytes read
## Booting kernel from Legacy Image at c0700000 ...
Image Name: topic/2.6.32+2.6.33-rc4-r50.2+gi
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2115624 Bytes = 2 MB
Load Address: c0008000
Entry Point: c0008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
After that, all is quiet. I also enabled CONFIG_DEBUG_LL in the kernel config, but still no output whatsoever.
Any hints on how to continue? Maybe another OE branch (currently using org.openembedded.dev)? Is it feasible at all to use OE for this board?
