Hi All, First off, thanks to Luka et al. for maintaining u-boot for the iconnect. This is my first venture into bootloader land (I do not have a JTAG setup) and I am a little bit leery of jumping off of the cliff without any way to unbrick! Having reports of working versions on the same device is quite a good safety net for me!
I've been trying the u-boot version from http://downloads.openwrt.org/snapshots/trunk/kirkwood/openwrt-kirkwood-iconnect-u-boot.kwb on an iconnect that (used to) boot from a USB hard drive under the stock version of u-boot. My problem is that when I do a "usb start" (in addition to fairly frequent timeouts which can be worked around) I find the message "READ_CAP ERROR" from u-boot, and ext2load just hangs. If it matters to u-boot, I'm actually trying to boot a Debian distro, with known-working uInitrd and uImage on an ext2 partition. Some of the u-boot environment is from the openWRT version, but some of it is from my older config (saved in a text file). I'm cutting and pasting a transcription of the actual boot and errors below. --- begin log --- U-Boot 2012.04.01 (Jul 24 2012 - 15:38:47) Iomega iConnect Wireless SoC: Kirkwood 88F6281_A0 DRAM: 256 MiB WARNING: Caches not enabled NAND: 512 MiB In: serial WARNING: Caches not enabled NAND: 512 MiB In: serial Out: serial Err: serial Net: egiga0 Hit any key to stop autoboot: 0 iconnect => printenv arcNumber=1682 baudrate=115200 boot=bootm 0x2000000 0x4500000 boot_size=0x1f400000 boot_start=0x980000 bootargs=console=ttyS0,115200 mtdparts=orion_nand:0xc0000@0x0(uboot),0x20000@0xa0000(env),0x300000@0x100000(zImage),0x300000@0x540000(initrd),0x1f400000@0x980000(boot) rootdelay=10 root=/dev/mapper/connectovg-rootlv bootcmd=run bootcmd_usb; bootm 0x00800000 0x01100000; reset bootcmd_usb=usb start; ext2load usb 0:1 0x01100000 /uInitrd; ext2load usb 0:1 0x00800000 /uImage bootdelay=3 env_size=0x20000 env_start=0xa0000 ethact=egiga0 ethaddr=00:D0:B8:0D:F0:E6 flash_load=run make_boot_args load1 load2 boot initrd_size=0x300000 initrd_start=0x540000 kernel_size=0x300000 kernel_start=0x100000 load1=nand read.e 0x2000000 $(kernel_start) $(kernel_size) load2=nand read.e 0x4500000 $(initrd_start) $(initrd_size) make_boot_args=setenv bootargs console=ttyS0,115200 mtdparts=orion_nand:;setenv bootargs $(bootargs)$(uboot_size)@$(uboot_start)(uboot),;setenv bootargs $(bootargs)$(env_size)@$(env_start)(env),;setenv bootargs $(bootargs)$(kernel_size)@$(kernel_start)(zImage),;setenv bootargs $(bootargs)$(initrd_size)@$(initrd_start)(initrd),;setenv bootargs $(bootargs)$(boot_size)@$(boot_start)(boot) stderr=serial stdin=serial stdout=serial uboot_size=0xc0000 uboot_start=0x0 x_bootargs=console=ttyS0,115200 mtdparts=orion_nand:1M(u-boot),3M@1M(kernel),32M@4M(rootfs),475M@36M(data) x_bootargs_root=root=/dev/mtdblock2 rw rootfstype=jffs2 x_bootcmd_kernel=nand read 0x6400000 0x100000 0x300000 x_bootcmd_usb=usb start Environment size: 1582/131068 bytes iconnect => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 3 USB Device(s) found scanning bus for storage devices... EHCI timed out on TD - token=0x2008d80 EHCI timed out on TD - token=0x2008d80 READ_CAP ERROR 2 Storage Device(s) found iconnect => usb start (Re)start USB... USB: Register 10011 NbrPorts 1 USB EHCI 1.00 scanning bus for devices... 3 USB Device(s) found scanning bus for storage devices... READ_CAP ERROR 2 Storage Device(s) found iconnect => ext2load usb 0:1 0x01100000 /uInitrd --- end log --- The device needs to be powered off and back on to come back from this hang. I've setup the environment above to be able to boot into the still stock iconnect firmware (other than the re-flashed u-boot and my environment, of course) using the command "run flashload". This works after setting another environment variable "setenv machid 692" so that I can get into the stock iconnect firmware. Strangely enough, the usb disk is NOT found by linux even in this environment! I haven't re-created my entire old u-boot environment variable setings yet, but am suspicious that this anomalous usb behavior (even when booted) is somehow related to u-boot. Incidently, without getting access to that disk, it will not be simple for me to find my (hopefully correct) version of the old, stock, u-boot binary. Is that lying around anywhere on the net? Any advice as to how best to proceed would be greatly appreciated! Cheers, Frank Horowitz _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
