From: Stefano Babic <sbabic@denx.de>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: artem.bityutskiy@linux.intel.com,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: Re: UBIFS seeing corrupt blank pages when image flashed via u-boot
Date: Fri, 03 Jan 2014 15:04:18 +0100 [thread overview]
Message-ID: <52C6C362.2020209@denx.de> (raw)
In-Reply-To: <1388753970.25123.124.camel@sauron.fi.intel.com>
Hi Gupta,
On 03/01/2014 13:59, Artem Bityutskiy wrote:
> Basically, "ubiformat" is the "correct" UBI-aware flasher, while
> u-boot's "nand write" seems to be a dumb flasher.
It is, it is *not* recommended for UBI volume without "ubinizing" your
image.
> I guess you have 2
> options:
>
> 1. Teach u-boot's "nand write" to skip empty pages, or may be implement
> a separate "clever" flashing command.
You can also add (my preferred way) UBI support to your U-Boot, if it
does not yet have. Then you will have "ubi part" (corresponds to
ubiattach in Artem's MTD utilities), "ubi createvol" and "ubi writevol"
(respectively, ubiupdatevol and ubimkvol). If you use dumb nand
utilities, you have to erase the flash first with "nand erase", and this
will lose the erase counters.
Best regards,
Stefano Babic
--
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-53 Fax: +49-8142-66989-80 Email: sbabic@denx.de
=====================================================================
next prev parent reply other threads:[~2014-01-03 14:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-03 11:45 UBIFS seeing corrupt blank pages when image flashed via u-boot Gupta, Pekon
2014-01-03 12:59 ` Artem Bityutskiy
2014-01-03 13:05 ` Bityutskiy, Artem
2014-01-03 14:04 ` Stefano Babic [this message]
2014-01-07 17:30 ` Gupta, Pekon
2014-01-13 12:19 ` Calvin Johnson
2014-01-13 12:58 ` Artem Bityutskiy
2014-01-13 13:16 ` Gupta, Pekon
2014-01-13 15:06 ` Artem Bityutskiy
2014-01-15 21:29 ` Gupta, Pekon
2014-01-16 7:19 ` Artem Bityutskiy
2014-01-16 7:44 ` Gupta, Pekon
2014-01-16 8:22 ` Artem Bityutskiy
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=52C6C362.2020209@denx.de \
--to=sbabic@denx.de \
--cc=artem.bityutskiy@linux.intel.com \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@ti.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;
as well as URLs for NNTP newsgroup(s).