[u-boot] Environment garbled after setenv?

Evgeniy Karyakin anthropophagite at gmail.com
Mon Dec 8 05:58:47 CET 2008

Al Johnson:
> On Sunday 07 December 2008, Evgeniy Karyakin wrote:
>> Joachim Breitner:
>>> AFAIR, the NOR uboot and the NAND uboot don’t share the environment – is
>>> that right?
>>     Then I don't know what "u-boot_env" points to. If we update NAND
>> environment and then boot with the help of NOR menu, I don't see a
>> point. Frankly I never tried NAND, maybe I should now.
> The NOR uboot environment is stored in NOR, and you can't change it unless you 
> have a debug board. This is intentional as the NOR uboot is there to stop you 
> being able to brick your phone, and it wouldn't be much good at that if you 
> could wipe its environment. You should usually be using the NAND uboot which 
> keeps its environment in NAND in the u-boot_env area.

    This explains everything, Al, thanks. So when I use a terminal to 
get into U-Boot console, I interact with NOR machinery, and u-boot_env 
storage is really in NAND field; that makes a point.

More information about the community mailing list