All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Alexis Ciavaldini <pierre-alexis@ciavaldini.fr>
To: "u-boot@lists.denx.de" <u-boot@lists.denx.de>
Subject: u-boot saveenv to redundant fat does not persist env
Date: Tue, 27 Jul 2021 16:44:20 +0200	[thread overview]
Message-ID: <7EB54645-1F55-4BB0-8E58-8B74BC8F2452@getmailspring.com> (raw)

Hi,

I'm trying to integrate u-boot in our project that is a custom scripted build without yocto, for use with mender.
The complete discussion can be found here : https://hub.mender.io/t/pi3-usb-boot-support/595/54?u=peac
The problem is that when issuing saveenv in u-boot, it responds with "Saving Environment to FAT... OK" but then using fw_printenv in the booted linux, does not show saved variables.

The system currently boots because i've tricked it by getting the compiled-in env over uart (env print -a) and made a uboot.env using mkenvimage manually to enable fw_printenv to work.
I've noticed that when deleting "/boot/u-boot/uboot.env", u-boot's saveenv does not re-create it, so it seems to me that saveenv does not write uboot.env.
Here's the complete project files : https://git.iostud.io/cosmos/u-boot/-/tree/cosmos
relevant modified files are:
- configs/rpi_4_32b_defconfig
- include/config_mender_defines.h
- include/env_mender.h
- include/configs/rpi.h
- include/env_default.h
- include/config_mender.h

Any help or investigating direction would be greatly appreciated.
Thank you,
Pierre-Alexis Ciavaldini

             reply	other threads:[~2021-07-28 12:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-27 14:44 Pierre-Alexis Ciavaldini [this message]
2021-07-28 14:39 ` u-boot saveenv to redundant fat does not persist env Tom Rini
2021-07-28 14:41   ` Pierre-Alexis Ciavaldini
2021-07-28 15:23     ` Tom Rini
2021-07-28 15:25       ` Pierre-Alexis Ciavaldini
2021-07-28 15:32         ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2021-07-16 12:01 Pierre-Alexis Ciavaldini

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=7EB54645-1F55-4BB0-8E58-8B74BC8F2452@getmailspring.com \
    --to=pierre-alexis@ciavaldini.fr \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.