On 08/06/12 22:50, Tim Fletcher wrote:
> If I try and tftpboot the bin file I get the following:
> 
> Marvell>> tftp 0x800000 iconnect/openwrt-kirkwood-iconnect-u-boot.bin
> Using egiga0 device
> TFTP from server 192.168.1.1; our IP address is 192.168.1.10
> Filename 'iconnect/openwrt-kirkwood-iconnect-u-boot.bin'.
> Load address: 0x800000
> Loading: #################################################################
>           #######
> done
> Bytes transferred = 364540 (58ffc hex)
> Marvell>> go 0x800000
> ## Starting application at 0x00800000 ...
> software interrupt
> pc : [<00800dcc>]          lr : [<0060022c>]
> sp : 00600000  ip : c8012078     fp : 005ff25c
> r10: 00000000  r9 : 00000000     r8 : c8012000
> r7 : 005ff67f  r6 : 00000002     r5 : 005ffe78  r4 : 00000000
> r3 : 00000000  r2 : 00000000     r1 : 00000000  r0 : deadbeef
> Flags: nzcv  IRQs on  FIQs on  Mode USER_26
> Resetting CPU ...
> 
> I have messed about with the iconnect a fair bit and I've never managed 
> to get another uboot binary to chain boot in it.
> 
Try loading it to 0x600000 as that's the start address usually compiled-in the
u-boot binary. See
#define CONFIG_SYS_TEXT_BASE    0x00600000
in include/boards/mv-common.h
_______________________________________________
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Reply via email to