From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot Tool: fw_setenv - kernel option?
Date: Tue, 18 Jul 2017 18:55:43 -0400 [thread overview]
Message-ID: <20170718225543.GD14320@bill-the-cat> (raw)
In-Reply-To: <trinity-c9473cde-db50-4887-9dd1-6b994681284b-1500300507110@3capp-gmx-bs55>
On Mon, Jul 17, 2017 at 04:08:27PM +0200, Arno Steffens wrote:
> After using a plain vanilla instead of a vendor kernel I do have
> problems with fw_setenv.
> Althoug fw_printenv still works fine, after usage of fw_setenv the
> environment is destroyed, CRC error.
>
> I checked a lot of things, changed u-boot, devicetree, fw_setenv ...
> and finally came to the point, that it just depends on the kernel.
> Only changing the kernel makes the difference. I assume that there is
> an option not enabled. Honestly, I am lost with the differences - I
> couldn't identify the one that makes difference.
> Using an older config file, with lot more options, than it works also
> with a newer kernel.
>
> Someone has an idea, which of the million settings is my friend?
> CONFIG_CRC16 and 32 are both enabled.
The most likely answer here is that in the working kernel you have
things enabled correctly for your environment storage device (I would
guess some form of NAND) and in the not working kernel you do not have
things such as ECC scheme configured correctly, so writes do not work.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170718/447aa053/attachment.sig>
next prev parent reply other threads:[~2017-07-18 22:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-17 14:08 [U-Boot] U-Boot Tool: fw_setenv - kernel option? Arno Steffens
2017-07-18 22:55 ` Tom Rini [this message]
2017-07-21 8:37 ` Arno Steffens
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=20170718225543.GD14320@bill-the-cat \
--to=trini@konsulko.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