On Fri, Jun 08, 2012 at 08:50:46PM +0100, Tim Fletcher wrote:
> On 08/06/12 02:32, Luka Perkov wrote:
> >Board owners please test this patch and give feedback for the boards:
> >
> > * sheevaplug
> > * dockstar
> > * iconnect
> >
> >You can use kwboot tool like this (run as root):
> >
> >./bin/kirkwood/u-boot-kwboot/kwboot -b
> >bin/kirkwood/openwrt-kirkwood-ib62x0-u-boot.kwb -p /dev/ttyUSB0
> >
> >As soon as it is finished run your favorite terminal like usual. With
> >kwboot you can not brick your boards. It sends bootloader via serial and
> >does not touch the flash... You can recover board with no bootloader
> >using this tool.
>
> My iConnect doesn't seem to do anything with this tool, all I get is
>
> Sending boot message. Please reboot the target...- and a spinning
> cursor, the iConnect doesn't boot.
>
> According to strace kwboot continues in a loop doing
>
> ioctl(3, TCFLSH, 0x2) = 0
> write(3, "\273\21\"3DUfw", 8) = 8
> ioctl(3, TCSBRK, 0x1) = 0
> select(4, [3], NULL, NULL, {0, 50000}) = 0 (Timeout)
Ok. On older kirkwood boards this does not work. Read about it here:
http://lists.denx.de/pipermail/u-boot/2012-May/123866.html
> 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.
This is normal if you try to run it that way. Plase test (and experiment)
with this values in package/uboot-kirkwood/files/include/configs/iconnect.h:
#define CONFIG_SYS_TEXT_BASE 0x800000
#define CONFIG_SYS_RAMBOOT
Then try "go 0x800000"
Luka
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
