The default CONFIG_ENV_OFFSET is not enough for i.MX6 SabreAuto board on U-Boot 201601

[yeah]

Hi,

Do not know who should fix this issue:

The default CONFIG_ENV_OFFSET in mx6sabre_common.h of U-Boot 201601 is not correct as below:

git.denx.de Git - u-boot.git/blob - include/configs/mx6sabre_common.h

211 #if defined(CONFIG_ENV_IS_IN_MMC)

212 #define CONFIG_ENV_OFFSET               (8 * 64 * 1024)

213 #endif

It is 512KB, while I compiled as below:

gcc: gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_linux.tar.xz from: http://releases.linaro.org/14.03/components/toolchain/binaries/

export ARCH=arm

export CROSS_COMPILE=arm-linux-gnueabihf-

make distclean

make mx6dlsabreauto_config

make

The produced image for i.MX6DL SabreAuto is: 535 KB (547,840 bytes) and has conflict with the env offset.

So when saveenv, the U-Boot cannot boot up again.

I also searched an old commit here:

git.denx.de Git - u-boot.git/commit

imx: mx6q/dl sabre_common: Move MMC ENV offset to 512KB position

Set the CONFIG_ENV_OFFSET from 384KB to 512KB offset, so we will have larger space

for u-boot image.

When enabling NAND flash support feature, the u-boot image size has exceeded the

384KB, which causes overlay to the environment variables storage.

Signed-off-by: Ye.Li <B37916@freescale.com>

Acked-by: Fabio Estevam <fabio.estevam@freescale.com>

So it may need to enlarge again.

[BiyongSUN · Accepted solution]

please use nxp official git server:

uboot-imx.git - Freescale i.MX u-boot Tree

[yeah]

Yes, the nxp official works as it produced a image "470016 Jan 27 09:36 u-boot.imx".

Maybe the git.denx.de Git - u-boot.git/commit should be updated to make it work too.

[weidong_sun]

Hello Yeah,

     Did you solve your questions according to Biyong's suggestion?

     Yes, you should be u-boot source code from NXP git server and patch it.

Regards,

weidong

[yeah]

Hi Weidong,

There's no need to patch, just because the default built image is bigger than the ENV_OFFSET from DENX git server.

The NXP git server's produced image is not bigger that it.

But I doubt 512KB ENV_OFFSET is still dangerous, may need to enlarge or use other method. But it depends on NXP's enginerring.

BR.

Yeah