[..snip..]
> % mkfs.jffs2 --little-endian --no-cleanmarkers --pad 2048 --pagesize 2048
> --eraseblock 131072 -d /tmp/tmp.h9dKGpcNFw -D root.devices -o root.jffs2
>
> >> nand write.i ${loadaddr} 0x00c00000 0x2000000
> >> nand write.i ${loadaddr} 0x04200000 0x2000000
> >
> > [Ghorai] why you writing in two places?
>
> Redundant images.
>
> >> Following that, the board is updated, from Linux, using 'flash_eraseall
> -
> >> q'
> >> and 'nandwrite -p -q' on all partitions, except that containing MLO.
> > [Ghorai]
> >
> > 1. can you send the exact comment you used to write in nand? Which
> partition?
>
> flash_eraseall -q /dev/mtd7
> nandwrite -p -q /dev/mtd7 root.jffs2
> flash_eraseal -q /dev/mtd9
> nandwrite -p -q /dev/mtd9 root.jffs2
>
> > 2. What is the last kernel you used and was working perfectly?
> v2.6.32_OMAPPSP_03.00.01.06.patch1
[Ghorai] I followed the steps you mentioned. Also I used the following command
to mount the jffs2 FS and working fine.
mount -t jffs2 /dev/mtdblock3 /mnt/nand
I have tested in zoom3 -
NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron NAND 512MiB 1,8V
16-bit).
And using the latest kernel -
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Linux version 2.6.37-rc3-00102-gea49b16 (a0393...@omapldc12)
(gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #20 SMP Wed Nov 24 17:27:21
IST 2010
Would you please share your latest log?
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
