On Jan 5, 2016, at 10:12 PM, Vagrant Cascadian <vagr...@debian.org> wrote:
>>> There are a couple bugs reported against u-boot which may be relevent: >>> >>> https://bugs.debian.org/781874 >>> https://bugs.debian.org/782293 For what it’s worth, by grepping about in /dev/mtd0, I located what seems to be the place where the u-boot environment is located. It’s 0x80000. And to verify that, I have changed /etc/fw_env.config to > # MTD device name Device offset Env. size Flash sector size > /dev/mtd0 0x80000 0x20000 0x20000 then I did “fw_printenv". Guess what! No message about bad CRC or default environment, and the environment that it printed matched the output of “printenv” under u-boot. So I guess it’s all explained by https://bugs.debian.org/781874 . I’ve certainly learned a lot! Enjoy! Rick PS: I’ll test the experimental u-boot u-boot-tools stuff as soon as you approve my proposed testing procedure. And I’ll also agree to test any new versions you point me at — I can’t guarantee 24-hour turn-around time, but I’ll certainly try!
