AM3358: Uboot environment

Nancy Wang

Expert 8210 points

Part Number: AM3358

Hi,

The customer flashed uboot in spi nor flash and dtb+kernel+rootfs in emmc.

1.He set bootfile=uImage(original ZImage), and system can reading uImage successfully.

printenv->uImage

2.Clear bootfile and the system reading zImage again after reboot

printenv->zImage

Please help explain in detail.

over 6 years ago

0 Kemal R. Shakir over 6 years ago

TI__Guru 55345 points

Hello Nancy,

It is not clear where the U-Boot environment gets saved. Please, edit the bootfile in <Processor SDK>/board-support/u-boot-<version>/include/configs/am335x_evm.h and rebuild the u-boot.img to have the zImage changed to uImage.

Best regards,
Kemal

0 Nancy Wang over 6 years ago in reply to Kemal R. Shakir

TI__Expert 8210 points

Hi,

The customer edited in that way like you said and could change to uImage successfully. But when he clear that value, the system read zImage automatically again. What‘s the realization principle?

0 Kemal R. Shakir over 6 years ago in reply to Nancy Wang

TI__Guru 55345 points

Can you try this scenario?

=> setenv bootfile
=> saveenv
=> reset
=> printenv bootfile

If an uEnv.txt file gets loaded and the bootfile is defined as zImage there, but when you type saveenv the environment is saved as uboot.env, in this case you can observe this kind of behavior, or if you have if setenv bootfile zImage condition defined somewhere within your U-Boot environments can also lead to this kind of result.