From: Martin Egholm Nielsen <martin@egholm-nielsen.dk>
Date: Tue, 21 Dec 2004 10:01:16 +0100
Subject: [U-Boot-Users] Re: Reading or writing jffs2 - how?
In-Reply-To: <87ekhkc26l.fsf@deepthought.outer.space.org>
References: <cppc9u$op8$1@sea.gmane.org>	<87hdmnuvpi.fsf@deepthought.outer.space.org>	<41C6DD2F.5090800@egholm-nielsen.dk> <87ekhkc26l.fsf@deepthought.outer.space.org>
Message-ID: <41C7E65C.7030002@egholm-nielsen.dk>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Detlev,

>>The problem has been solved...
>>The reason that "ls" didn't work from u-boot, was that the boards'
>>u-boot config-file included an erroneous nand-size:
>>#define CONFIG_JFFS2_NAND_SIZE 64*1024*1024
> Yes, I was about to check the options available in U-Boot and ask you
> to verify those but you beat me to it.
:-)

>>My board had only one configuration-file associated, but multiple
>>nand-size configurations.
>>The jffs2-image problems were related to the endianess problems of
>>mkfs.jffs2:
>>http://lists.infradead.org/pipermail/linux-mtd/2004-January/009091.html
> Another reason for using our ELDK - it has a working mkfs.jff2 ;)
Noo?! I used mkfs.jffs2 from ELDK 3.0:

# mkfs.jffs2 --version
mkfs.jffs2 revision 1.25

# which mkfs.jffs2
/usr/local/eldk/usr/bin/mkfs.jffs2

# cat /usr/local/eldk/version
ELDK version 3.0
ppc_4xx: Build 2004-02-16

But ofcourse, I guess the above error blocked u-boot from putting the 
correct image in the nand...

BR,
  Martin Egholm