Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[EMAIL PROTECTED]
You can reach the person managing the list at
[EMAIL PROTECTED]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
2. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
3. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
4. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
5. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
6. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
7. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
8. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
9. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
10. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
11. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
12. [Bug 212] Charging seems completely broken
([EMAIL PROTECTED])
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 21:10 -------
Harald wrote:
> 1) the PMU decides that the battery voltage is high enough to boot
> 2) it switches on the CPU, which in turn switches on various peripherals, most
> notably high-power peripherals such as backlight
> 3) due to the high current draw, the battery voltage decreases below the
> threshold of the PMU
...
> a) we could set a higher Vlowbat (minimum battery voltage) threshold. This
> sucks because we would shut down the phone even before the battery is
> empty.
So is this just a case of missing hysteresis? That is, is there a single
threshold value that is being examined in steps 1 and 3 above? If so, could the
answer be as simple as using separate values and raising the value for step 1
while leaving the value for step 3 where it is?
-Carl
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 21:10 -------
Harald wrote:
> 1) the PMU decides that the battery voltage is high enough to boot
> 2) it switches on the CPU, which in turn switches on various peripherals, most
> notably high-power peripherals such as backlight
> 3) due to the high current draw, the battery voltage decreases below the
> threshold of the PMU
...
> a) we could set a higher Vlowbat (minimum battery voltage) threshold. This
> sucks because we would shut down the phone even before the battery is
> empty.
So is this just a case of missing hysteresis? That is, is there a single
threshold value that is being examined in steps 1 and 3 above? If so, could the
answer be as simple as using separate values and raising the value for step 1
while leaving the value for step 3 where it is?
-Carl
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 21:10 -------
Harald wrote:
> 1) the PMU decides that the battery voltage is high enough to boot
> 2) it switches on the CPU, which in turn switches on various peripherals, most
> notably high-power peripherals such as backlight
> 3) due to the high current draw, the battery voltage decreases below the
> threshold of the PMU
...
> a) we could set a higher Vlowbat (minimum battery voltage) threshold. This
> sucks because we would shut down the phone even before the battery is
> empty.
So is this just a case of missing hysteresis? That is, is there a single
threshold value that is being examined in steps 1 and 3 above? If so, could the
answer be as simple as using separate values and raising the value for step 1
while leaving the value for step 3 where it is?
-Carl
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 21:10 -------
Harald wrote:
> 1) the PMU decides that the battery voltage is high enough to boot
> 2) it switches on the CPU, which in turn switches on various peripherals, most
> notably high-power peripherals such as backlight
> 3) due to the high current draw, the battery voltage decreases below the
> threshold of the PMU
...
> a) we could set a higher Vlowbat (minimum battery voltage) threshold. This
> sucks because we would shut down the phone even before the battery is
> empty.
So is this just a case of missing hysteresis? That is, is there a single
threshold value that is being examined in steps 1 and 3 above? If so, could the
answer be as simple as using separate values and raising the value for step 1
while leaving the value for step 3 where it is?
-Carl
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 21:10 -------
Harald wrote:
> 1) the PMU decides that the battery voltage is high enough to boot
> 2) it switches on the CPU, which in turn switches on various peripherals, most
> notably high-power peripherals such as backlight
> 3) due to the high current draw, the battery voltage decreases below the
> threshold of the PMU
...
> a) we could set a higher Vlowbat (minimum battery voltage) threshold. This
> sucks because we would shut down the phone even before the battery is
> empty.
So is this just a case of missing hysteresis? That is, is there a single
threshold value that is being examined in steps 1 and 3 above? If so, could the
answer be as simple as using separate values and raising the value for step 1
while leaving the value for step 3 where it is?
-Carl
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 21:10 -------
Harald wrote:
> 1) the PMU decides that the battery voltage is high enough to boot
> 2) it switches on the CPU, which in turn switches on various peripherals, most
> notably high-power peripherals such as backlight
> 3) due to the high current draw, the battery voltage decreases below the
> threshold of the PMU
...
> a) we could set a higher Vlowbat (minimum battery voltage) threshold. This
> sucks because we would shut down the phone even before the battery is
> empty.
So is this just a case of missing hysteresis? That is, is there a single
threshold value that is being examined in steps 1 and 3 above? If so, could the
answer be as simple as using separate values and raising the value for step 1
while leaving the value for step 3 where it is?
-Carl
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 21:10 -------
Harald wrote:
> 1) the PMU decides that the battery voltage is high enough to boot
> 2) it switches on the CPU, which in turn switches on various peripherals, most
> notably high-power peripherals such as backlight
> 3) due to the high current draw, the battery voltage decreases below the
> threshold of the PMU
...
> a) we could set a higher Vlowbat (minimum battery voltage) threshold. This
> sucks because we would shut down the phone even before the battery is
> empty.
So is this just a case of missing hysteresis? That is, is there a single
threshold value that is being examined in steps 1 and 3 above? If so, could the
answer be as simple as using separate values and raising the value for step 1
while leaving the value for step 3 where it is?
-Carl
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|PC |Other
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 22:14 -------
Here's how one can reproduce at least some of the symptoms on my bv2.
Be sure you know what you're doing. If you reverse the polarity,
all you're likely to get is a heap of smoking misery. All readings
are from the lab supply. I didn't measure what's going on on USB.
- remove the battery
- set the voltage of your lab power supply to 3.0V
- hook up your lab supply instead the the battery (careful !)
- set the current limit high (above 300 mA)
- connect USB
- your voltage readout on the lab supply should jump to about 4.1V
- turn your Neo on. You should now get, on the lab supply, up to
250 mA and 3.0V
- while the system is running, limit the current to about 220 mA
- the system should reset, make it to the splash screen, reset
again, etc.
- briefly press the power button to end this
- power on repeats the cycle
- you can reduce the time the splash screen is shown by limiting the
current further. The minimum is about 150 mA.
- you'll notice that each cycle lasts about 1.25 seconds
- limit the current to about 90 mA
- all of a sudden, the cycles get quicker, about 0.6 seconds
- pressing the power button no longer has any effect now
- if I disconnect and reconnect USB, the machine happily enters the
same cycle again
- further lowering the current accelerates the cycle to about 120 ms
- this goes on until I limit the current to nominally zero
- even at "zero", the cycle is restarted as soon as both USB and
battery power are present (no matter in which order)
Note that my bv2 is "naked". In particular, it doesn't have a vibrator,
which may change some of the results.
- Werner
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|PC |Other
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 22:14 -------
Here's how one can reproduce at least some of the symptoms on my bv2.
Be sure you know what you're doing. If you reverse the polarity,
all you're likely to get is a heap of smoking misery. All readings
are from the lab supply. I didn't measure what's going on on USB.
- remove the battery
- set the voltage of your lab power supply to 3.0V
- hook up your lab supply instead the the battery (careful !)
- set the current limit high (above 300 mA)
- connect USB
- your voltage readout on the lab supply should jump to about 4.1V
- turn your Neo on. You should now get, on the lab supply, up to
250 mA and 3.0V
- while the system is running, limit the current to about 220 mA
- the system should reset, make it to the splash screen, reset
again, etc.
- briefly press the power button to end this
- power on repeats the cycle
- you can reduce the time the splash screen is shown by limiting the
current further. The minimum is about 150 mA.
- you'll notice that each cycle lasts about 1.25 seconds
- limit the current to about 90 mA
- all of a sudden, the cycles get quicker, about 0.6 seconds
- pressing the power button no longer has any effect now
- if I disconnect and reconnect USB, the machine happily enters the
same cycle again
- further lowering the current accelerates the cycle to about 120 ms
- this goes on until I limit the current to nominally zero
- even at "zero", the cycle is restarted as soon as both USB and
battery power are present (no matter in which order)
Note that my bv2 is "naked". In particular, it doesn't have a vibrator,
which may change some of the results.
- Werner
------- You are receiving this mail because: -------
You reported the bug, or are watching the reporter.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|PC |Other
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 22:14 -------
Here's how one can reproduce at least some of the symptoms on my bv2.
Be sure you know what you're doing. If you reverse the polarity,
all you're likely to get is a heap of smoking misery. All readings
are from the lab supply. I didn't measure what's going on on USB.
- remove the battery
- set the voltage of your lab power supply to 3.0V
- hook up your lab supply instead the the battery (careful !)
- set the current limit high (above 300 mA)
- connect USB
- your voltage readout on the lab supply should jump to about 4.1V
- turn your Neo on. You should now get, on the lab supply, up to
250 mA and 3.0V
- while the system is running, limit the current to about 220 mA
- the system should reset, make it to the splash screen, reset
again, etc.
- briefly press the power button to end this
- power on repeats the cycle
- you can reduce the time the splash screen is shown by limiting the
current further. The minimum is about 150 mA.
- you'll notice that each cycle lasts about 1.25 seconds
- limit the current to about 90 mA
- all of a sudden, the cycles get quicker, about 0.6 seconds
- pressing the power button no longer has any effect now
- if I disconnect and reconnect USB, the machine happily enters the
same cycle again
- further lowering the current accelerates the cycle to about 120 ms
- this goes on until I limit the current to nominally zero
- even at "zero", the cycle is restarted as soon as both USB and
battery power are present (no matter in which order)
Note that my bv2 is "naked". In particular, it doesn't have a vibrator,
which may change some of the results.
- Werner
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|PC |Other
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 22:14 -------
Here's how one can reproduce at least some of the symptoms on my bv2.
Be sure you know what you're doing. If you reverse the polarity,
all you're likely to get is a heap of smoking misery. All readings
are from the lab supply. I didn't measure what's going on on USB.
- remove the battery
- set the voltage of your lab power supply to 3.0V
- hook up your lab supply instead the the battery (careful !)
- set the current limit high (above 300 mA)
- connect USB
- your voltage readout on the lab supply should jump to about 4.1V
- turn your Neo on. You should now get, on the lab supply, up to
250 mA and 3.0V
- while the system is running, limit the current to about 220 mA
- the system should reset, make it to the splash screen, reset
again, etc.
- briefly press the power button to end this
- power on repeats the cycle
- you can reduce the time the splash screen is shown by limiting the
current further. The minimum is about 150 mA.
- you'll notice that each cycle lasts about 1.25 seconds
- limit the current to about 90 mA
- all of a sudden, the cycles get quicker, about 0.6 seconds
- pressing the power button no longer has any effect now
- if I disconnect and reconnect USB, the machine happily enters the
same cycle again
- further lowering the current accelerates the cycle to about 120 ms
- this goes on until I limit the current to nominally zero
- even at "zero", the cycle is restarted as soon as both USB and
battery power are present (no matter in which order)
Note that my bv2 is "naked". In particular, it doesn't have a vibrator,
which may change some of the results.
- Werner
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
--- Begin Message ---
http://bugzilla.openmoko.org/cgi-bin/bugzilla/show_bug.cgi?id=212
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Platform|PC |Other
------- Additional Comments From [EMAIL PROTECTED] 2007-03-10 22:14 -------
Here's how one can reproduce at least some of the symptoms on my bv2.
Be sure you know what you're doing. If you reverse the polarity,
all you're likely to get is a heap of smoking misery. All readings
are from the lab supply. I didn't measure what's going on on USB.
- remove the battery
- set the voltage of your lab power supply to 3.0V
- hook up your lab supply instead the the battery (careful !)
- set the current limit high (above 300 mA)
- connect USB
- your voltage readout on the lab supply should jump to about 4.1V
- turn your Neo on. You should now get, on the lab supply, up to
250 mA and 3.0V
- while the system is running, limit the current to about 220 mA
- the system should reset, make it to the splash screen, reset
again, etc.
- briefly press the power button to end this
- power on repeats the cycle
- you can reduce the time the splash screen is shown by limiting the
current further. The minimum is about 150 mA.
- you'll notice that each cycle lasts about 1.25 seconds
- limit the current to about 90 mA
- all of a sudden, the cycles get quicker, about 0.6 seconds
- pressing the power button no longer has any effect now
- if I disconnect and reconnect USB, the machine happily enters the
same cycle again
- further lowering the current accelerates the cycle to about 120 ms
- this goes on until I limit the current to nominally zero
- even at "zero", the cycle is restarted as soon as both USB and
battery power are present (no matter in which order)
Note that my bv2 is "naked". In particular, it doesn't have a vibrator,
which may change some of the results.
- Werner
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog
