anyone got embinux's android donut build running?

(i've already asked about this on embinux's mailing list, but there
seems to be a weird time lag with their list in that you won't see
anything for a while, followed by a flurry of posts. in any event,
i'm kind of pressed for time, so i thought i'd harass this list as

  a couple weeks ago, embinux released the tarball
ANDROID_DONUT_BEAGLE_08Oct2009.tar.bz2, so this morning, i grabbed a
spare SD card, formatted it, and populated it appropriately.

  i then followed the instructions in the README file and configured
u-boot thusly:

OMAP3 #setenv bootargs console=ttyS2,115200n8 noinitrd
root=/dev/mmcblk0p2 video=omapfb.mode=dvi:1280x720MR-24@50 init=/init
rootfstype=ext3 rw rootdelay=1 nohz=off androidboot.console=ttyS2
OMAP3 # mmc init
OMAP3 # fatload mmc 0 0x80300000 uImage
OMAP3 # bootm 0x80300000

  at which point, the boot process took off, looked good, until:

... snip ...

Waiting 1sec before mounting root device...
mmc0: new high speed SDHC card at address 1234
mmcblk0: mmc0:1234 SA04G 3.68 GiB
mmcblk0: p1 p2
kjournald starting. Commit interval 5 seconds
EXT3 FS on mmcblk0p2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
VFS: Mounted root (ext3 filesystem) on device 179:2.
Freeing init memory: 144K
Warning: unable to open an initial console.
init: cannot open '/initlogo.rle'
init: cannot find '/system/bin/playmp3', disabling 'bootsound'
# warning: `rild' uses 32-bit capabilities (legacy support in use)
enabling adb

at which point the BB is simply hung. thoughts? i'm still new to
android, so i'm not sure if the console settings are correct, since
that's what claims to be the problem.

  any advice?


Your Bootup Process looks pretty good.
After that you should be able to use the console.
How do you mean the BB "hung"? Is the Display locked?

You should be able to type a command after adb_open. Try
# ps
for instance


Also, watch out for the bootargs: the supplied example is for 1280x1024@50 - you most likely need to change this for your NA monitor.

I re-built from scratch and have it working. Watch out for the script since it sets the defconfig every time, overwriting any config changes you may have made (for example, to get your usb ethernet dongle working). Nothing magical about building the kernel, so you might just avoid the script, although it does document the particular options/steps.


whoops, you're right, it was a minicom glitch. i tried exactly the
same thing again and got to a boot prompt. thanks, sorry for the
interruption, carry on.