public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] NAND and JFFS2
Date: Wed, 23 May 2007 13:56:04 +0200	[thread overview]
Message-ID: <46542BD4.4020102@atmel.com> (raw)
In-Reply-To: <131AF8573CF31945B5B11E4201D3F1E142BC58@mail3.Avidyne.com>

Matt Gessner skrev:
> Hi, all,
> 
> I'm using 1.2.0 on an AT91RM9200, along with linux 2.6.20-2 w/ patches
> from Maxim.
> 
> I'm looking for info on how compatible the JFFS2 stuff is between u-boot
> and linux.
> 
> When I mount a partition (I have JFFS2 debugging turned on in the
> kernel), I get two kinds of error messages:
> 
> 	"jffs2_check_nand_cleanmarker(): Cleanmarker node not detected
> in block at X"
> 	"OOB at X was ...."  (lots of data, not all FF)
> 	"CLEANMARKER node found at X has totlen 0xc != normal 0x0"
> 
> OR
> 
> 	"jffs2_check_nand_cleanmarker(): Cleanmarker node not detected
> in block at X"
> 	"OOB at X was ...."  (lots of FF)
> 
> I'm wondering if anyone can point me to what I'm doing wrong.
> 
> I have 3 partitions: boot, backup and config, which I made using
> mtdparts.  When I work with my nand device, I use 'nand erase clean',
> which I thought would write the nand clean markers.  The jffs2 is
> expecting nand clean markers at every 4K (0x1000) bytes.
> 
> I'm wondering if my mkfs.jffs2 command is wrong, or if my use of nand
> erase is wrong, or if I need to specify something in either the kernel
> or the u-boot config is wrong.
> 

Extract from www.at91.com forum post:
"When using NAND make sure to pass the -n option to mkfs.jffs2 when creating the image.
Otherwise you will get errors about the cleanmarkers when you mount the filesystem"

> Any pointers are appreciated.
> 
> Thanks for everyone's hard work making u-boot a great tool.
> 
> Regards,
> 
> Matt G.
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> U-Boot-Users mailing list
> U-Boot-Users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/u-boot-users


-- 
Best Regards,
Ulf Samuelsson
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ulf.vcf
Type: text/x-vcard
Size: 301 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20070523/3bf1f622/attachment.vcf 

  reply	other threads:[~2007-05-23 11:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23 14:14 [U-Boot-Users] NAND and JFFS2 Matt Gessner
2007-05-23 11:56 ` Ulf Samuelsson [this message]
2007-05-24 13:41   ` Matt Gessner
2007-05-24 14:36 ` Detlev Zundel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46542BD4.4020102@atmel.com \
    --to=ulf@atmel.com \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox