Hi Tim, great news, I'd would be nice if you can help so we can get U-Boot for this board tested.
On 06/06/12 15:24, Tim Fletcher wrote: > I have access to an iConnect, what is it that you need testing? OpenWrt can build the U-Boot loader for some boards, including the kirkwood platform. So board-specific definitions for the iconnect were added to the uboot-kirkwood package, but they didn't get upstream till now. In order to update U-Boot to version 2012.04.01, I forward-ported the board support for the iconnect by applying the same changes to it which were also committed to similar devices like the SheevaPlug in the U-Boot sources. So this should be tested before it can go upstream. Basically, the other OpenWrt-supported board, the dockstar, already made it's way into the U-Boot sources, so patch 2181 is obsoleted by that. After applying the 3 patches (see below) to trunk, you will have the option to build uboot for the iconnect board. Please test the resulting image by chain-loading it with your current U-Boot (risk free). For this you will need the device hooked up via serial console, and enter the bootloader after power-on, the procedure looks like this: Marvell>> setenv ipaddr 192.168.1.2 Marvell>> setenv serverip 192.168.1.1 Marvell>> tftp 0x600000 openwrt-kirkwood-iconnect-u-boot.bin Using egiga0 device TFTP from server 192.168.1.1; our IP address is 192.168.1.2 Filename 'openwrt-kirkwood-iconnect-u-boot.bin'. Load address: 0x600000 Loading: ########################## done Bytes transferred = 372440 (5aed8 hex) Marvell>> go 0x600000 ## Starting application at 0x00600000 ... U-Boot 2012.04.01 (Jun 07 2012 - 00:26:14) ... The got the newly build U-Boot loaded and you can play with it a bit to see if it's working properly. Test loading and booting something from NAND and from TFTP, S-ATA may or may not work, USB should work (try 'usb start', then mount a usb storage device and loading a kernel) After testing the bootloader A LOT and making sure that you won't brick stuff, you may or may not decide to flash it onto the NAND. You may take this as an inspiration, but check it thoroughly and don't blame me if things go wrong: Marvell>> printenv check mtdparts for the name of the u-boot partition (usually either 'uboot' or 'u-boot') and use that name for nand erase.part and nand write. setenv ipaddr 192.168.1.2 setenv serverip 192.168.1.1 tftp 0x600000 openwrt-kirkwood-iconnect-u-boot.kwb nand erase.part uboot nand write 0x600000 uboot 0x80000 reset > The patch from http://patchwork.openwrt.org/patch/734/ ? No, this thread is about about http://patchwork.openwrt.org/patch/2180/ http://patchwork.openwrt.org/patch/2181/ http://patchwork.openwrt.org/patch/2182/ _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
