So I've been having some difficulty following the instructions to build and boot an OMAP linaro image for qemu here: https://wiki.linaro.org/Source/ImageInstallation

Following the instructions, I can build the image, and boot it. Uboot works fine, and the kernel begins to load, however it seems to hang after the following on the serial line:

[ 3.416564] OMAP DISPC rev 3.0 [ 3.417175] OMAP VENC rev 2 [ 3.768157] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled [ 3.794738] serial8250.0: ttyS0 at MMIO 0x4806a000 (irq = 72) is a 16550A [ 3.827117] serial8250.1: ttyS1 at MMIO 0x4806c000 (irq = 73) is a 16550A [ 3.844787] serial8250.2: ttyS2 at MMIO 0x49020000 (irq = 74) is a 16550A [ 3.851776] console [ttyS2] enabled, bootconsole disabled [ 3.851776] console [ttyS2] enabled, bootconsole disabled [ 3.984436] brd: module loaded [ 4.059204] loop: module loaded [ 4.086456] omap2-nand driver initializing

At first I suspected the console was just sitting on ttyS2, and the serial port in qemu was ttyS0. So I mucked around with qemu's serial port settings, but no-matter the config, I didn't see any other output.

I then tried to force uboot to set the console line to ttyS0, but the boot.scr script uboot loads seems to overwrite any environment values (trying to write my own boot line from the pre-boot.scr environment values didn't boot either).

So I finally just hacked the linaro-media-create script to use ttyS0 instead of ttyS2, and there I found the console output stopped immediately after the "console [ttyS0] enabled, bootconsole disabled" message. So that doesn't seem to be the issue.

So now I'm suspecting I'm hitting some other hang. Does anyone else have a working qemu omap environment that they are using to test the linaro images? Are there any extra steps that need to be documented?

thanks -john