<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
<body text="#000000" bgcolor="#FFFFFF">
<pre><i> Hi Sam,
</i><i> Am 23.10.2012 um 15:48 schrieb Sam Muirhead:
></i><i> >> I then inserted the SD card and tried to boot the GTA04. (not plugged
</i><i> </i><i>> </i><i> >> into USB)</i><i>
</i><i> ></i><i> >> It didn't boot, there was no light from the power button, no other signs
</i><i> ></i><i> >> of life.
</i><i> ></i><i> >The last case "It didn't boot" means: not the bootloader either, after
</i><i> ></i><i> >replacing the uSD?
</i><i> ></i><i> Not the bootloader either. With or without SD card, nothing happens when I try to power on.
</i><i> What could have happened is that the contents of the NAND flash have been changed in a way that prevents booting.
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.).
Therefore the device appears to be dead but it is just not coming beyond the point of showing any signs of activity.
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
after a while the battery is deeply discharged that even X-Loader does not start any more.
But you can not see a difference from outside.
</i><i> ></i><i> I've checked my logs and had been getting the same message up until I tried booting it with the SD card.
</i><i> ></i><i> Since then there has been no recognition of the device at all, no 'new device' mentions.
</i><i> This supports my theory stated above. U-Boot is responsible for initializing the USB interface.
</i><i> ></i><i> >> So am I right in saying that I have a flat battery that won't charge?
</i><i> ></i><i> >> Or have I missed something important along the way?
</i><i> ></i><i> >It is what Benjamin wrote: keep it connected, it will trickle-charge for quite
</i><i> ></i><i> >a while, than start flashing the screen on and off, until it accumulates
</i><i> ></i><i> >enough charge to reach the bootloader screen.
</i><i> ></i><i> I kept it connected yesterday, checking on it, and even leaving it connected overnight had no effect. It still won't power on.
Recently I have received one device back that if I remember correctly was in the same state.
I wasn't able to find out how it came into it, i.e. could not reproduce it or develop some countermeasures.
The solution was to connect a RS232 cable and inspect the console messages. U-Boot did
show some error messages but I could erase the U-Boot environment. After restart it worked
Do you have access to such a cable? Or someone nearby can help you?</i>
Thanks for your help Nikolaus - I don't have access to an RS232 cable but I'm based in Berlin, is there anyone on the list who lives here and can help me out?