Control: tags 803497 moreinfo Control: tags 821056 moreinfo On 2015-10-30, William Hay wrote: > I'm trying to migrate an existing (mixed armel/armhf) system from a > CuBox to a BananaPro. I used dd to copy the appropriate > u-boot-sunxi-with-spl.bin to an offset of 8k from the start of the > sdcard. > > I copied the fw_env.config settings from the following page: > https://blog.night-shade.org.uk/2014/01/fw_printenv-config-for-allwinner-devices/ > > I ran fw_printenv expecting it to display the u-boot environment > embedded in the .bin file. > > Instead it prints the error about Bad CRC mentioned at the bottom of > the page. Followed by what I assume is a u-boot environment embedded > in fw_printenv.
Yeah, without an fw_env.config, fw_printenv defaults to some built-in values. > Poking at the .bin file I find something that looks like a u-boot > environment at a much lower offset but I lack the knowledge to work > backwards from the file to fw_env.config values. > > It would be useful if the u-boot-sunxi package came with documentation > of appropriate fw_env.config settings for each variant it supports. In general, since there are so many platforms in u-boot, details for specific boards are provided by folks who have those boards to test and verify. Allwinner/sunxi boards are a little difficult, as u-boot-sunxi and u-boot mainline may have different offsets, and given boards may also have different offsets. So documenting the right offsets may depend on what version of u-boot installed. There are a number of example fw_env.config shipped in the u-boot-tools package, but it is not comprehensive for all the supported platforms. live well, vagrant
signature.asc
Description: PGP signature
