On 25 Mar 2008 at 17:00, Markus Klotzbücher wrote:
w.wegner@astro-kom.de writes:
I just had the problem of fw_{print,save}env not being able to access the environment because I was using the default (builtin) environment after flashing U-Boot.
[...]>
AFAIK there is currently no way to check this from the U-Boot shell. Nevertheless I think that would be the way to go instead of hard-coding this. How about setting an environment variable like "env_default" if the default environment is used? That way scripts can be used to run saveenv but could also do more complex initialization.
This seems to be the cleanest solution to me - and the easiest, too, because no patching of U-Boot is required. I just did not think about the possibilty to un-set the environment variable when this initialization is run to make it a one-shot run... 8)
Best regards
Markus Klotzbuecher
Thank you and best regards, Wolfgang