From: Victhor <vic...@gm...> - 2011-04-14 09:31:34
|
No, I was referring to the kernel image on /dev/mtdblock3(I think). Does the timestamp issue still apply? > Actually I'm told this won't work since the timestamps will be > different. Not sure how else you might verify your image. > > -- > Neil > > On 11-04-11 03:44 PM, Neil MacMunn wrote: > > Once you have extracted the image to /media/mtdblock4 you can try to > > compress the filesystem again and compare the md5sum to that of the > > original archive. > > > > Something like this: > > > > # tar -cjf /media/mtdblock4/* newarchive.tar.bz2 > > # md5sum newarchive.tar.bz2> newmd5sum.txt > > > > -- > > Neil > > > > On 11-04-06 03:13 PM, Victhor wrote: > >> Thanks, that alone did not work, I had to run mkfs.jffs2 > >> -o /dev/mtdblock4 after it(otherwise it would not mount, same error as > >> the one on the original message), then mount the device. Unfortunately I > >> get loads of ECC errors upon mount, and during the erasure process I > >> noticed there were 3 bad blocks. I don't know if these appeared during > >> my (little) usage of the device or if they are marked by the factory. > >> Also, if I try to boot any kernel image on it, I get this: > >> > >> NAND read: device 0 offset 0x280000, size 0x400000 > >> NAND read from offset 280000 failed -74 > >> 4194304 bytes read: ERROR > >> ## Booting kernel from Legacy Image at 82000000 ... > >> Image Name: Angstrom/2.6.34/overo > >> Image Type: ARM Linux Kernel Image (uncompressed) > >> Data Size: 2929436 Bytes = 2.8 MiB > >> Load Address: 80008000 > >> Entry Point: 80008000 > >> Verifying Checksum ... Bad Data CRC > >> ERROR: can't get kernel image! > >> > >> The same image works fine on a microSD. I don't know how to obtain the > >> image back from the NAND to check the md5(to see if it's ok), though. > >>> You might have to use the -j option with flash_eraseall. This works for me. > >>> > >>> # umount /dev/mtdblock4 > >>> # flash_eraseall -j /dev/mtd4 > >>> # mkdir -p /media/mtdblock4 > >>> # mount -t jffs2 /dev/mtdblock4 /media/mtdblock4 > >>> # cd /media/mtdblock4 > >>> # tar xjf rootfs.tar.bz2 > >>> > >>> > >>> -- > >>> Neil > >>> > >>> On 11-04-05 01:50 PM, Victhor wrote: > >>>> I finally managed to reflash my device after a accidental NAND wipe, but > >>>> I can't seem to be able to write any rootfs to it, > >>>> because /dev/mtdblock4 will not mount: > >>>> > >>>> root@overo:/media/mmcblk0p1# mount -t > >>>> jffs2 /dev/mtdblock4 /media/mtdblock4/ > >>>> Cowardly refusing to erase blocks on filesystem with no valid JFFS2 > >>>> nodes > >>>> empty_blocks 1993, bad_blocks 0, c->nr_blocks 1996 > >>>> mount: /dev/mtdblock4: can't read superblock > >>>> > >>>> I tried to use flash_eraseall /dev/mtd4 but it didn't help... > >>>> > >>>> > >>>> ------------------------------------------------------------------------------ > >>>> Xperia(TM) PLAY > >>>> It's a major breakthrough. An authentic gaming > >>>> smartphone on the nation's most reliable network. > >>>> And it wants your games. > >>>> http://p.sf.net/sfu/verizon-sfdev > >>>> _______________________________________________ > >>>> gumstix-users mailing list > >>>> gum...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >>> > >>> > >>> ------------------------------------------------------------------------------ > >>> Xperia(TM) PLAY > >>> It's a major breakthrough. An authentic gaming > >>> smartphone on the nation's most reliable network. > >>> And it wants your games. > >>> http://p.sf.net/sfu/verizon-sfdev > >>> _______________________________________________ > >>> gumstix-users mailing list > >>> gum...@li... > >>> https://lists.sourceforge.net/lists/listinfo/gumstix-users > >> > >> > >> > >> ------------------------------------------------------------------------------ > >> Xperia(TM) PLAY > >> It's a major breakthrough. An authentic gaming > >> smartphone on the nation's most reliable network. > >> And it wants your games. > >> http://p.sf.net/sfu/verizon-sfdev > >> _______________________________________________ > >> gumstix-users mailing list > >> gum...@li... > >> https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > > > ------------------------------------------------------------------------------ > > Forrester Wave Report - Recovery time is now measured in hours and minutes > > not days. Key insights are discussed in the 2010 Forrester Wave Report as > > part of an in-depth evaluation of disaster recovery service providers. > > Forrester found the best-in-class provider in terms of services and vision. > > Read this report now! http://p.sf.net/sfu/ibm-webcastpromo > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > ------------------------------------------------------------------------------ > Forrester Wave Report - Recovery time is now measured in hours and minutes > not days. Key insights are discussed in the 2010 Forrester Wave Report as > part of an in-depth evaluation of disaster recovery service providers. > Forrester found the best-in-class provider in terms of services and vision. > Read this report now! http://p.sf.net/sfu/ibm-webcastpromo > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |