Quote:
Originally Posted by nikkie
@toyz, I noticed that after I did the run boot_recover, on that first reboot, pushing the menu/rotate buttons actually displayed output to the terminal indicating the buttons had been pressed. They don't while in the bad flashed firmware. After it does that first boot though, it goes back to the bad firmware, so it doesn't help us too much. I tried doing a flash during that first reboot while the "Pocket Edge" logo displayed, but it didn't take. So the button connections must be wired differently for the regular edge, which explains why those of us with the bad firmware are not able to reflash.
I agree that tftpboot over usb is probably the best option. I don't have the usb-ethernet cable, and have no experience with it, so I'm just sort of fumbling about. I know some folks who might, and have been looking around for an IRC room with people with experience usinb tftpboot with embedded devices.
|
Some thoughts
1. I think by running "boot_recover" we are running the same kernel maybe root/initrd that the tablet normally would when pressing menu+rotate. I think if we pass it the correct boot args (as it would have gotten some how by the menu+rotate method) then it would go through it's re-flash procedure. I think this approach has a lot of promise. I will have to tear apart my good PE and see if I can watch bootargs based on the key presses you mentioned. (tomorrow)
2. At first I thought you must have a usb-ethernet adapter, but I'm not so sure now. Check out sections "Smart USB Peripherals ("Gadgets")" and "Most Linux PDAs: iPaq, Yopy, ..." here:
http://www.linux-usb.org/usbnet/
From a practical point of view, I think u-boot would have to have more effort to have a driver stack usb+nic+tcpip than it would usb+clevertcpip hack.