Re-reading this, I realize that I said “0x80000” for the environment location of legacy u-boot. But when I went to test it, the true value turned out to be “0xa0000”.
Sorry for the confusion. The latter value (0xa0000) is correct. Rick PS: Just out of curiosity, was there a reason behind the change? Or was it just one of those things that “seemed like a good idea at the time” ? On Apr 16, 2016, at 6:04 PM, Rick Thomas <rbtho...@pobox.com> wrote: > > On Apr 15, 2016, at 12:29 PM, Vagrant Cascadian <vagr...@debian.org> wrote: > >> On 2016-04-14, Rick Thomas wrote: >>> The directory /usr/share/doc/u-boot-tools/examples/ has example .config >>> files >>> for a variety of devices, but none for the OpenRD base, client or ultimate. >> ... >>> Oh, and BTW, the lastest u-boot puts the environment at 0x60000, while >>> legacy >>> versions put it at 0x80000, so it would be nice to reflect that (as was >>> done for sheevaplug -- thanks!) in the example .config file. >> >> If you could provide a tested, working config, I can include it, but I >> have no way of testing it myself. >> >> >> live well, >> vagrant > > Here you go: > > ============/usr/share/doc/u-boot-tools/examples/openrd.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 > # Legacy u-boot versions: > #/dev/mtd0 0xa0000 0x20000 0x20000 > > # New u-boot versions: > /dev/mtd0 0x60000 0x20000 0x20000 > ============ cut here =============== > > Tested and working on openrd client and ultimate hardware for both versions > of u-boot: > Legacy: U-Boot 1.1.4 (May 18 2009 - 13:33:10) Marvell version: 3.4.16 > New: U-Boot 2016.03+dfsg1-3 (Apr 04 2016 - 18:23:06 +0000) > > Rick Thomas > > PS: You may add my name as a tester if you want.
