[U-Boot] Anyone using recentish u-boot on a GuruPlug?
I naively compiled a 2017.11 u-boot for GuruPlug and wrote the u-boot.kwb to nand, but that bricked the GuruPlug (should have tested with a ram version first, yes, I know).
I have a jtag for it and was able to recover, but I wonder if i did something wrong in my local build or if support just bitrotted silently. I am not familiar with .kwb and early kirkwood bootstrap, so not sure how I could debug this, besides the jtag is "slightly fragile" and using it a bit inconvenient.
Anyone used recentish u-boot on Sheeva/Guruplug lately?
Martin
I tested the RAM version now and indeed it does not work either.
With my old u-boot I get:
U-Boot 2013.10 (Oct 21 2013 - 20:54:41) Marvell-GuruPlug
SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0, egiga1 Warning: failed to set MAC address
88E1121 Initialized on egiga0 88E1121 Initialized on egiga1 Hit any key to stop autoboot: 3
while the new one:
U-Boot 2017.11 (Dec 05 2017 - 14:52:54 +0100) Marvell-GuruPlug
SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: <--- hangs here
Anyone got an idea where to look?
Martin
Hi Martin,
On Mon, Dec 18, 2017 at 8:35 AM, Martin Husemann martin@netbsd.org wrote:
I tested the RAM version now and indeed it does not work either.
With my old u-boot I get:
U-Boot 2013.10 (Oct 21 2013 - 20:54:41) Marvell-GuruPlug
SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0, egiga1 Warning: failed to set MAC address
88E1121 Initialized on egiga0 88E1121 Initialized on egiga1 Hit any key to stop autoboot: 3
while the new one:
U-Boot 2017.11 (Dec 05 2017 - 14:52:54 +0100) Marvell-GuruPlug
SoC: Kirkwood 88F6281_A1 DRAM: 512 MiB WARNING: Caches not enabled NAND: <--- hangs here
Anyone got an idea where to look?
I've got a couple of out-of-tree boards using Kirkwood SoCs (or equivalent integrated). One even uses NAND. I've just tried that board on top of 2017.11 and it boots and detects NAND (at least when loaded into RAM). I can't try u-boot/master because I haven't got myself a gcc > 6 toolchain yet.
In terms of differences between configs between my board and guruplug I don't see anything that stands out.
participants (2)
-
Chris Packham -
Martin Husemann