I can report now:
- u-boot up to 2017.07+dfsg1-3 works fine.
- 2017.09+dfsg1-3: can be flashed, but after reset usb doesn't work
properly:
=> usb start
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices...
[and no more reaction]
- 2017.11+dfsg1-3: cannot even be flashed:
=> nand write 0x0800000 0x0 ${filesize}
NAND write: device 0 offset 0x0, size 0x8f924
NAND write to offset 0 failed -5
0 bytes written: ERROR
Markus
Am 04.05.2018 um 21:02 schrieb Markus Krebs:
Just thinking: Maybe it does indeed have something to do with the size
of u-boot. The one from bodhi is 524 KB, whereas the Debian one is 599 KB.
Am 04.05.2018 um 20:40 schrieb Markus Krebs:
Interesting thoughts, but: I tried again flashing both from within
Debian and from u-boot (using ${filesize}). $filesize is accepted and
flashing works, but the plug doesn't boot.
Flashing (again with $filesize, just to confirm it works) the u-boot
from bodhi-linux (the one I was referring to) works, so it must be the
u-boot.kwb in Debian which is broken.
Am 04.05.2018 um 19:11 schrieb Martin Michlmayr:
* Vagrant Cascadian <vagr...@debian.org> [2018-05-04 08:40]:
I do recall that there was some incompatible change regarding the
environment size on some of the marvell platforms, as u-boot.kwb grew
large enough to overwrite the environment section.
Uh, this might not be an u-boot issue then but a problem with my
upgrade instructions (although Markus said he tried to do the update
from within Debian too, so maybe not).
https://www.cyrius.com/debian/kirkwood/sheevaplug/uboot-upgrade/ says:
nand write 0x0800000 0x0 0x80000
0x80000 = 524288
but:
-rw-r--r-- 1 tbm tbm 599684 Apr 2 03:20
usr/lib/u-boot/sheevaplug/u-boot.kwb
so we're not writing the whole binary to flash.
The reason I used 0x80000 instead of ${filesize} is because very old
u-boot versions (as originally shipped on the SheevaPlug) have
problems with ${filesize}:
NAND write: device 0 offset 0x0, size 0x68ab0
nand_write_ecc: Attempt to write not page aligned data
0 bytes written: ERROR
