From: Daniel Gorsulowski <Daniel.Gorsulowski@esd.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] Nand: Uboot-Environment at bad block
Date: Thu, 04 Aug 2011 12:07:00 +0200 [thread overview]
Message-ID: <4E3A6F44.5000808@esd.eu> (raw)
In-Reply-To: <BANLkTimtNJ5Au4uPp2D7q8hZkbk3x5RERA@mail.gmail.com>
Arno Steffen wrote:
> In one of my devices, uboot-environment is located at a bad block.
> "save
> Saving Environment to NAND...
> Erasing Nand...
> Skipping bad block at 0x000c0000
>
> Writing to Nand... FAILED!"
>
> In my memory mapping I have already reseverd 2blocks.
> How can I setup uboot in a way, that it will look at c0000 or (in case
> of bad block) at the next block e0000?
>
...
>
> Maybe someone can give me an advice?
> Thanks
> - Arno
>
...
Hello!
Is there a solution to this problem?
I was going to ask exactly the same question, but then I found this topic.
My board config (ARM platform) is
#define CONFIG_ENV_IS_IN_NAND 1
#define CONFIG_ENV_OFFSET 0xC0000
#define CONFIG_ENV_SIZE 0x20000
Now there is a board with a bad block exactly at 0xC0000
=> nand bad
Device 0 bad blocks:
000c0000
02f40000
...
If I try to write the environment, i get
Saving Environment to NAND...
Erasing Nand...
Skipping bad block at 0x000c0000
Writing to Nand... FAILED!
Any hints?
Kind regards
Daniel
next prev parent reply other threads:[~2011-08-04 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 14:10 [U-Boot] Nand: Uboot-Environment at bad block Arno Steffen
2011-06-20 14:33 ` Wolfgang Denk
2011-06-20 14:49 ` Arno Steffen
2011-06-20 14:58 ` Wolfgang Denk
2011-08-04 10:07 ` Daniel Gorsulowski [this message]
2011-08-04 18:02 ` Scott Wood
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=4E3A6F44.5000808@esd.eu \
--to=daniel.gorsulowski@esd.eu \
--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 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.