Greetings,
I have to agree with Wolfgang.
You should be fine as long as you use multiple blocks per environment range
and use redundant environments.
These are two separate things that both need to be enabled.
Here's the setup that's working good for us.
I tested it by simulating bad blocks with
Dear Frans Meulenbroeks,
In message <817622.67175...@web33604.mail.mud.yahoo.com> you wrote:
>
> > Time to look into UBI, me thinks.
>
> For u-boot env settings??
Why not? Once the flash is UBI managed, there are virtually no bad
blocks any more.
> My problem that the designated env blocks
Am Sonntag, den 11.01.2009, 14:28 +0100 schrieb Wolfgang Denk:
> Dear Manfred,
>
> In message <1231672254.3130.29.ca...@mobil.alm.archives.at> you wrote:
> >
> > 1. For our systems we assume, that the env-block never gets bad in
> > productive use, because the env-block is never written again. So
Hi!
Am Sonntag, den 11.01.2009, 05:26 -0800 schrieb Frans Meulenbroeks:
> Manfred,
>
> Thanks for your suggestions.
> Did you modify u-boot to search from the last block of the device backwards?
> I feel putting the env at the end is quite a good idea.
>
Yes. First I wanted to implement the openm
>
> That's a pretty risky setup because it is based on
> an incorrect
> assumption - on NAND, block become not only bad when being
> erased or
> written to, but also after a certain number of read
> operations is
> exceeded. Yes, there is a maximum number of reads per
> block on NAND!
Dear Manfred,
In message <1231672254.3130.29.ca...@mobil.alm.archives.at> you wrote:
>
> 1. For our systems we assume, that the env-block never gets bad in
> productive use, because the env-block is never written again. So we
> reduced the problem to number of initial/factory bad blocks.
That's
rom: Schlaegl Manfred jun.
> Subject: Re: [U-Boot] NAND bad environment block handling
> To: fransmeulenbro...@yahoo.com
> Cc: u-boot@lists.denx.de
> Date: Sunday, January 11, 2009, 12:10 PM
> Hi!
> Am Donnerstag, den 08.01.2009, 07:19 -0800 schrieb Frans
> Meulenbroeks:
> >
Hi!
Am Donnerstag, den 08.01.2009, 07:19 -0800 schrieb Frans Meulenbroeks:
>
> Has someone experience in this area? Ideas? Suggestions?
1. For our systems we assume, that the env-block never gets bad in
productive use, because the env-block is never written again. So we
reduced the problem to num
Dear Marcel Ziswiler,
In message you wrote:
>
> The openmoko guys do have an alternative implementation which dynamically
> sizes
> all partitions in NAND according to what bad blocks are found therefore not
> wasting any space. And they are using it in full-scale production environment
> for th
common practice today seems to be to reserve slack room for every partition (or
even worse, ignore the problem and assume perfect NAND)
Best regards, Frans
--- On Thu, 1/8/09, Cote, Sylvain wrote:
> From: Cote, Sylvain
> Subject: RE: [U-Boot] NAND bad environment block handlin
Scott Wood freescale.com> writes:
> On Thu, Jan 08, 2009 at 07:19:29AM -0800, Frans Meulenbroeks wrote:
> > Is there a solution for this? (obviously I am not considering the
> > situation for a single system, where I just would relocate the
> > environment block; this concerns a production situat
On Thu, Jan 08, 2009 at 07:19:29AM -0800, Frans Meulenbroeks wrote:
> Is there a solution for this? (obviously I am not considering the
> situation for a single system, where I just would relocate the
> environment block; this concerns a production situation).
>
> E.g. it would be nice if U-Boot c
Hi,
I think bad blocks are less likely to happen near the first block, which
is guaranteed to be good. It may be possible to find NAND chip that
guarantee more blocks but I have not encountered one myself.
U-boot has the code to skip bad block when reading environment. As
Sylvain said, you j
oun...@lists.denx.de [mailto:u-boot-boun...@lists.denx.de] On
Behalf Of Frans Meulenbroeks
Sent: Thursday, January 08, 2009 10:19 AM
To: u-boot@lists.denx.de
Subject: [U-Boot] NAND bad environment block handling
Hi,
I'm wondering what the best way is to handle bad environment blocks in NAND.
Accordin
Hi,
I'm wondering what the best way is to handle bad environment blocks in NAND.
According to the spec of our supplier a delivered component is considered to be
OK if less than 2% of the blocks are not bad.
This means that for our products we need to take into account that worst case
2% of the
15 matches
Mail list logo
