<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Sam,<div><br><div><div>Am 23.10.2012 um 15:48 schrieb Sam Muirhead:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div text="#000000" bgcolor="#FFFFFF">
<pre><font color="#666666"> >><i> I then inserted the SD card and tried to boot the GTA04. (not plugged
</i> >><i> into USB)</i>
>><i> The gta04 init bootloader screen appeared, and I tried to select the SD
</i> >><i> card, but nothing happened. no response, no sound, no visible change.
</i> >><i> I waited for one minute or so, then tried selecting NAND, just to see if
</i> >><i> it would do anything - still no change.
</i> >><i> I removed the battery, removed the SD card, replaced the battery and
</i> >><i> tried to just boot to lxde again.
</i> >><i> It didn't boot, there was no light from the power button, no other signs
</i> >></font><i><font color="#666666"> of life.</font>
</i><font color="#333333"> >The last case "It didn't boot" means: not the bootloader either, after
>replacing the uSD? </font>
Not the bootloader either. With or without SD card, nothing happens when I try to power on.
</pre></div></blockquote><div>What could have happened is that the contents of the NAND flash have been changed in a way that prevents booting.</div><div>This means that X-Loader starts and loads U-Boot but U-Boot hangs before doing anything useful (e.g. switching on the display, blinking LEDs etc.).</div><div><br></div><div>Therefore the device appears to be dead but it is just not coming beyond the point of showing any signs of activity.</div><div><br></div><div>The problem is that the device isn't charging any more (except trickle charge) in this situation. I.e. battery drains and will not get full again. So</div><div>after a while the battery is deeply discharged that even X-Loader does not start any more.</div><div><br></div><div>But you can not see a difference from outside.</div><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF"><pre><font color="#666666">
>><i> -It was around this point that I read something saying the battery
</i> >><i> should be fully charged when installing an OS - I don't know how much
</i> >><i> charge was on the battery when I started, but it took me a long time
</i> >><i> organising the SD card so it may have been low by the time I tried to
</i> >></font><i><font color="#666666"> boot it.</font>
</i><font color="#333333"> >I expect the phone being connected to your system via USB, while working on
>the uSD, or was it just lying around? As long as it keeps charging, USB
>provides enough power to run the phone and charge the battery.</font>
It was not connected via USB the whole time, but it was only on for maximum 15 minutes since receiving the phone.
<font color="#666666"> >><i> Previously when plugged in via USB I at least had a notification that a
</i> >><i> wired network was active, but now there is no sign of a USB device being
</i> >><i> plugged in (at least I don't think there is). I'm running ubuntu 12.04
</i> >></font><i><font color="#666666"> on a Macbook Pro:</font>
</i><font color="#333333"> >This is what tail -f /var/log/messages tells while turning on and showing the
>bootloader screen:
>Oct 22 21:38:31 tp kernel: [345675.170991] usb 1-1.2: new full-speed USB
>device number 7 using ehci_hcd</font>
I've checked my logs and had been getting the same message up until I tried booting it with the SD card.
Since then there has been no recognition of the device at all, no 'new device' mentions.
</pre></div></blockquote><div>This supports my theory stated above. U-Boot is responsible for initializing the USB interface.</div><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF"><pre><font color="#666666">
>><i> So am I right in saying that I have a flat battery that won't charge?
</i> >></font><i><font color="#666666"> Or have I missed something important along the way?</font>
</i><font color="#333333"> >It is what Benjamin wrote: keep it connected, it will trickle-charge for quite
>a while, than start flashing the screen on and off, until it accumulates
>enough charge to reach the bootloader screen. </font>
I kept it connected yesterday, checking on it, and even leaving it connected overnight had no effect. It still won't power on.
<font color="#333333"> >If I recall correctly, the bootloader screen got enough intelligence to ask
>for a higher current (and charge faster). I'm not sure about that anymore
>though (it was in Radeks bootscreen documentation, but I can't find it at the
>moment).
</font>
<font color="#666666"> >><i> Any suggestions for the next step I should try, or is there any further
</i> >><i> information I should supply?
</i></font><font color="#333333"> >Maybe one more thing: do you have an Openmoko charger, or another high(er)
>power charger? That will charge your battery faster than a USB port of course,
>but besides that, the powermanagement chip seems quite picky about the current
>it receives from the host. Alexander has given a list of creative ways of
>discharging the battery (which I could not find eiter, but I found another
>more to the point discussion about power at boot up:
><a href="http://lists.goldelico.com/pipermail/gta04-owner/2011-November/000659.html">http://lists.goldelico.com/pipermail/gta04-owner/2011-November/000659.html</a></font>
I don't have an Openmoko charger or any other kind of charger - just a USB cable.
</pre></div></blockquote><div>That should be sufficient to charge. The Openmoko charger has no real benefits unless you want to charge with WLAN and UMTS enabled and CPU on full power.</div><blockquote type="cite"><div text="#000000" bgcolor="#FFFFFF"><pre>Where can I get an Openmoko charger?
<font color="#333333">
>Good luck!</font>
Thanks for your help!
</pre>
</div></blockquote><br></div><div>Recently I have received one device back that if I remember correctly was in the same state.</div><div>I wasn't able to find out how it came into it, i.e. could not reproduce it or develop some countermeasures.</div><div><br></div><div>The solution was to connect a RS232 cable and inspect the console messages. U-Boot did</div><div>show some error messages but I could erase the U-Boot environment. After restart it worked</div><div>fine again.</div><div><br></div><div>Do you have access to such a cable? Or someone nearby can help you?</div><div><br></div><div>BR,</div><div>Nikolaus</div><div><br></div><br></div></body></html>