From: Artem Bityutskiy <dedekind@infradead.org>
To: "Musch, Edwin" <musche@dataio.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: UBI - NAND Flash Programming
Date: Tue, 05 May 2009 08:18:15 +0300 [thread overview]
Message-ID: <1241500695.3760.32.camel@localhost.localdomain> (raw)
In-Reply-To: <B538B21A486F9E4CBBE577217764F37701662A53@email2.dataio.internal>
On Mon, 2009-05-04 at 08:39 -0700, Musch, Edwin wrote:
>
> Hello
>
> I am from Data I/O. We produce mass production Flash programming equipment.
> We received a request from Keymile/Germany to support the UBI.
>
> As you will know we need to program the raw NAND Flash the same way than the application is handling the NAND Flash ( bad blocks )
>
> Could you please give me further information regarding the Bad Block Handling? Since we are programming the NAND Flash only once we are not worried about wear levelling.
>
You have an UBI image, and you need to flash it to your device,
right?
> 1) If we detect a bad block where should we move the Data
> a. SKIP: go on with the next good block - or
> b. Put the Data into a reserved area
> c. Please let me know where this area is defined
a).
> 2) Do I need to update the Main area if I move a block? - Is there a header?
> 3) Could you explain the info within the spare area?
> a. Do I need to update anything if I move a block to different location?
> b. ECC - In case I need to update the main area - How is it done?
I do not really understand these questions, sorry.
> 4) Are there any dynamic table somewhere that needs to be updated - Bad block table?
There might be. It depends what you MTD driver chooses. See the
NAND_USE_FLASH_BBT option in the linux kernel. I personally never
used on-flash BBT.
Please, take a look here:
http://www.linux-mtd.infradead.org/doc/ubi.html#L_format
The flashing algorithm is described there.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2009-05-05 5:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-04 15:39 UBI - NAND Flash Programming Musch, Edwin
2009-05-05 5:18 ` Artem Bityutskiy [this message]
2009-05-05 21:41 ` AW: " Musch, Edwin
2009-05-13 8:24 ` 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=1241500695.3760.32.camel@localhost.localdomain \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=musche@dataio.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