Will a full discharge reset the battery-protection-circuit's CPU?

ankostis ankostis at gmail.com
Tue Sep 2 18:16:13 CEST 2008


Hi,

I'm having problems with my new Freerunner's Battery, as described here:
http://lists.openmoko.org/pipermail/support/2008-August/002388.html

In short, the battery contained within the box was already charged (~3.6 V),
but it didn't charge any more.
Although the status='Charging', the current-now=0!
I verified it with a amp-meter as instructed here:
http://wiki.openmoko.org/wiki/Charging_battery_directly

Contacting the support list, i was told to contact my dealer, and i did.
After evaluating the situation with the scripts and results i'm attaching,
they have agreed to post me a replacement battery
(excellent support so far)


I was also told by Michael Shiloh to post the next question here:
(see http://lists.openmoko.org/pipermail/support/2008-September/002435.html)

I'm thinking that the problem lies within the protecting-circuit's CPU.
The idea is to force the CPU to a reset.
And i'm thinking of draining the battery completely and hoping that it
will fix the protection-circuit's logic.

Is this a viable solution?

Thank you in advance,
  Kostis Anagnostopoulos



-----------------------
Charger Test Script
-----------------------
#!/bin/sh
echo STATE OF POWER SUBSYSTEMS

echo APM says:
apm

echo
echo "** Sysfs reports charger status **"
echo "Charge mode (enabled if there is enough power available to charge,"
echo "             even if not currently charging)"
cat /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/chgmode

echo Charger type:
cat /sys/devices/platform/s3c2440-i2c/i2c-adapter/i2c-0/0-0073/charger_type

echo
echo "** Sysfs reports battery status - may be up to 4 seconds out of date **"

echo "Status (Not Charging or Full means there's power available"
echo "        but the battery doesn't need charging at the moment.)"
cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/status

echo "Coulomb Counter present? (should be 1 with an Openmoko battery)"
cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/present

echo Battery Voltage:
echo $((`cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/voltage_now`/1000))mV

echo "Battery Current (-ve when charging):"
echo $((`cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/current_now`/1000))mA

echo Estimated capacity when full:
echo $((`cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/charge_full`/1000))mAh

echo "Charge state (%)"
cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/capacity

echo Battery temperature:
echo $((`cat /sys/devices/platform/bq27000-battery.0/power_supply/bat/temp`/10))
C

-----------------------
Results with Charger
-----------------------
STATE OF POWER SUBSYSTEMS
APM says:
On-line, battery status critical: 0% (45d+12:15:00)

** Sysfs reports charger status **
Charge mode (enabled if there is enough power available to charge,
             even if not currently charging)
enabled
Charger type:
charger 1A mode 1A

** Sysfs reports battery status - may be up to 4 seconds out of date **
Status (Not Charging or Full means there's power available
        but the battery doesn't need charging at the moment.)
Not charging
Coulomb Counter present? (should be 1 with an Openmoko battery)
1
Battery Voltage:
3103mV
Battery Current (-ve when charging):
0mA
Estimated capacity when full:
1214mAh
Charge state (%)
0
Battery temperature:
30 C
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ptest1_usb.txt
Url: http://lists.openmoko.org/pipermail/openmoko-kernel/attachments/20080902/11bc5af2/attachment.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ptest2_nothing.txt
Url: http://lists.openmoko.org/pipermail/openmoko-kernel/attachments/20080902/11bc5af2/attachment-0001.txt 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ptest3_charger.txt
Url: http://lists.openmoko.org/pipermail/openmoko-kernel/attachments/20080902/11bc5af2/attachment-0002.txt 


More information about the openmoko-kernel mailing list