[okl4-developer] okl4 on openmoko under qemu-neo
Ashish Bijlani
ashish.bijlani at gmail.com
Fri Aug 1 12:53:28 EST 2008
Hi,
I've been trying to boot okl4 on openmoko neo1973 qemu-neo based
emulator, but it doesn't work. Nothing appears on the screen.
PATH=/home/ashish/okl4/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/arm-linux/bin/:$PATH
./tools/build.py machine=gta01 project=iguana wombat=true
toolprefix=/home/ashish/okl4/opt/nicta/tools/gcc-3.4.4-glibc-2.3.5/arm-linux/bin/arm-linux-
simulate
This is what I did -
* downloaded qemu-neo from
http://wiki.openmoko.org/wiki/Openmoko_under_QEMU followed the
instructions to build openmoko emulated environment. linux boots fine
in this emulated environment.
* copied "qemu-system-arm" and "openmoko/openmoko-flash.base" under
"/opt/okl/Linux-i386/usr/share/qemu-neo/"
The command that seems to be executing is -
"/opt/okl/Linux-i386/bin/qemu-system-arm -M gta01 -m 130 -mtdblock
/opt/okl/Linux-i386/usr/share/qemu-neo/openmoko-flash.base -serial
stdio -nographic -kernel %s" % (source[0].abspath)
I tried booting okl4/build/images/image.boot directly - doesn't work.
Emulator loads u-boot and then u-boot loads the kernel at 0x30100000 -
fails (Bad Magic Number)
arm-softmmu/qemu-system-arm -M gta01 -m 130 -mtdblock
openmoko/openmoko-flash.image -kernel
/home/ashish/okl4/okl4_2.1/build/images/image.boot -usb -show-cursor
On the mailing list archive I saw this post
http://lists.okl4.org/pipermail/developer/2008-April/000917.html and
tired changing the load addr to 0x31000000 - doesn't work - u-boot
loads okl4, but fails with Bad Magic Number again.
I tried booting the binary image (invoking objcopy) as well since
u-boot boots linux's binary bootable image on qemu-neo, but it fails
as well with Bad Magic Number.
Am I missing something? Please help.
Also, in the code base I didn't see any server/driver dirs for flash
and networking for openmoko/gta01 so just curious to know how okl4
virtualizes flash/network for linux based virtual machines running on
top of okl4?
Thanks,
Ashish
More information about the Developer
mailing list