u-boot area was erased. openmoko can't power on.
andy at openmoko.com
Wed Jan 9 12:33:20 CET 2008
-----BEGIN PGP SIGNED MESSAGE-----
Somebody in the thread at some point said:
> Sometimes I used bebug board.
> Current my openmoko can’t power on.
> Openmoko must detect power using debug board.
> My openmoko can’t power on so my openmoko can’t see boot menu.
> Battery is full but I can’t anything.
"Power on" and "boot" are different things, if you erased U-Boot then it
is expected the device can't do much in the way of booting when you give
it power, but still it probably did "power on" and try to do something.
There is no boot menu any more for your device because the boot menu is
sent by the U-Boot that you erased.
But it can still be okay if you have a debug board: the debug board has
a Jtag connection to the device as well as serial. You can use the
information in the links that Mike gave to put a fresh U-Boot image into
the U-Boot partition over Jtag, and then on the next power-on you should
be back to normal.
The process is not smooth to do this, you need to compile a some stuff
like OpenOCD (which understands JTAG) and libfdti-0.8 (which knows how
to talk to the USB <-> serial converter on the debug board -- only
version 0.8 worked for me) and because it is not used by many people it
is a bit of a difficult path. But it can work in the end and you can
recover from this situation I think.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the openmoko-uboot