Hi Chris,
The first thing to figure out is whether the u-boot util is supposed to
be writing a jffs2 image. It seems like it is.
If this is the case, then it's possible that what u-boot is writing is
not valid (in this situation). I've seen many a problem with jffs2 when
you first mount the image if it's not written exactly right. For
example if the thing that created the jffs2 image does not use the
correct erase block size and/or if the erase block markers are not written.
I suggest verifying this is supposed to be jffs2 and if so asking on a
u-boot list why Linux can't mount this (on an /dev/mtdblock device).
Regards, Stuart
On 01/09/11 21:17, Chris Westervelt wrote:
When you write the bin file with u-boot you use nand write.jffs2
<bin-file>. Whatever that produces is good for u-boot to load into
ram for execution but when you try to mount that block in Linux, you
get a bunch of problems. In other words, they don't appear to be
compatible. I'm thinking that somehow I need the kernel image already
in some sort of JFFS2 image format and do what you said and just write
it to /dev/mtdblock4.
*From:*Stuart Hughes [mailto:[email protected]]
*Sent:* Thursday, September 01, 2011 3:51 AM
*To:* Chris Westervelt
*Cc:* [email protected]
*Subject:* Re: [Ltib] updating Kernel image in MTD from Linux
Hi Chris,
You need to provide more detail.
If the MTD partition holding the kernel is formatted as jffs2 then you
should be able to just mount and then copy across the new kernel image.
If it's a raw partition then I think you can just do 'cp ImageFile
/dev/mtdx'
Regards, Stuart
On 31/08/11 18:38, Chris Westervelt wrote:
Has anyone worked out a mechanism that would allow one to re-write the
Kernel MTD block with a fresh Kernel from inside linux? If I try to
mount this partition jffs2, I get lots of errors and an inevitable
mount failure.
*Chris Westervelt*
_______________________________________________
LTIB home page: http://ltib.org
Ltib mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/ltib
