Editing N900 Software BME

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

This page is to bring together efforts and links for those working on understanding BME - the battery managment entity.

This is required to implement user friendly [[N900_Hardware_USB_Host|Host Mode]]

See also the garage project [https://garage.maemo.org/projects/jrbme/ JR-BME].

BME is divided into three parts.
* Kernel driver that handles all of the low-level interaction with the hardware.
* hald-addon-bme - an add-on process for HAL that reports status.
* bme_RX-51 - Process started early in boot, with watchdog tickling of the watchdog in chip, configuring the charger chip, selecting charge current etc.

The kernel driver is split over several files.

http://mxr.maemo.org/fremantle/source/kernel/include/linux/i2c/twl4030-madc.h
This handles reading various ADCs to readout voltages, currents and BSI.

'''BSI''', or battery size indicator is the third pin of the battery. Resistance between the - pin and third pin on battery is measured by BME through twl4030-madc, and mapped into a capacity in mAh. BME noticeably uses this as a reference "full" value for the battery meter, and possibly for other uses as well. Here are some experimental results, all resistance readings are to be considered inaccurate at best:

100 k&Omega; 1250mAh (Original BL-5J battery)
  90 k&Omega; 1000mAh
  80 k&Omega;  862mAh
  78 k&Omega;  740mAh

Unsorted adds:

* Then there's also <code>/usr/lib/hal/hald-addon-bme</code>, which seems not to be completely out of order (according to lshal) even when bme_RX-51 is stopped.
* Mer 'replacement hald-addon-bme': http://gitorious.org/mer-toggles/hald-addon-bme/blobs/master/hald-addon-bme.c [[Mer/Documentation/BME_Protocol]] (N810!)
* <code>lsof -p `pidof bme_RX-51`</code> gives an idea about what BME is actually interfering/interfacing with, and a strace will show it talks to dsme_lib probably to implement the watchdog timers.
* BME process/file is called <code>/usr/sbin/bme_RX-51</code> and killing or sigstop'ing it will cause immediate or delayed reboot. It is easily suspended though through upstart process management by:<br /><pre>~>stop bme</pre>and resumed any time by:<br /><pre>~>start bme</pre>

A nice little experiment to investigate the bq24150a USB Battery Charger chip's abilities is to 
* plug in Nokia wallwart charger
* <pre>->stop bme</pre>
* wait max 32s until bq24150a internal watchdog timer expires (due to bme not resetting it), which will cause bq24150a to reset to defaults, which are a mostly sane, safe charging without any software support. You can tell this by bq24150a firing up the hardwired steady yellow indicator LED

I'm about to write a first draft little script to somewhat replace bme's basic functions, eventually turning this into a real project Just-Replaces-BME aka jrbme (some say it's "JRBME replaces BME", according to an age old tradition of linux self referencing ETLA [like GNU=="GNU Not Unix", KDE=="KDE Desktop Environment"])

Joerg's script can be found [http://talk.maemo.org/showpost.php?p=658278&postcount=861 here].
It should not be used by anyone who has not read and understood all relevant datasheets, and understands why it does what it does.

Editing this without understanding can CAUSE YOUR N900 TO CATCH FIRE.

==Replacement Goals==
===Alpha===
* Not make the battery explode.
* Charge from any 5V source, assuming the battery is in a safe condition, just setting the charger chip to the end voltage, and resetting the watchdog.
===Beta===
* Watch the state of the battery, and charge taking into account device load.
** Battery charger chip should be configured to float the battery at a current which slightly exceeds the desired float current, and the charge normally terminated when the actual battery current measured by the bq27200 reaches the 'taper' value. A simple way to measure this is if the 'time till full' field goes to 65535. This ensures a consistent shutoff taper current, which the battery charger alone cannot do.

===Gamma===
* Charge at appropriate limits for USB chargers, and USB hosts we are plugged into.
* Monitor and reset from abnormal conditions - incorrect 'battery missing' and other error codes. Capacity and charge data from bq27200 can be very inaccurate if the phone has not appropriately learned the capacity of the battery, or if it erroneously detects battery full due to a high impedence battery or poor contact.
* If phone is in active use, and charger or USB is plugged in, maintain a constant battery voltage somewhat under the peak charge voltage, without regards to taper current. (To keep phone charged, but not degrade battery with pointless micro-cycling, or high float voltage)

[[Category:N900_Hardware]]

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Retrieved from "https://wiki.maemo.org/N900_Software_BME"

Personal tools

Navigation

Views

Editing N900 Software BME

@@ Line 6: / Line 6: @@
 BME is divided into three parts.
-* Kernel driver that handles all of the low-level interaction with the hardware. (basically just I2C IO)
+* Kernel driver that handles all of the low-level interaction with the hardware.
 * hald-addon-bme - an add-on process for HAL that reports status.
 * bme_RX-51 - Process started early in boot, with watchdog tickling of the watchdog in chip, configuring the charger chip, selecting charge current etc.