From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] saveenv not working with CONFIG_ENV_IS_IN_UBI
Date: Thu, 23 Feb 2017 07:57:03 +0100 [thread overview]
Message-ID: <58AE87BF.6050507@denx.de> (raw)
In-Reply-To: <CAN-NoH1BDXSoLk85nundQHi6KaEihj_ahv+FxqubjUqyD4gK6g@mail.gmail.com>
Hello Richard,
Am 20.02.2017 um 22:38 schrieb Richard Cagley:
> I am unable to have my uboot environment variable persist when using saveenv.
>
> I have these configs set
> #define MTDIDS_DEFAULT "nand0=xilinx_nand"
> #define MTDPARTS_DEFAULT \
> "mtdparts=xilinx_nand:" \
> "8M(boot)ro," \
> "16M(env-boot)," \
> "20M(itb)," \
> "-(root)"
> #define CONFIG_ENV_IS_IN_UBI
> #define CONFIG_ENV_UBI_PART "env-boot"
> #define CONFIG_ENV_UBI_VOLUME "u-boot-env1"
> #define CONFIG_ENV_UBI_VOLUME_REDUND "u-boot-env2"
>
> Once in u-boot I do something along these lines:
> mtdparts default
> nand erase.part env-boot
> ubi part env-boot
> ubi create u-boot-env1 0x20000 dynamic
> ubi create u-boot-env2 0x20000 dynamic
> setenv foo 1
> saveenv
> saveenv
> reset
> printenv foo
> ## Error: "foo" not defined
Can you provide some more informations?
On which hw?
Is the board support for your hw in mainline?
Does UBI support work at all on your hw?
Please provide a full log, may with ubi debug enabled.
Thanks!
bye,
Heiko
>
> thanks
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
prev parent reply other threads:[~2017-02-23 6:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-20 21:38 [U-Boot] saveenv not working with CONFIG_ENV_IS_IN_UBI Richard Cagley
2017-02-23 6:57 ` Heiko Schocher [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=58AE87BF.6050507@denx.de \
--to=hs@denx.de \
--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