From mboxrd@z Thu Jan 1 00:00:00 1970 From: U.Mutlu Date: Wed, 10 Apr 2019 01:10:21 +0200 Subject: [U-Boot] Bug in saveenv handling? In-Reply-To: <20190409210903.GX4664@bill-the-cat> References: <5CAD0650.5010903@mutluit.com> <20190409210903.GX4664@bill-the-cat> Message-ID: <5CAD265D.9070708@mutluit.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Tom Rini wrote on 04/09/2019 11:09 PM: > 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 >> > 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! # U-Boot 2019.04 Configuration Yes, I too can confirm now that the problem of saveenv overwriting u-boot doesn't happen in the 2019.04 release version. But the said crash when issuing the command "scsi scan" is still present, but this maybe has some other reasons. Thx.