Bug#897671: u-boot does not work on sheevaplug
Am 10.05.2018 um 20:10 schrieb Vagrant Cascadian: On 2018-05-09, Markus Krebs wrote: Am 09.05.2018 um 14:33 schrieb klaus.go...@theobroma-systems.com: On 09.05.2018, at 10:19, Markus Krebs <markus.kr...@web.de> wrote: Am 08.05.2018 um 22:54 schrieb Vagrant Cascadian: On 2018-05-08, Vagrant Cascadian wrote: On 2018-05-05, Tom Rini wrote: On Sat, May 05, 2018 at 04:04:08PM -0700, Vagrant Cascadian wrote: 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. ... And setting SYS_THUMB_BUILD=y as well as disabling EFI_LOADER gets it down to 432k! Thanks to beeble for the suggestion. Anyone who has a sheevaplug can test that it actually boots with CONFIG_SYS_THUMB_BUILD=y enabled? I could test it, but I don't know the config-file where I can change those options (EFI_LOADER, CONFIG_SYS_THUMB_BUILD). Both are Kconfig options. So just disable it via menuconfig or in your .config file Thanks. The modified u-boot (size indeed 441592 bytes only) boots! Can you try with CONFIG_SYS_THUMB_BUILD=y only (e.g. leave EFI_LOADER at the default). Yes, it works (size now 473740 bytes)!
Bug#897671: [U-Boot] Bug#897671: u-boot does not work on sheevaplug
Am 09.05.2018 um 14:33 schrieb klaus.go...@theobroma-systems.com: On 09.05.2018, at 10:19, Markus Krebs <markus.kr...@web.de> wrote: Am 08.05.2018 um 22:54 schrieb Vagrant Cascadian: On 2018-05-08, Vagrant Cascadian wrote: On 2018-05-05, Tom Rini wrote: On Sat, May 05, 2018 at 04:04:08PM -0700, Vagrant Cascadian wrote: 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. ... I've added the maintainer to the list as well. I would suggest looking for things to trim out, perhaps CMD_MEMTEST ? Thanks for the suggestsions. CMD_MEMTEST wasn't present, but disabling EFI_LOADER made u-boot 2018.05 go from 592k down to 548k. There's not a *lot* left to disable in the config, but that's a significant start... And setting SYS_THUMB_BUILD=y as well as disabling EFI_LOADER gets it down to 432k! Thanks to beeble for the suggestion. Anyone who has a sheevaplug can test that it actually boots with CONFIG_SYS_THUMB_BUILD=y enabled? I could test it, but I don't know the config-file where I can change those options (EFI_LOADER, CONFIG_SYS_THUMB_BUILD). Both are Kconfig options. So just disable it via menuconfig or in your .config file Thanks. The modified u-boot (size indeed 441592 bytes only) boots!
Bug#897671: [U-Boot] Bug#897671: u-boot does not work on sheevaplug
Am 08.05.2018 um 22:54 schrieb Vagrant Cascadian: On 2018-05-08, Vagrant Cascadian wrote: On 2018-05-05, Tom Rini wrote: On Sat, May 05, 2018 at 04:04:08PM -0700, Vagrant Cascadian wrote: 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. ... I've added the maintainer to the list as well. I would suggest looking for things to trim out, perhaps CMD_MEMTEST ? Thanks for the suggestsions. CMD_MEMTEST wasn't present, but disabling EFI_LOADER made u-boot 2018.05 go from 592k down to 548k. There's not a *lot* left to disable in the config, but that's a significant start... And setting SYS_THUMB_BUILD=y as well as disabling EFI_LOADER gets it down to 432k! Thanks to beeble for the suggestion. Anyone who has a sheevaplug can test that it actually boots with CONFIG_SYS_THUMB_BUILD=y enabled? I could test it, but I don't know the config-file where I can change those options (EFI_LOADER, CONFIG_SYS_THUMB_BUILD).
Bug#897671: u-boot does not work on sheevaplug
Am 05.05.2018 um 20:36 schrieb Markus Krebs: Am 05.05.2018 um 20:35 schrieb Martin Michlmayr: * Markus Krebs <markus.kr...@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 0x2 /* 128k */ #define CONFIG_ENV_ADDR 0x8 #define CONFIG_ENV_OFFSET 0x8 /* env starts here */ but the environment shouldn't start at 0x8 when u-boot.kwb > 524 KB; in this case 'saveenv' overwrites u-boot (?). Changing 0x8 to 0xa helps ; I compiled a u-boot.kwb from the so-modified sources, and now I can start Debian fine. Markus
Bug#897671: u-boot does not work on sheevaplug
Am 05.05.2018 um 20:35 schrieb Martin Michlmayr: * Markus Krebs <markus.kr...@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.
Bug#897671: u-boot does not work on sheevaplug
I got it. Indeed it has to to with the size of u-boot.
The space in the command in your instructions "nand erase 0x0 0x8"
is too small now for u-boot.kwb. I tried "nand erase 0x0 0xc0"
(which should still be ok, as mtd0 is 1 Megabyte) and everything works
fine (flashing with ${filesize} afterwards of course).
This works when flashing from u-boot. For flashing from Debian maybe
"/etc/fw_env.config" must be changed? Or the commands/values in
/usr/share/doc/u-boot/README.Debian which are
sudo flash_erase /dev/mtd0 0 0
sudo nandwrite -p /dev/mtd0 /usr/lib/u-boot/sheevaplug/u-boot.kwb
I don't know how, though. Maybe you can direct me?
Am 05.05.2018 um 14:41 schrieb Markus Krebs:
It gives the same type of error when flashing:
NAND write: device 0 offset 0x0, size 0x934cc
nand_write_ecc: Attempt to write not page aligned data
0 bytes written: ERROR
Am 05.05.2018 um 11:13 schrieb Martin Michlmayr:
Can you try:
http://ftp.debian.org/debian/pool/main/u/u-boot/u-boot_2018.05~rc3+dfsg-1_armel.deb
Bug#897671: u-boot does not work on sheevaplug
It gives the same type of error when flashing: NAND write: device 0 offset 0x0, size 0x934cc nand_write_ecc: Attempt to write not page aligned data 0 bytes written: ERROR Am 05.05.2018 um 11:13 schrieb Martin Michlmayr: Can you try: http://ftp.debian.org/debian/pool/main/u/u-boot/u-boot_2018.05~rc3+dfsg-1_armel.deb
Bug#897671: u-boot does not work on sheevaplug
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 0x080 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 0x080 0x0 0x8
0x8 = 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 0x8 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
Bug#897671: u-boot does not work on sheevaplug
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 0x080 0x0 0x8
0x8 = 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 0x8 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
Bug#897671: u-boot does not work on sheevaplug
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 [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 0x080 0x0 0x8
0x8 = 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 0x8 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
Bug#897671: u-boot does not work on sheevaplug
Package: u-boot Version: 2018.03+dfsg1-2 Severity: critical Justification: breaks the whole system Dear Maintainer, flashing the newest u-boot.kwb on sheevaplug makes the system unbootable. I tried flashing out of Debian as well as from u-boot - no difference. One must flash a different u-boot via OpenOCD to bring the system back to life again. The u-boot.kwb provided at https://forum.doozan.com/read.php?3,12381 works. -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 4.15.0-3-marvell Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- no debconf information Markus
