On Mon, Sep 08, 2008 at 04:54:03PM +0200, Pedro Luis D. L. wrote: > On Mon, 8 Sep 2008 19:51:59 +0530 Navin wrote: > > >Hi all, > > > >I am running u-b00t-1.6.6 on custom at91sam9263 board. > > Are you sure it is u-boot-1.6.6? The latest u-boot in repository is > 1.3.4.
I'm guessing he meant 1.1.6, which is quite old (and apparently old enough to suffer l33tsp34k bitrot). > >Now i am able to boot, jffs2 filesystem with linux-2.6.20 kernel. Especially since he's also using a kernel that is quite old. :-) > >but the procedure i am using to burn is jffs2 is : > > >1)boot the linux kernel with ramdisk > > >2)erase the flash partition using $flasheraseall -j /dev/mtd1 > >3)writing the image using $nandwrite -p /dev/mtd1 rootfs.jffs2 > > > > You should be able to flash the jffs2 file sytem from u-boot. > No need to do it from linux. I think that's the point, that it should work from u-boot but doesn't. There's probably either something wrong with the u-boot NAND driver being used, or the ECC layout doesn't match the kernel's. > >In uboot i did this way: > > > >1) tftp 21100000 rootfs.jffs2 > >2)nand write.jffs2 21100000 0x200000 0x(hex add of displayed by tftp) > > > > Which command is "nand write.jffs2"? It's a perfectly normal u-boot command. > Maybe you're using a version which > is modified by the board supplier. > A "normal" way to flash it would be: > > cp.b 21100000 $(destiny_addr) $(filesize) That's for NOR flash. It does not work for NAND. -Scott _______________________________________________ U-Boot mailing list [email protected] http://lists.denx.de/mailman/listinfo/u-boot
