I analyzed the the calls with strace and found one difference:
although both read the same /etc/fw_env.config, the one kernel calls
ioctl(4, MIXER_READ(1) or MEMGETINFO, {type=MTD_NORFLASH,
flags=MTD_WRITEABLE|MTD_BIT_WRITEABLE, size=0x10000, erasesize=0x1000,
writesize=0x1, oobsize=0, padding=0}) = 0
and the other
ioctl(4, MIXER_READ(1) or MEMGETINFO, {type=MTD_NORFLASH,
flags=MTD_WRITEABLE|MTD_BIT_WRITEABLE, size=0x10000, erasesize=0x10000,
writesize=0x1, oobsize=0, padding=0}) = 0
So the erasesize differs!!!
How can this be? Just depends on kernel options?
Best regards
Arno
> Gesendet: Montag, 17. Juli 2017 um 10:27 Uhr
> Von: [email protected]
> An: [email protected]
> Betreff: [meta-xilinx] uboot-utils fw_setenv ends up with wrong CRC in
> environment
>
> With update to yocto2.3 I started using the vanilla 4.9 kernel. (currently
> out of tree, as I don't know howto build a recipe to build from kernel.org
> sources).
> This works for me with minor changes (backporting the spi-zynq-qspi.c).
>
> But I found a strange problem. The tool "fw_setenv" (out of u-boot utils)
> doesn't work anymore - after usage I get a destroyed environment.
> ("fw_readenv works - but only until usage of fw_setenv).
> I checked a few things, but I end up, that just changing the kernel is the
> issue (neither u-boot, nor the utils, nor the devicetree). I am wonding what
> can be the reason for that? Is some kernel setting missing?
> --
> _______________________________________________
> meta-xilinx mailing list
> [email protected]
> https://lists.yoctoproject.org/listinfo/meta-xilinx
>
--
_______________________________________________
meta-xilinx mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-xilinx
