[Bug 878] New: Neo is bricked when not on debug board
bugzilla-daemon at bugzilla.openmoko.org
bugzilla-daemon at bugzilla.openmoko.org
Mon Sep 17 22:12:51 CEST 2007
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=878
Summary: Neo is bricked when not on debug board
Product: Neo1973 Hardware
Version: GTA01v4
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P2
Component: PMU (Power Management Unit)
AssignedTo: sean_chiang at fic.com.tw
ReportedBy: go at l5.org
CC: buglog at lists.openmoko.org
After updating the kernel and rootfs about two weeks ago, I left the Neo on and
connected to my computer USB port. It was not connected to the GSM network (no
SIM installed.) About a week or so later, I noticed the unit was off and tried
to power it up. No luck. Battery showed to be completely discharged, so I
tried my spare (and known to be fully charged battery.) Unit came up and tried
to boot but failed during the last of the boot procedure (about a minute later.)
Unit was now dead and the only sign of life was seen if I removed the battery
and left the unit unpowered for a long time and then reinserted the battery and
tried to power up. I would occasionally (about 1 in 3 times) see a bright
screen flash, usually all white and then nothing. This would occur about 30
seconds after hitting the power button.
I connected the Neo to the debug board, and found that when powered by the debug
board, it would come up and all functions seemed to work. I left it on the
debug board for a few hours and then tried the stand-alone power again and it
failed.
Works on debug board power, fails on own power.
While connected to debug board, I reflashed with current (as of 9/12) u-boot,
kernel and rootfs in case there was some latent (and unreported) bug in my
previous flash (first time I actually flashed the u-boot.) This made no
difference - it still works on debug board and fails on stand-alone power.
My unit model is 70-7GTA01B-00001
S/N is 8A7507575
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
More information about the buglog
mailing list