This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: JFFS2 on big-endian system
On Montag, 24. November 2003 21:10, Gary Thomas wrote:
> On Mon, 2003-11-24 at 10:46, Roland Caßebohm wrote:
> > Hello,
> >
> > I try to use jffs2 on my big-endian system. First I had the problem, that
> > mkfs.jffs2 couldn't make big-andian images, even if -b was set. Now I
> > have a newer version which could do that.
> >
> > This is what I have done:
> >
> > Linux> mkfs.jffs2 -o jffs2_b.img -b -r experimental -e 0x10000
> >
> > RedBoot> load -r -b 0x40000 -h 192.168.1.36 jffs2_b.img
> > RedBoot> fis create -f 0x20c0000 -l 0x30000 jffs2
> >
> > It works except of mount() gave th following output:
> >
> > <4>Node at 0x00000c30 with length 0x000004d6 would run over the end of
> > the erase block
> > <4>Perhaps the file system was created with the wrong erase size?
> > <5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000c38:
> > 0xde82 instead
> > <5>Further such events for this erase block will not be printed
> > <5>jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00001000:
> > 0x7cba instead
> > <5>Further such events for this erase block will not be printed
> >
> > Does anybody know what could be wrong?
>
> Does your FLASH actually have an erase block size of 64K (0x10000)?
> This number is *critical* - if it's wrong, either too large or too
> small, the whole file system fails.
My FLASH have a block size of 4K (0x1000) so the erase block size is
4K two. But always erasing 64K at once shouldn't be a problem and the
minimal configureable erase blocksize seems to be 64K.
>
> Other than that, try turning on the low level debug messages. That may
> show you something.
Where can I turn on low level debug messages?
Thanks,
Roland
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss