Hello U-Boot.
Markus Krebs discovered that the sheevaplug target has again grown and installation overlaps where the u-boot env is saved since u-boot ~2017.09. Running saveenv overwrites u-boot, and installing u-boot overwrites any prior environment settings.
More detail on the bug report in Debian:
https://bugs.debian.org/897671
We don't carry any patches for the sheevaplug u-boot target in Debian, so this is likely also an issue upstream. Who are the current maintainers for sheevaplug in u-boot upstream?
A brief summary of the current findings:
On 2018-05-05, Markus Krebs wrote:
Am 05.05.2018 um 20:36 schrieb Markus Krebs:
Am 05.05.2018 um 20:35 schrieb Martin Michlmayr:
- Markus Krebs Markus.Krebs@web.de [2018-05-05 20:32]:
I got it. Indeed it has to to with the size of u-boot.
Does it boot?
Yes it does.
... and no longer so, when I "saveenv" :-(
I downloaded u-boot via git; I guess that the config for u-boot for sheevaplug is already broken upstream (in sheevaplug.h):
#define CONFIG_ENV_SIZE 0x20000 /* 128k */ #define CONFIG_ENV_ADDR 0x80000 #define CONFIG_ENV_OFFSET 0x80000 /* env starts here */
but the environment shouldn't start at 0x80000 when u-boot.kwb > 524 KB; in this case 'saveenv' overwrites u-boot (?). Changing 0x80000 to 0xa0000 helps ; I compiled a u-boot.kwb from the so-modified sources, and now I can start Debian fine.
It looks like it was bumped from 0x60000 to 0x80000 in 2014:
http://git.denx.de/?p=u-boot.git;a=commit;h=4dfb0e4d3e75763d6fbe8788316bea9b...
If 0x80000 isn't enough, there might be some features in the config to experiment with removing, or it may need to be bumped again.
Not sure what the best coarse of action is.
live well, vagrant