2011/12/28 Ni Qingliang <niqingli...@insigma.com.cn> > I have just done a seperate env tools bb for my project, but use the > config file to assign the env size and address (which is generated on > booting from /proc/mtd). > > in the fdt, the u-boot env has a seperate partition identified by it's > name "u-boot environment" > > and have some problem: > 1. the fw_printenv will exit with 0 even though can't read the env (CRC > error). >
Apparently the author of the program did not consider this as an error. See tools/env/fw_env.c > > 2. the default env vars in fw_printenv(used when CRC error) are not same > as it in the u-boot. > If I recall correctly this is addressed in the 2nd patch I posted. >From memory: Issue is that fw_env.h redefines CONFIG_BOOTCOMMAND. This gives you a different boot command. By putting #ifdef's around it the default one is taken Enjoy! Frans
_______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
