This was the case with two different u-boot flashes, the one that came with the moko and a more recent build. It's unlikely the problem. The cord is also likely fine, as I can successfully flash other images. Lastly, I did try erase the rootfs first with nand erase clean rootfs from the serial line.
I'm running Gutsy Gibbon, which has some known USB problems. I'm going to try to flash the phone on a comrade's computer today, that's my guess as to the error. I'll update this as to how it goes. On 10/30/07, Nick Guenther <[EMAIL PROTECTED]> wrote: > > On 10/29/07, Kurtis Heimerl <[EMAIL PROTECTED]> wrote: > > of course! > > > > [EMAIL PROTECTED]:~/moko/build/tmp/deploy/glibc/images/neo1973$ > > sudo ./dfu-util -a rootfs -R -D > > openmoko-devel-image-fic-gta01.jffs2 > > dfu-util - (C) 2007 by OpenMoko Inc. > > This program is Free Software and has ABSOLUTELY NO WARRANTY > > > > Opening USB Device 0x0000:0x0000... > > Found Runtime: [0x1457:0x5119] devnum=19, cfg=0, intf=0, alt=5, > > name="rootfs" > > Claiming USB DFU Interface... > > Setting Alternate Setting ... > > Determining device status: state = dfuERROR, status = 14 > > dfuERROR, clearing status > > Determining device status: state = dfuIDLE, status = 0 > > dfuIDLE, continuing > > Transfer Size = 0x1000 > > bytes_per_hash=407961 > > Starting download: > > [##################################################dfu_download > > error -110 > > ] finished! > > unable to read DFU status > > [EMAIL PROTECTED]:~/moko/build/tmp/deploy/glibc/images/neo1973$ > > This is worrying. Maybe your uboot (which handles the flashing) is > corrupted or just happens to be broken? Maybe it's the USB hardware > you're using? Frayed cord? Have you tried to flash a bunch of times? > Have you "nand erase rootfs"'d? > > -Nick > >
