From: U.Mutlu <for-gmane@mutluit.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Bug in saveenv handling?
Date: Wed, 10 Apr 2019 01:10:21 +0200 [thread overview]
Message-ID: <5CAD265D.9070708@mutluit.com> (raw)
In-Reply-To: <20190409210903.GX4664@bill-the-cat>
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.
prev parent reply other threads:[~2019-04-09 23:10 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
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 [this message]
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=5CAD265D.9070708@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