Depends on the controller of the battery.
Older smart batteries the eeprom was external. I tried the erasing thing, Some batteries it worked, but the IBM batteries it would cause an orange flashing light and battery failure to be recognized. the serial number, model, and the battery's odometer is in the eeprom. Also some batteries firmware checksum the eeprom, so if you modify it anyway you have to know the algo otherwise it again is rejected. So many varieties. I eventually gave up the whole smart battery thing. I guess if you had a battery that the firwmare was available for it, and in plain text, your life just got loads easier as you can just simply reflash the micro.
Newer batteries, the micro has everything integrated and in which case your screwed as most of those have thier security bits set.
if we are to rebuild smart batteries, we need tools to do so. Such as reverse engineering of the data protocol, firmwares, etc.. Because what would be nice is if an "open controller" was created, that supported a multitude of different battery/ACPI protocols. Then we can just replace the cells, put an open source controller in it, and done.
Its also possible that some batteries have a function built in that you can call, and it revirginizes the eeprom/odometer and resets it back to "refurbished" or new state. I cant verify that though. Again depends on the firmware/controller.
Older smart batteries the eeprom was external. I tried the erasing thing, Some batteries it worked, but the IBM batteries it would cause an orange flashing light and battery failure to be recognized. the serial number, model, and the battery's odometer is in the eeprom. Also some batteries firmware checksum the eeprom, so if you modify it anyway you have to know the algo otherwise it again is rejected. So many varieties. I eventually gave up the whole smart battery thing. I guess if you had a battery that the firwmare was available for it, and in plain text, your life just got loads easier as you can just simply reflash the micro.
Newer batteries, the micro has everything integrated and in which case your screwed as most of those have thier security bits set.
if we are to rebuild smart batteries, we need tools to do so. Such as reverse engineering of the data protocol, firmwares, etc.. Because what would be nice is if an "open controller" was created, that supported a multitude of different battery/ACPI protocols. Then we can just replace the cells, put an open source controller in it, and done.
Its also possible that some batteries have a function built in that you can call, and it revirginizes the eeprom/odometer and resets it back to "refurbished" or new state. I cant verify that though. Again depends on the firmware/controller.