All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonas Dietsche <jdietsche@fsforth.de>
To: blair@circumnavnetworks.com
Cc: linux-mtd@lists.infradead.org
Subject: Re: nand write problem
Date: Tue, 31 May 2005 17:24:02 +0200	[thread overview]
Message-ID: <429C8192.30004@fsforth.de> (raw)
In-Reply-To: <1117478995.24559.12.camel@blairs-desktop>

Hi Blair,

thanks for your help!

>># ./nandwrite --jffs2 /dev/mtd/2 jffs2.img
>>Use -f option to enforce legacy placement on autoplacement enabled mtd 
>>device
> 
> What version of nandwrite (nandwrite -V) do you have? Version 1.30
> supports -f.

> 
>># ./nandwrite -f /dev/mtd/2 jffs2.img
>>./nandwrite: illegal option -- f
>>
>># ./nandwrite -f --jffs2 /dev/mtd/2 jffs2.img
>>./nandwrite: illegal option -- f
>>
>># ./nandwrite -p /dev/mtd/2 jffs2.img
>>this takes a long time until it is finished.
> 
> If your JFFS2 image has any size to it, I would expect it to take some
> time.
> 
>>then I mount it with
>># mount -t jffs2 /dev/mtdblock/2 /mnt/
>>and get a lot of
>>CLEANMARKER node found at 0x00000000 has totlen 0xc != normal 0x0
>>
>>Copy the image with nandwrite is the correct and only way? Or is there 
>>another possibility?
> 
> I've seen the CLEANMARKER errors before. How did you create the JFFS2
> partition?
> 
> Check out this thread for a little more detail:
> http://lists.infradead.org/pipermail/linux-mtd/2005-March/012045.html
> 
> Good luck! 
> 
> -blair
> 

-- 
Jonas Dietsche, FS Forth-Systeme GmbH, www.fsforth.de
Kueferstrasse 8, 79206 Breisach, Germany
Phone: +49 (7667) 908 189, FAX +49 (7667) 908 200

  reply	other threads:[~2005-05-31 15:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <B1091462CF5479489B1D8FE818330D2C80F27E@exchange2003.ad.skymv.com>
2005-05-30 10:34 ` nand write problem Jonas
2005-05-30 18:49   ` Blair Barnett
2005-05-31 15:24     ` Jonas Dietsche [this message]
2005-05-31 15:35       ` Jonas
2005-05-31 15:24     ` Peter Grayson
2005-05-25 14:29 Jonas
2005-05-25 14:55 ` Thomas Gleixner

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=429C8192.30004@fsforth.de \
    --to=jdietsche@fsforth.de \
    --cc=blair@circumnavnetworks.com \
    --cc=linux-mtd@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.