On Tue, Aug 6, 2013 at 2:12 PM, Stephen Warren <swar...@wwwdotorg.org> wrote: > On 08/06/2013 10:58 AM, Otavio Salvador wrote: >> On Tue, Aug 6, 2013 at 1:54 PM, Stephen Warren <swar...@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? > > I don't believe you can. Why would you want to? It's the default > environment that makes sense for that board, and that's defined by the > person creating U-Boot. > > If you want the user to be able to switch between different > environments, just have them save/load from a disk file that they > create. I think there's a command for that?
So that's the real goal to change it inside of code. This does make sense to have a way to set it from outside. -- Otavio Salvador O.S. Systems http://www.ossystems.com.br http://projetos.ossystems.com.br Mobile: +55 (53) 9981-7854 Mobile: +1 (347) 903-9750 _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
