fw_printenv resulting in bad crc, using default environment

[Anatolij Gustschin]

On Wed, 5 Feb 2020 10:09:40 +0000
Robert Varga robert.varga at getinge.com wrote:
...
> The content of /etc/fw_env.config is as follows:
> cat /etc/fw_env.config
> # Configuration file for fw_(printenv/setenv) utility.
> # Up to two entries are valid, in this case the redundant
> # environment sector is assumed present.

The above statement is a hint.

> # Notice, that the "Number of sectors" is ignored on NOR and SPI-dataflash.
> # Futhermore, if the Flash sector size is ommitted, this value is assumed to
> # be the same as the Environment size, which is valid for NOR and SPI-dataflash
> 
> # THIS IS VALID FOR TQMa6x eMMC-card only!
> # eMMC Block device access
> /dev/mmcblk00x1000000x2000
> # if using with redundant env
> /dev/mmcblk00x1020000x2000

Comment out the above line and try again.

...
> hexdump -C -s 0x100000 -n 8192 /dev/mmcblk0
> 00100000  95 fc 63 38 61 64 64 63  6d 61 3d 73 65 74 65 6e  |..c8addcma=seten|
> 00100010  76 20 62 6f 6f 74 61 72  67 73 20 24 7b 62 6f 6f  |v bootargs ${boo|

It looks like this U-Boot configuration does not use redundant environment,
so you must have only one entry in /etc/fw_env.config.

--
Anatolij