[Bug 937] Qemu doens't want to flash images

bugzilla-daemon at bugzilla.openmoko.org bugzilla-daemon at bugzilla.openmoko.org
Sat Oct 27 19:20:02 CEST 2007


http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=937





------- Additional Comments From m.bitter at gmx.net  2007-10-27 19:20 -------
I've had the same problem on debian.
After correcting the path in MokoMakefile (line 421) 
to "../tmp/deploy/glibc/images/neo1973" the fash.sh find the correct images 
from make openmoko-devel-image but after that I have the same problem as 
reportet in Bug 937:

my output from make flash-qemu-local is now:

( cd build/qemu && openmoko/flash.sh ../tmp/deploy/glibc/images/neo1973 )
/usr/bin/pngtopnm
/usr/bin/ppmtorgb3
make[1]: Entering directory `/home/openmoko/build/qemu/openmoko'
make[1]: »splash.gz« ist bereits aktualisiert.
make[1]: Leaving directory `/home/openmoko/build/qemu/openmoko'
ls: /home/openmoko/build/tmp/deploy/glibc/images/neo1973/uImage-2.6.*-fic-gta01.bin: 
Datei oder Verzeichnis nicht gefunden
basename: fehlender Operand
„basename --help“ gibt weitere Informationen.
Using '' as the kernel image.
Using 'OpenMoko-openmoko-devel-image-glibc-ipk-P1-Snapshot-20071027-fic-gta01.rootfs.jffs2' 
as the root filesystem image.
Using 'u-boot-gta01bv4-1.2.0+gitf34024d4a328e6edd906456da98d2c537155c4f7+svn2943-r1.bin' 
as bootloader.
make[1]: Entering directory `/home/openmoko/build/qemu/openmoko'
# Making an empty/erased flash image.  Need a correct echo behavior.
echo -en \\0377\\0377\\0377\\0377\\0377\\0377\\0377\\0377 > .8b
cat .8b .8b > .16b # OOB is 16 bytes
cat .16b .16b .16b .16b .16b .16b .16b .16b > .512b
cat .16b .16b .16b .16b .16b .16b .16b .16b >> .512b
cat .16b .16b .16b .16b .16b .16b .16b .16b >> .512b
cat .16b .16b .16b .16b .16b .16b .16b .16b >> .512b
cat .512b .16b > .sec # A sector is 512 bytes of data + OOB
cat .sec .sec .sec .sec .sec .sec .sec .sec > .8sec
cat .8sec .8sec .8sec .8sec .8sec .8sec .8sec .8sec > .64sec
cat .64sec .64sec .64sec .64sec .64sec .64sec .64sec .64sec > .512sec
cat .512sec .512sec .512sec .512sec > .2ksec
cat .2ksec .2ksec .2ksec .2ksec .2ksec .2ksec .2ksec .2ksec > .16ksec
# Neo NAND is 128k sectors big
cat .16ksec .16ksec .16ksec .16ksec .16ksec .16ksec .16ksec .16ksec > 
openmoko-flash.base
rm -rf .8b .16b .512b .sec .8sec .64sec .512sec .2ksec .16ksec
make[1]: Leaving directory `/home/openmoko/build/qemu/openmoko'
Please wait, programming the NAND flash...
300
neo_gsm_switch: GSM disabled.


U-Boot 1.3.0-rc11.2.0+gitf34024d4a328e6edd906456da98d2c537155c4f7+svn2943 (Oct 
27 2007 - 14:50:08)

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

Video: 640x480x8 31kHz 59Hz
USB:   S3C2410 USB Deviced
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
mtdparts variable not set, see 'help mtdparts'
In:    serial
Out:   serial
Err:   serial
pcf_write: charging in Qualification Mode.
pcf_write: charge voltage 4.20V.
neo_lcd_rst_switch: LCD reset.
jbt6k74_command: Display on.
neo_vib_switch: Buzz, buzz.
neo_vib_switch: Vibrator stopped.
neo_bl_switch: LCD Backlight now on.
GTA01Bv4 #
GTA01Bv4 #
GTA01Bv4 # setenv dontask y
GTA01Bv4 # nand createbbt
Create BBT and erase everything ? <y/N>
Skipping bad block at  0x03ff0000
Skipping bad block at  0x03ff4000
Skipping bad block at  0x03ff8000
Skipping bad block at  0x03ffc000

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 'openmoko/flash.sh: line 89: 15285 Beendet                 
$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 300 seconds, giving up.

make: *** [flash-qemu-local] Fehler 255




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the buglog mailing list