Dear "David Collier",
In message <memo.20090812101725.10088B@postmaster+dexdyne.com.cix.co.uk> you wrote:
Dear "Dexdyne Postmaster",
whoops - fixed that now!!!
Thanks.
This depends on your configuration. When using an "embedded" environment, this will get replaced with each install.
" this will get replaced with each install "
sorry - I don't know how you mean that will happen....
If you flash a new U-Boot image, this will also overwrite the embedded environment with the one built into the U-Boot image.
OK - I'm working on an AVR32 - if I follow the instructions they give, it
I have no idea who "they" are, nor what instructions "they" give, but if you follow their advice you should probably ask them for help, too.
replaces the u-boot code, and leaves the environment sector in flash unchanged. I have added a 1-byte-write to the sector to my script to corrupt it.... but a command would be easier.
As mentioned above, with an embedded environment this is not needed.
OK again - I don't seem to have scripting enabled in my u-boot - I'd like to do that so I can use && in by boot sequence.
Well, then enable it.
What would I put in a script to have the effect of forcing a load of the new defaults??? If there's no single command, do you mean I could make up a script full of "set" commands?
A list of "setevn" commands, correct.
Best regards,
Wolfgang Denk