On my Cubox-i4Pro when I run fw_printenv (from the u-boot-tools package) it says “Warning: Bad CRC, using default environment”.
The “default environment” is clearly *not* the environment that u-boot is using to boot the box. At least the “ethaddr” variable in that environment is clearly a fake one as show here: > root@cube:~# fw_printenv ethaddr > Warning: Bad CRC, using default environment > ethaddr=00:00:11:22:33:44 This is definitely not the ethernet address that the box is using for dhcp. A couple of more data points that may shed light on this: > root@cube:~# cat /etc/fw_env.config > # Configuration file for fw_(printenv/saveenv) utility. > # Up to two entries are valid, in this case the redundant > # environment sector is assumed present. > # > # XXX this configuration might miss a fifth parameter for the "Number of > # sectors" > > # MTD device name Device offset Env. size Flash sector size > /dev/mmcblk1p1 0x80000 0x2000 > root@cube:~# cat /usr/share/doc/u-boot-tools/examples/mx6cuboxi.config > # Configuration file for fw_(printenv/saveenv) utility. > # Up to two entries are valid, in this case the redundant > # environment sector is assumed present. > # > # XXX this configuration might miss a fifth parameter for the "Number of > # sectors" > > # MTD device name Device offset Env. size Flash sector size > /dev/mmcblk0 0x80000 0x2000 FWIW the micro-SD card on this box is identified as /dev/mmcblk1 — not as either /dev/mmcblk0 or /dev/mmcblk1p1. Does this represent a bug in u-boot-tools, or am I mis-interpreting something? Enjoy! Rick