From: U.Mutlu <for-gmane@mutluit.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Bug in saveenv handling?
Date: Tue, 9 Apr 2019 23:01:43 +0200 [thread overview]
Message-ID: <5CAD0837.2010506@mutluit.com> (raw)
In-Reply-To: <5CAD0650.5010903@mutluit.com>
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).
next prev parent reply other threads:[~2019-04-09 21:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-09 19:05 [U-Boot] Bug in saveenv handling? U.Mutlu
2019-04-09 19:39 ` Frank Wunderlich
2019-04-09 20:53 ` U.Mutlu
2019-04-09 21:01 ` U.Mutlu [this message]
2019-04-09 21:21 ` U.Mutlu
2019-04-10 8:00 ` Frank Wunderlich
2019-04-10 18:32 ` U.Mutlu
2019-04-09 21:09 ` Tom Rini
2019-04-09 23:10 ` U.Mutlu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5CAD0837.2010506@mutluit.com \
--to=for-gmane@mutluit.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox