On Tue, Aug 06, 2013 at 01:58:22PM -0300, Otavio Salvador wrote:
On Tue, Aug 6, 2013 at 1:54 PM, Stephen Warren swarren@wwwdotorg.org wrote:
How can someone 'overwrite' the default environment from system or when generating a FIT image?
If U-Boot is running, you can get back to the default environment by running exactly the commands you wrote below.
If you're flashing U-Boot, you could force it to use the default environment when it boots by erasing/corrupting the copy of the environment that's stored in flash (or wherever ENV_IS points) at the same time that you flash the new U-Boot binary.
The question of how to get the default environment when generating a FIT image doesn't make sense; generating a FIT image of something (kernel, initrd, DTB?) is entirely unrelated to the environment content that U-Boot uses when running.
Ok but when I do env -f -d -a it uses the built-in environment as default. How can I 'change' this default without rebuilding U-Boot binary?
What you want (and I'm not saying this works today) would be: load ... $addr otavios-sane-env.txt env import -t --reset-to $addr
Where --reset-to cleared the current environment and set it to only the valid env found at $addr.