[closed] Loading and starting any uboot on dockstar fails

Before upgrading my uboot on my dockstar by writing it to NAND, i prefer to load and start it. If it works, i would write it to NAND, but it always fail with any newer or older uboot image.

Even an old uboot image i once successfully used to flash to a second dockstar years ago will not work.


i do ...

Marvell>> tftpboot 0x800000 uboot.2014.07-tld-2.dockstar.mtd0.kwb
Marvell>> go 0x800000
## Starting application at 0x00800000 ...

... and here it gets stuck



Serial output:

U-Boot 2010.06-00695-gbd23130-dirty (Aug 30 2010 - 23:04:56)
Marvell-Dockstar/Pogoplug by Jeff Doozan

SoC: Kirkwood 88F6281_A0
DRAM: 128 MiB
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Using egiga0 device
ping failed; host 192.168.x.y is not alive
Hit any key to stop autoboot: 0
Marvell>> tftpboot 0x800000 uboot.2014.07-tld-2.dockstar.mtd0.kwb
Using egiga0 device
TFTP from server 192.168.x.y; our IP address is 192.168.x.z
Filename 'uboot.2014.07-tld-2.dockstar.mtd0.kwb'.
Load address: 0x800000
Loading: T T T T T T T T ####################################
done
Bytes transferred = 524288 (80000 hex)
Marvell>> go 0x800000
## Starting application at 0x00800000 ...

(ignore 'ping failed; host 192.168.x.y is not alive', i disconnected the LAN to get the boot loader prompt and reconnected it while loading the newer uboot)



Edited 1 time(s). Last edit at 11/30/2015 03:28PM by Chin.

I think you need to set console parameters first.

Chin,

2 parts answers:

1. What Leggo said about console parameters. Basically, when you have both serial and netconsole from the same box, you should have 2 consoles (serial and net) to see all the boot activities.

2. Chainloading from u-boot 2010 to run new 2014 u-boot rarely works (too much differences structurally between 2 code bases). Besides, the command was not correct, it should be:

Marvell>> go 0x800200

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Thanks for the quick replies.

I indeed see more info over netcat, i did not expect that.

What's going wrong ?

Marvell>> tftpboot 0x800000 uboot.2014.07-tld-2.dockstar.mtd0.kwb
tftpboot 0x800000 uboot.2014.07-tld-2.dockstar.mtd0.kwb
Using egiga0 device
TFTP from server 192.168.x.y; our IP address is 192.168.x.z
Filename 'uboot.2014.07-tld-2.dockstar.mtd0.kwb'.
Load address: 0x800000
Loading: *.####################################
done
Bytes transferred = 524288 (80000 hex)
Marvell>> go 0x800200
go 0x800200
## Starting application at 0x00800200 ...
interrupt request
pc : [<0052359c>]. lr : [<0060a4d8>]
sp : 004ffeb8 ip : 00000000. fp : 00000014
r10: 00000000 r9 : 00000000. r8 : 00000000
r7 : 00000000 r6 : 00000000. r5 : 006186cc r4 : 00000000
r3 : 005234f8 r2 : 005235b8. r1 : 0060a528 r0 : 00000003
Flags: nzcv IRQs on FIQs on Mode USER_26
Resetting CPU ...

resetting ...

Chin,

As I said above, the reason is the structural differences between the 2 u-boots. Chainloading requires memory, registers,..etc to match closely.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I followed the uboot install steps in http://forum.doozan.com/read.php?3,12381

Flashed, it works.

Thanks.



Edited 2 time(s). Last edit at 11/30/2015 03:28PM by Chin.