On Thu, Jul 26, 2012 at 11:58:48PM +0100, Tim Fletcher wrote: > On 26/07/12 00:43, Frank Horowitz wrote: > >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! > > I have an iconnect with the new uboot on too, and the usb does seem > more picky about some usb storage devices. > > The disk should work in any other linux system and the way that I > have recovered from this is to copy the uImage and uInitrd off on to > a tftp server and just boot it with tftp. > > When this happened to me I found that cleaning and reseating the usb > connection helped but that might just be coincidence, I always use > the single usb port for the boot device too this might make no > difference mind.
Frank, did kwboot work on your device? I do not have iConnect device. I just cleaned up the code and prepared it for upstream. Regards, Luka _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel