Skip to contentSkip to conversation

jffs2 CFG_CMD_JFFS2

PATCH New himba 3 participants 3 messages Aug 21, 2004 – Oct 12, 2004

lore
Share & tools
lore

himba

author
#0 lore raw

PATCH 1/1 jffs2 CFG_CMD_JFFS2

Hi,

Running ./MAKEALL 8xx fails for several (all ?) boards using CFG_CMD_JFFS2. Problem is in defining chpart CMD after its corresponding do_jffs2_chpart() function has not been defined.

CHANGELOG:
Patch by Hinko Kocevar, 21 Aug 2004:
Fix build failure when CFG_CMD_JFFS2 is used

regards,
himba
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: cmd_jffs2.patch
Url: http://lists.denx.de/pipermail/u-boot/attachments/20040821/e23ca732/attachment.txt

#1 lore raw

PATCH 1/1 jffs2 CFG_CMD_JFFS2

Quoted 4 lines · In message <[email protected]> you wrote:

CHANGELOG:
Patch by Hinko Kocevar, 21 Aug 2004:
Fix build failure when CFG_CMD_JFFS2 is used

This was already fixed in the meantime. Thanks anyway.

Best regards,

Wolfgang Denk

Signature · 5 lines
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
Blast medicine anyway!  We've learned to tie into every organ in the
human body but one.  The brain!  The brain is what life is all about.
	-- McCoy, "The Menagerie", stardate 3012.4
#2 lore raw

[U-Boot-Users] nand write.jffs2 addr ofs size, what does size mean?

Hello README.nand says:

Quoted 7 lines

nand write.jffs2 addr ofs size
Like `write', but blocks that are marked bad are skipped and the is written to the next block instead. This allows writing writing a JFFS2 image, as long as the image is short enough to fit even after skipping the bad blocks. Compact images, such as those produced by mkfs.jffs2 should work well, but loading an image copied from another flash is going to be trouble if there are any bad blocks.

a) Is ofs+size-1 the maximal address where the NAND is accessed while writing?
b) Is add+size-1 the maximal address where the RAM is accessed while reading?
c) how does this change if bad blocks are detected?

e.g. in RAM at 200.000 is a 100.000bytes long jffs2 image generated by mkfs.jffs2. I wan't to install a JFFS2 with this content in NAND at 400.000 with 100.000bytes.

# nand write.jffs2 200.000 400.000 100.000

what happens if the NAND has some bad blocks, does the write command writes beyond 500.000 to the NAND, or does it abort since there is not enough space available?

thank you for any hints,

Signature · 3 lines
Thomas Kuhlmann, FS Forth-Systeme GmbH, www.fsforth.de
Kueferstrasse 8, D-79206 Breisach, Germany
Phone: +49 (7667) 908 144 Fax: +49 (7667) 908 244