not sure whether this is more appropriately a u-boot question but
i'll ask here to start with.
i'm using the current (git) version of u-boot on my BBB, where the
new BBB-specific configuration of "am335x_boneblack_config" lets me
store the u-boot environment in the eMMC hardware partition "boot1".
this not only lets me save u-boot environment information even if i'm
booting off of SD card, but it lets me see the env info after i've
booted by hexdump'ing that HW partition:
# hexdump -C /dev/mmcblk1boot1
00000000 fc d7 b6 21 61 72 63 68 3d 61 72 6d 00 62 61 75 |...!arch=arm.bau|
00000010 64 72 61 74 65 3d 31 31 35 32 30 30 00 62 6f 61 |drate=115200.boa|
00000020 72 64 3d 61 6d 33 33 35 78 00 62 6f 61 72 64 5f |rd=am335x.board_|
00000030 6e 61 6d 65 3d 41 33 33 35 42 4e 4c 54 00 62 6f |name=A335BNLT.bo|
00000040 61 72 64 5f 72 65 76 3d 30 41 35 43 00 62 6f 6f |ard_rev=0A5C.boo|
00000050 74 5f 66 64 74 3d 74 72 79 00 62 6f 6f 74 61 72 |t_fdt=try.bootar|
00000060 67 73 3d 63 6f 6e 73 6f 6c 65 3d 74 74 79 4f 30 |gs=console=ttyO0|
... etc ...
however, i've used OE to build my system and added the
u-boot-fw-utils package, which gives me the utilities fw_printenv and
fw_setenv to allegedly manipulate that u-boot env info from the
command line, but the problem is that i don't know what to place in
the config file /etc/fw_env.config to refer to that eMMC HW partition.
normally, that file points at a partition and also has to specify
flash properties of device offset, flash sector size and so on, but
none of that seems relevant here given that this is a different kind
of partition.
can this even be done? do the u-boot env utilities have the
capability to work with an eMMC HW partition like boot1?
rday