flash.sh failed when setup qemu-neo1973

Gordon Syme gordon at twiceasgood.net
Wed Oct 31 09:57:19 CET 2007


孙廉焘 wrote:
> Hi all,
> 
> I have a problem, when I setup the qemu-neo1973 envirement followed by
> http://wiki.openmoko.org/wiki/Qemu.
> 
> I have done these steps:
> sudo apt-get install netpbm lynx
> svn checkout https://svn.openmoko.org/trunk/src/host/qemu-neo1973
> cd qemu-neo1973
>  ./configure --target-list=arm-softmmu --cc=/home/sunlt/gcc33
>  make
> openmoko/download.sh
> openmoko/flash.sh
> 
> After openmoko/flash.sh, the output information is listed briefly as
> following(full version is an attachment):
> 
> ls: /root/openmoko/qemu-neo1973/openmoko/uImage-2.6.*-neo1973.bin: No
> such file or directory
> U-Boot 1.2.0-moko9_r0 (Aug 19 2007 - 19:17:12)
>  DRAM:  128 MB
>  NAND:  Bad block table not found for chip 0
>  Bad block table not found for chip 0
>  64 MiB
>  *** Warning - bad CRC or NAND, using default environment
> Creating BBT. Please wait ...Bad block table not found for chip 0
> Bad block table not found for chip 0
> Bad block table written to 0x03ffc000, version 0x01
> Bad block table written to 0x03ff8000, version 0x01
> 
> GTA01Bv4 # setenv bootcmd 'setenv bootargs ${bootargs_base}
> ${mtdparts}; bootm 0x31000000'
> GTA01Bv4 # setenv menu_1 'Set console to USB: setenv stdin usbtty;
> setenv stdout usbtty; setenv stderr usbtty'
> GTA01Bv4 # setenv menu_2 'Set console to serial: setenv stdin serial;
> setenv stdout serial; setenv stderr serial'
> GTA01Bv4 # setenv menu_3 'Power off: neo1973 power-off'
> GTA01Bv4 # setenv splashimage 'nand read.e 0x36000000 splash 0x5000;
> unzip 0x36000000 0x33d00000 0x96000'
> GTA01Bv4 # setenv mtdids nand0=neo1973-nand
> GTA01Bv4 # setenv mtdparts
> mtdparts=neo1973-nand:0x00050000(u-boot),0x00004000(u-boot_env),0x00208000(kernel),0x00010000(splash),0x039a4000(rootfs)
> GTA01Bv4 # #dynpart
> Unknown command '#dynpart' - try 'help'
> GTA01Bv4 # nand write.e 0x31000000 u-boot 0x33660
> 
> NAND write: device 0 offset 0x0, size 0x33660
> 
> Writing data at 0x33600 -- 100% complete.
> 
> Erasing Nand...Writing to Nand... done
> GTA01Bv4 # neo1973 power-off
> poweroff
> pcf_write: Power-off requested.
> openmoko/flash.sh: line 114: 30382 已终止               ( sleep $2; kill
> $pid; sleep 1; kill -KILL $pid )  (wd: /root/openmoko/qemu-neo1973)
> Please wait, programming the NAND flash...
> neo_gsm_switch: GSM disabled.
> 
> pcf_write: Power-off requested.
> Please wait, programming the NAND flash...
> sleep: invalid time interval 'nand'
> sleep: invalid time interval 'write.e'
> sleep: invalid time interval 'kernel'
> For more information, try 'sleep --help'
> openmoko/flash.sh: line 88: 30385 terminaled               ( sleep $2;
> kill $pid; sleep 1; kill -KILL $pid )
> openmoko/flash.sh: line 88: 30387 terminaled               $qemu
> -mtdblock "$script_dir/$flash_base" -kernel "$script_dir/$1" -serial
> stdio -nographic -usb -monitor null 0<&0
> 
> U-boot failed to finish writing in nand write.e 0x31000000 kernel
> 0x1000 seconds, giving up.
> 
> Who can help me?
> Thank you very much!

cd to your OpenMoko root directory and then cd to images/openmoko. There should
be at least three files in there:
[*] A .rootfs file which is the root filesystem for the device
[*] A u-boot file, this is the bootloader
[*] A uImage file, this is the kernel

It is very likely that the flashing program couldn't find the kernel. The
pattern that the flashing program uses to recognise kernels is kept in
build/qemu/openmoko/env in the "kernel_wildcard" variable.

Make sure that the uImage file in images/openmoko matches this pattern and you
should be OK.

-Gordon

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : http://lists.openmoko.org/pipermail/community/attachments/20071031/b23138bb/attachment.pgp 


More information about the community mailing list