Flashing FSO-lite to qemu

andrzej zaborowski balrogg at gmail.com
Wed Jul 2 17:45:41 CEST 2008

2008/7/2 David Samblas Martinez <dsamblas at yahoo.es>:
> Hello
> I succefuly build the fso-lite image from MokoMakefile and modifying the build/qemu/openmoko/env I was able(or I think I was able) to flash it to qemu device with the ./openmoko/flash.sh but wen I try to start the qemu with make run-qemu the qemu starting up messages on the simulated neo complains about an VFS:Cannot open root device "mtdblock4" or unknown-block(31,4). Attached is the screen capture (right now I'm working on a remote machine trough vnc)
> Below is a C&P of the env modified , what else you may need to make a diagnose of whats happening?
> -------------env file----------------------------------
> # The scripts will include this on startup to setup variables
> src_dir="`pwd`"
> script_dir_relative=openmoko
> script_dir="$src_dir/$script_dir_relative"
> uboot_symlink="$src_dir/u-boot.bin"
> qemu_relative="arm-softmmu/qemu-system-arm -M gta01 -m 130"
> qemu="$src_dir/$qemu_relative"
> flash_base=openmoko-flash.base
> flash_image=openmoko-flash.image
> make=make
> which gmake && make=gmake
> echo=echo
> which gecho && echo=gecho
> export make echo
> dump_dir="$script_dir/vvfat"
> qemu_monitor="$HOME/.qemu_monitor"
> qemu_cmd () { $script_dir/qemu-cmd.pl "$qemu_monitor" "$*"; }
> kernel_addr=0x30100000
> splash_addr=0x36000000
> splash_size=0x5000
> # We don't want the "-latest" symlinks to match
> kernel_wildcard="uImage-2.6.*-om-gta02.bin"
> rootfs_wildcard="Open?oko-fso-*image*-om-gta02.rootfs.jffs2"

Here you're flashing a GTA02 image. GTA02 has a different NAND sector
size and block size (as seen in the kernel error messages). You need
to try building a gta01 image of FSO - I don't know OE well but it
should only require changing MACHINE.


More information about the openmoko-devel mailing list