<br><br><div class="gmail_quote">2011/12/28 Ni Qingliang <span dir="ltr"><<a href="mailto:niqingliang@insigma.com.cn">niqingliang@insigma.com.cn</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I have just done a seperate env tools bb for my project, but use the<br>
config file to assign the env size and address (which is generated on<br>
booting from /proc/mtd).<br>
<br>
in the fdt, the u-boot env has a seperate partition identified by it's<br>
name "u-boot environment"<br>
<br>
and have some problem:<br>
1. the fw_printenv will exit with 0 even though can't read the env (CRC<br>
error).<br></blockquote><div><br>Apparently the author of the program did not consider this as an error.<br>See tools/env/fw_env.c<br> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
2. the default env vars in fw_printenv(used when CRC error) are not same<br>
as it in the u-boot.<br></blockquote></div><br>If I recall correctly this is addressed in the 2nd patch I posted.<br>From memory:<br>Issue is that fw_env.h redefines CONFIG_BOOTCOMMAND. This gives you a different boot command.<br>
By putting #ifdef's around it the default one is taken<br><br>Enjoy!<br>Frans<br><br>