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/11... https://dev.openwrt.org/browser/trunk/package/boot/uboot-envtools/patches/11...
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