From: Artem Bityutskiy <dedekind1@gmail.com>
To: twebb <taliaferro62@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: ubiformat image verification
Date: Mon, 01 Feb 2010 06:33:29 +0200 [thread overview]
Message-ID: <1264998809.2517.7.camel@localhost.localdomain> (raw)
In-Reply-To: <dbdb2ea61001311650v136a002v3a8e261e91d4a457@mail.gmail.com>
On Sun, 2010-01-31 at 19:50 -0500, twebb wrote:
> >>> Can the image that is written to NAND using ubiformat be read back
> >>> (using nanddump) and compared identically to the original image file?
> >>> I want to somehow verify that the image was written error-free to NAND
> >>> flash.
> >>
> >> It can. But it is simpler to add a --check option to ubiformat and teach
> >> it to read stuff back and verify.
> >>
> >
> > Yes, a --check or --verify option would be nice. Does it matter
> > whether the underlying NAND flash is erased or not prior to the
> > ubiformat?
> >
>
> I'm finding that it does matter whether the NAND is erased or not
> first. If erased, the comparison after read back is successful. If
> not erased in advance, the comparison fails. Can you confirm that
> this is accurate?
ubiformat works correctly without any prior erase. It erases everything
itself, you do not need to do this. Erasing is bad because you loose
erase counters.
You cannot verify things by reading back, because ubiformat changes
erase counters, so they are not the same as in input UBI the image.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-02-01 4:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 19:18 ubiformat image verification twebb
2010-01-29 20:21 ` Artem Bityutskiy
2010-01-31 23:17 ` twebb
2010-02-01 0:50 ` twebb
2010-02-01 4:33 ` Artem Bityutskiy [this message]
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=1264998809.2517.7.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=taliaferro62@gmail.com \
/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