From: Luka Perkov <luka@openwrt.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] can u-boot tools fw_{printenv, setenv} work with eMMC HW partition?
Date: Sat, 24 Aug 2013 00:20:52 +0200 [thread overview]
Message-ID: <20130823222052-6976@mutt-kz> (raw)
In-Reply-To: <alpine.DEB.2.02.1308231709060.26979@oneiric>
On Fri, Aug 23, 2013 at 05:11:01PM -0400, Robert P. J. Day wrote:
> On Fri, 23 Aug 2013, Luka Perkov wrote:
>
> > On Fri, Aug 23, 2013 at 08:25:07AM -0400, Robert P. J. Day wrote:
> > > i'm sure there's a simple answer to this -- i built u-boot for my
> > > beaglebone black using the "am335x_boneblack" config, which supports
> > > saving env info to the eMMC HW partition boot1. but now that it's
> > > there, is there a way i can manipulate that info with fw_printenv and
> > > fw_setenv?
> >
> > I have put this in OpenWrt:
> >
> > https://dev.openwrt.org/browser/trunk/package/boot/uboot-envtools/patches/110-add-support-for-MTD_ABSENT.patch
> > https://dev.openwrt.org/browser/trunk/package/boot/uboot-envtools/patches/115-writing-environment-for-mtd-devices.patch
> >
> > With those two you will be able to use fw_{printenv,setenv} on MMC
> > devices.
>
> i'll get a chance to test the above this weekend, but i just want to
> make absolutely sure we're talking about the same thing. are you
> saying that with the above patches, the u-boot-tools will be able to
> manipulate an eMMC HW partition just as easily as a regular MTD
> partition?
Yes.
> and, if so, what is the format of the entry one would add
> to /etc/fw_env.config to refer to that eMMC HW partition (in this
> case, boot1)?
I have done this for imx6 wandboard in OpenWrt:
https://dev.openwrt.org/browser/trunk/package/boot/uboot-envtools/files/imx6
So example config would look like:
/dev/mmcblk0 0x60000 0x2000 0x2000
Luka
next prev parent reply other threads:[~2013-08-23 22:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 12:25 [U-Boot] can u-boot tools fw_{printenv, setenv} work with eMMC HW partition? Robert P. J. Day
2013-08-23 12:44 ` Andreas Bießmann
2013-08-23 12:57 ` Robert P. J. Day
2013-08-23 12:46 ` Stefano Babic
2013-08-23 13:25 ` Robert P. J. Day
2013-08-23 15:19 ` Luka Perkov
2013-08-23 15:28 ` Robert P. J. Day
2013-08-23 21:11 ` Robert P. J. Day
2013-08-23 22:20 ` Luka Perkov [this message]
2013-08-24 4:01 ` Robert P. J. Day
2013-08-24 11:16 ` Luka Perkov
2013-08-24 11:37 ` Robert P. J. Day
2013-08-24 13:08 ` Michael Heimpold
2013-08-24 17:33 ` Luka Perkov
2013-08-25 10:47 ` Stefano Babic
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=20130823222052-6976@mutt-kz \
--to=luka@openwrt.org \
--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