From mboxrd@z Thu Jan  1 00:00:00 1970
From: U.Mutlu <for-gmane@mutluit.com>
Date: Tue, 9 Apr 2019 23:01:43 +0200
Subject: [U-Boot] Bug in saveenv handling?
In-Reply-To: <5CAD0650.5010903@mutluit.com>
References: <q8iqdd$1pq4$1@blaine.gmane.org>
 <trinity-119c7ac1-2918-40be-911f-0849443b8b65-1554838765772@3c-app-gmx-bs46>
 <5CAD0650.5010903@mutluit.com>
Message-ID: <5CAD0837.2010506@mutluit.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

U.Mutlu wrote on 04/09/2019 10:53 PM:
> 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

Maybe EMV_ is a typo and should rather be ENV_ ?
$ grep -i EMV_ .config

$ grep -i ENV_ .config
CONFIG_ENV_SIZE=0x20000
CONFIG_ENV_OFFSET=0x88000
CONFIG_ENV_VARS_UBOOT_CONFIG=y
# CONFIG_SYS_CONSOLE_ENV_OVERWRITE is not set
# CONFIG_SPL_ENV_SUPPORT is not set
CONFIG_CMD_ENV_EXISTS=y
# CONFIG_CMD_ENV_CALLBACK is not set
# CONFIG_CMD_ENV_FLAGS is not set
# CONFIG_ENV_IS_IN_EEPROM is not set
CONFIG_ENV_IS_IN_FAT=y
# CONFIG_ENV_IS_IN_EXT4 is not set
# CONFIG_ENV_IS_IN_FLASH is not set
# CONFIG_ENV_IS_IN_MMC is not set
# CONFIG_ENV_IS_IN_NAND is not set
# CONFIG_ENV_IS_IN_NVRAM is not set
# CONFIG_ENV_IS_IN_ONENAND is not set
# CONFIG_ENV_IS_IN_REMOTE is not set
# CONFIG_ENV_IS_IN_SPI_FLASH is not set
# CONFIG_ENV_IS_IN_UBI is not set
CONFIG_ENV_FAT_INTERFACE="mmc"
CONFIG_ENV_FAT_DEVICE_AND_PART="0:auto"
CONFIG_ENV_FAT_FILE="uboot.env"
# CONFIG_USE_DEFAULT_ENV_FILE is not set
# CONFIG_ENV_VARS_UBOOT_RUNTIME_CONFIG is not set

> $ 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
> irrelevant minor changes in make menuconfig.
> It's actually a Banana Pi R1 board.
> CONFIG_DEFAULT_DEVICE_TREE="sun7i-a20-lamobo-r1"
>
> Thx
>
>>> Gesendet: Dienstag, 09. April 2019 um 21:05 Uhr
>>> Von: "U.Mutlu" <for-gmane@mutluit.com>
>>
>>> It seems u-boot has overwritten parts of itself on the storage medium (uSD
>>> with FAT boot partition).