Dear u-boot specialists,

I've been working a while now with a beagle Xm board and using u-boot to boot a linux kernel. Recently I've performed an update to version u-boot-2011.03-rc1 and found that it's not booting anymore.

It looks like the bootcmd doesn't get set to the CONFIG_BOOTCOMMAND value in the 'include/configs/omap3_beagle.h' file. This value makes it into the 'include/autoconf.mk' file but not into the printenv of the u-boot. If I change the value of bootcmd (using setenv) to the CONFIG_BOOTCOMMAND value, and run bootcmd, everything works fine.

Is this issue known already and if so will it be solved in the next release?

Your help is appreciated.

Thanks, Egon.