[U-Boot] Problems with fw_printenv

Wolfgang Denk wd at denx.de
Thu Mar 4 09:57:00 CET 2010


Dear Ronald Kortekaas,

In message <4B8F60A1.4070105 at 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!_


More information about the U-Boot mailing list