[u-boot] Environment garbled after setenv?

Al Johnson openmoko at mazikeen.demon.co.uk
Mon Dec 8 00:13:31 CET 2008

On Sunday 07 December 2008, Evgeniy Karyakin wrote:
> Joachim Breitner:
> >>     I modified (shorten) your script for my needs and it works without
> >> an error, although I haven't really got my end station. After flashing
> >> environment with your script and then reading it back I see that
> >> environment reflects the changes desired. But getting to u-boot console
> >> shows me old env variables (printenv), and booting microSD card from NOR
> >> menu actually invokes old menu_1 setting -- I can see that after ssh-ing
> >> into the phone and seeing what's in /proc/cmdline. Strange.
> >>     My modified script is in attachment in case you're curious.
> >
> > Thanks.
> >
> > 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.

More information about the community mailing list