[U-Boot] Bug in saveenv handling?

[Tom Rini]

On Tue, Apr 09, 2019 at 10:53:36PM +0200, U.Mutlu wrote:
> Frank Wunderlich wrote on 04/09/2019 09:39 PM:
> >this looks for me like the CONFIG_ENV_OFFSET+CONFIG_ENV_SIZE is overlapping uboots code
> >
> >can you post these values and position of uboot and its size for your device?
> >
> >which env-storage do you use (EMV_IN_MMC or ENV_FAT)?
> 
> I looked up in the .config file:
> 
> # U-Boot 2019.04-rc4 Configuration
> 
> 
> $ grep CONFIG_ENV_OFFSET .config
> CONFIG_ENV_OFFSET=0x88000
> 
> $ grep CONFIG_ENV_SIZE .config
> CONFIG_ENV_SIZE=0x20000
> 
> $ grep EMV_IN_MMC .config
> 
> $ grep ENV_FAT .config
> CONFIG_ENV_FAT_INTERFACE="mmc"
> CONFIG_ENV_FAT_DEVICE_AND_PART="0:auto"
> CONFIG_ENV_FAT_FILE="uboot.env"
> 
> I guess the uboot.env is a hidden file, but occassionally (esp. after
> saveenv & reboot) I see this file as a normal file in /, not hidden.
> 
> I used "Lamobo_R1_defconfig" as basis and made just a few

So, -rc4 has a bug that the final release does not, on this platform.
Please try the v2019.04 release first and then if you see the problem
still, continue reporting and also make sure to Cc Jagan, thanks!

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190409/1d4faf7d/attachment.sig>