Control: tags 869680 moreinfo On 2017-07-25, John Forecast wrote: > /etc/fw_env.config was not present so I copied > /usr/share/doc/u-boot-tools/examples/linkstation_pro_live.config to > /etc/fw_env.config. This allowed me to see the current environment variables > with fw_printenv but any attempt to modify an environment variable with > fw_setenv generated the error: > > MTD erase error on /dev/mtd2: Invalid argument > Error: can't write fw_env to flash > > /etc/fw_env.config contained a single entry: > > /dev/mtd2 0x3F000 0x1000 0x1000
It looks like the linkstation mini currently has the same config... > This was similar to the entry I had seen in Jessie except that there was only > a single device for all 3 regions. I changed the offset to 0x00000: > > /dev/mtd2 0x00000 0x1000 0x1000 I don't have this device, so it's a bit hard to verify on my end. It may be possible that mainline u-boot and vendor-supplied u-boot require different settings, in which case I'd like to at least document both settings, if someone can confirm what the various values were and in which cases they apply, that would be helpful. The Debian packages do not currently build the "lsxhl" target, which appears to be the appropriate mainline target for this board, but in mainline u-boot, include/configs/lsxhl.h has: #define CONFIG_ENV_SIZE 0x10000 /* 64k */ #define CONFIG_ENV_OFFSET 0x70000 /* env starts here */ I guess I can add both, leaving both commented, but I'd like to know in what contexts which values are appropriate, so that we can include useful comments. live well, vagrant
signature.asc
Description: PGP signature
