From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Problems with fw_printenv
Date: Thu, 04 Mar 2010 09:57:00 +0100 [thread overview]
Message-ID: <20100304085700.13D2B28BBC@gemini.denx.de> (raw)
In-Reply-To: <4B8F60A1.4070105@chess.nl>
Dear Ronald Kortekaas,
In message <4B8F60A1.4070105@chess.nl> you wrote:
>
> I think I found the solution. I changed my configuration als follows:
...
> Changed my mtdparts to:
>
> #define MTDPARTS_DEFAULT
> "mtdparts=physmap-flash.0:256k(uboot)ro,128k(ubootenv),128k(ubootenv_re),4096k(kernel)"
>
> So mtd in u-boot showd:
>
> device nor0 <physmap-flash.0>, # parts = 3
> #: name size offset mask_flags
> 0: uboot 0x00040000 0x00000000 1
> 1: ubootenv 0x00020000 0x00040000 0
> 2: ubootenv 0x00020000 0x00060000 0
> 3: kernel 0x00400000 0x00080000 0
>
> I changed fw_env.h to #define HAVE_REDUND.
>
> And the fw_env.config:
>
> /dev/mtd2 0x0000 0x20000 0x20000
> /dev/mtd3 0x0000 0x20000 0x20000
This is one way to address this. You can also keep both copies of the
environment variables in a single MTD partition - just provide the
correct device name, offset and size data.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If there was anything that depressed him more than his own cynicism,
it was that quite often it still wasn't as cynical as real life.
- Terry Pratchett, _Guards! Guards!_
next prev parent reply other threads:[~2010-03-04 8:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 10:25 [U-Boot] Problems with fw_printenv Ronald Kortekaas
2010-03-03 20:21 ` Wolfgang Denk
2010-03-04 6:14 ` Ronald Kortekaas
2010-03-04 8:55 ` Wolfgang Denk
2010-03-04 7:26 ` Ronald Kortekaas
2010-03-04 8:57 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-03-03 9:14 Ronald Kortekaas
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=20100304085700.13D2B28BBC@gemini.denx.de \
--to=wd@denx.de \
--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