Re: Battery recovery issues
Here's the logfile. Just one observation: it tooked me 3:30 h to discharge the battery (I did a bat-recover for 16 hours previously), so the battery seems to be in good shape, and also the XO, since with other batteries the led and output from all these commands behave as expected. Also, I want you to know that the first 20 batteries I tested weren't faulty, they just needed to be charged (trickle charged at the begining, then normal charged). I think that kids and our technicians don't know what does the 4-times-blinking-orange-led mean, so I'm giving them immediate instructions on how to proceed. On Tue, May 5, 2009 at 6:44 PM, Richard A. Smith rich...@laptop.org wrote: Emiliano Pastorino wrote: bat-charge reports this: 320.83 mAh (7d53) 1428.12 mA (2ddc) 6.492 V (195c) Chg: 0.41mAh ( 29) then every column raises line to line (I copied that by hand because bat-charge-log always says Can't open file, even when usb stick is plugged in. Turns out the way I did the disk devices won't work unless you either: 1) boot with a usb drive plugged in 2) run 'p2' before bat-debug-log 'p2' will re-probe usb devices. If the first column is battery's charge, then it's almost dry. Should I try bat-recover or charge it the usual way? The first column is the ACR reading and you can't tell anything by just 1 reading. You have to know what it was when you started discharging or charging. I don't report SOC in that listing cause generally I don't care. I want to know what it does after I turn on charge rather than what level it was at previously. bat-charge simply enables charging and then starts reading the battery directly. Thus it does not care about any of the settings in the EEPROM. Its a good diag tool to see if the battery just physically won't take charge or if you just can't communicate to it at all. If bat-charge works but normal charging does not then its EC or EEPROM badness. The LFP batteries have an overvoltage cutoff that will protect them so its ok to just turn one on and leave it. For NiMH you would end up reducing its life. But since you don't have any NiMH you don't care. 'bat-recover' works by PWMing the charge pin to keep the charge current very low and allow the cells to equalize yet not trip the over voltage like they would if you just turned on the charge and left it. The settings I've picked by default seem to work in most cases but I've had many batteries where I needed to reduce the current even further from the default settings. To speed up the process you can use normal charging methods to get the battery close to full (or wherever it cuts out at) That way the recover process will be much shorter. I'll try bat-recover with a bunch of batteries today, so maybe tomorrow or on Wednesday I'll be sending you some logs, if it is ok to you. After looking at your bat-debug log I've realize that the extra diagnostic info is only present in f-series firmwares with my newer EC code. I'm forwarding you an e-mail with a copy of q2f02 that I worked on while trying to solve some problems with batteries in another deployment. q2f02 will be behind q2e41 in terms of OFW but has EC code with extra battery diag info. For battery testing there should no difference between the 2. Its also available here: (Just never announced since a new e-series release happened right after) http://dev.laptop.org/pub/firmware/q2f02/ So install f02 on your test laptop and re-run bat-debug-log after you have first run 'p2' and the logging to disk should work. I don't need any more see-bstate info. so the steps: install f02 remove battery boot stop at ok insert usb drive (or boot with it inserted) run 'p2' run 'bat-debug-log' insert battery run for a couple of minutes then hit a key send me the log. I'll try to get a f03 out soon with the latest of everything but I've got gen 1.5 bring up tasks that I need to attend to. -- Richard Smith rich...@laptop.org One Laptop Per Child -- Ing. Emiliano Pastorino LATU - Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598 2) 601 5773 int.: 213 2:29 0 0x0 0x0 0x1 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 2:29 0 0x0 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 2:30 0 0x0 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 2:30 0 0x0 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 2:31 0 0x0 0x0 0x1 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 2:31 0 0x0 0x0 0x1 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 2:32 0 0x0 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 2:33 0 0x0 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 2:33 0 0x0 0x0 0x1 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 2:34 0 0x0 0x0 0x1 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 2:34 0 0x0 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 2:35 0 0x0
Re: Battery recovery issues
Emiliano Pastorino wrote: Also, I want you to know that the first 20 batteries I tested weren't faulty, they just needed to be charged (trickle charged at the begining, then normal charged). I think that kids and our technicians don't know what does the 4-times-blinking-orange-led mean, so I'm giving them immediate instructions on how to proceed. It means its in trickle charge but that only happens with newer firmware. -- Richard Smith rich...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Battery recovery issues
Emiliano Pastorino wrote: bat-charge reports this: 320.83 mAh (7d53) 1428.12 mA (2ddc) 6.492 V (195c) Chg: 0.41mAh ( 29) then every column raises line to line (I copied that by hand because bat-charge-log always says Can't open file, even when usb stick is plugged in. Turns out the way I did the disk devices won't work unless you either: 1) boot with a usb drive plugged in 2) run 'p2' before bat-debug-log 'p2' will re-probe usb devices. If the first column is battery's charge, then it's almost dry. Should I try bat-recover or charge it the usual way? The first column is the ACR reading and you can't tell anything by just 1 reading. You have to know what it was when you started discharging or charging. I don't report SOC in that listing cause generally I don't care. I want to know what it does after I turn on charge rather than what level it was at previously. bat-charge simply enables charging and then starts reading the battery directly. Thus it does not care about any of the settings in the EEPROM. Its a good diag tool to see if the battery just physically won't take charge or if you just can't communicate to it at all. If bat-charge works but normal charging does not then its EC or EEPROM badness. The LFP batteries have an overvoltage cutoff that will protect them so its ok to just turn one on and leave it. For NiMH you would end up reducing its life. But since you don't have any NiMH you don't care. 'bat-recover' works by PWMing the charge pin to keep the charge current very low and allow the cells to equalize yet not trip the over voltage like they would if you just turned on the charge and left it. The settings I've picked by default seem to work in most cases but I've had many batteries where I needed to reduce the current even further from the default settings. To speed up the process you can use normal charging methods to get the battery close to full (or wherever it cuts out at) That way the recover process will be much shorter. I'll try bat-recover with a bunch of batteries today, so maybe tomorrow or on Wednesday I'll be sending you some logs, if it is ok to you. After looking at your bat-debug log I've realize that the extra diagnostic info is only present in f-series firmwares with my newer EC code. I'm forwarding you an e-mail with a copy of q2f02 that I worked on while trying to solve some problems with batteries in another deployment. q2f02 will be behind q2e41 in terms of OFW but has EC code with extra battery diag info. For battery testing there should no difference between the 2. Its also available here: (Just never announced since a new e-series release happened right after) http://dev.laptop.org/pub/firmware/q2f02/ So install f02 on your test laptop and re-run bat-debug-log after you have first run 'p2' and the logging to disk should work. I don't need any more see-bstate info. so the steps: install f02 remove battery boot stop at ok insert usb drive (or boot with it inserted) run 'p2' run 'bat-debug-log' insert battery run for a couple of minutes then hit a key send me the log. I'll try to get a f03 out soon with the latest of everything but I've got gen 1.5 bring up tasks that I need to attend to. -- Richard Smith rich...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Battery recovery issues
Richard, I've attached batdbug.log and seebstate.log. watch-battery says No battery. Battery led is always off. Sn is: 0060208060811873 bat-charge reports this: 320.83 mAh (7d53) 1428.12 mA (2ddc) 6.492 V (195c) Chg: 0.41mAh ( 29) then every column raises line to line (I copied that by hand because bat-charge-log always says Can't open file, even when usb stick is plugged in) If the first column is battery's charge, then it's almost dry. Should I try bat-recover or charge it the usual way? After all these tests, I'll have to write a step-by-step guide for the people at our technical center so they can tell when a battery can be recovered and when not, so I must try to cover as many situations as possible. I'll try bat-recover with a bunch of batteries today, so maybe tomorrow or on Wednesday I'll be sending you some logs, if it is ok to you. On Fri, May 1, 2009 at 3:29 AM, Richard A. Smith rich...@laptop.org wrote: Emiliano Pastorino wrote: Richard, I've just received a box with 60 faulty batteries inside, so I'll be playing with them for the next few years... :) I did a bat-recover on one of them for about 18 hours and I noticed this: When I run watch-battery, it still says No battery. I did a full-reset of the XO but nothing happened, it still says No battery. Then I loaded batman.fth and ran bat-charge and I got a nice output. All the values seemed to be OK when charging or discharging the battery. I tried batman-start; 6a bat-set-status; batman-stop and I could see tha 6a in the first block, but watch-battery still says No battery. Hmm.. and see-bstate shows 0 1 2 over and over? There is one more battery debugging tool available. Its called bat-debug and bat-debug-log.with the power for the cpu and for the The both read the same thing but bat-debug-log will write the contents to 'disk:\batdbug.log'. 'disk' is USB or SD depending on what you have inserted. bat-debug just does the screen and serial port. If the 1-wire state machine is just looping over and over bat-debug won't provide much more info. It might however point out what part of the state machine is failing. That part of the code has a pretty large number of if() clauses all lumped into the same state. Procedure: 1) Remove the problem battery. 2) Boot machine and stop boot at OFW prompt. 3) run bat-debug (or bat-debug-log) 4) insert the battery 5) let it run for one or 2 screenfuls of info 6) hit a key to stop bat-debug send me the info. Note, that you don't run batman-start before you run bat-debug since you want the EC state machine to run and you don't need to 'fload batman.fth'. bat-debug should be in your firmware already. What is the difference between batman's bat-charge and watch-battery? Tell me if I'm wrong, but I think that bat-charge reads battery info directly from it, and watch-battery takes that info from the EC. So, the problem could be that the EC isn't synced with the battery. Am I right? Correct. Batman code takes over the 1-wire communication bus from the EC and talks directly to the battery. 'watch-battery' uses EC commands to read what the EC thinks. So if the EC state machine is bailing out for some reason then you will get odd things from watch-battery where batman only needs the 1-wire to work. So long I could recover 2 batteries out of 4. I'll try more batteries, the batteries that seem to be ok now are the same model (GP NTA2490), and the other two (the ones I couldn't recover even with bat-recover) are BYD LP183662AR-2S. I have no idea what this number is. The serial number I would need is the long string of digits under the barcode in the center of the battery. If you want me to do a particular test with any of these batteries, just ask and I'll share my results with you. Well. I'd like to make sure the firmware has the diagnostics that will allow you to figure out whats up with the battery. So depending on what see-bstate and bat-debug info is I'll perhaps need to make new firmware or new diags in batman.fth to try and figure out whats up. -- Richard Smith rich...@laptop.org One Laptop Per Child -- Ing. Emiliano Pastorino LATU - Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598 2) 601 5773 int.: 210 23:25 0 0x0 0x0 0x1 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 23:26 0 0x0 0x0 0x1 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 23:26 0 0x0 0x0 0x1 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 23:27 0 0x0 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 23:27 0 0x0 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 23:28 0 0x0 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 23:28 0 0x0 0x0 0x0 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 23:29 0 0x0 0x0 0x1 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0 23:30 0 0x0 0x0 0x1 0x1 0x0 0x0 0x0 0x0 0x0 0.00 0.000 0.00 0.00 0 0x0 0x0
Re: Battery recovery issues
Emiliano Pastorino wrote: Richard, I've just received a box with 60 faulty batteries inside, so I'll be playing with them for the next few years... :) I did a bat-recover on one of them for about 18 hours and I noticed this: When I run watch-battery, it still says No battery. I did a full-reset of the XO but nothing happened, it still says No battery. Then I loaded batman.fth and ran bat-charge and I got a nice output. All the values seemed to be OK when charging or discharging the battery. I tried batman-start; 6a bat-set-status; batman-stop and I could see tha 6a in the first block, but watch-battery still says No battery. Hmm.. and see-bstate shows 0 1 2 over and over? There is one more battery debugging tool available. Its called bat-debug and bat-debug-log.with the power for the cpu and for the The both read the same thing but bat-debug-log will write the contents to 'disk:\batdbug.log'. 'disk' is USB or SD depending on what you have inserted. bat-debug just does the screen and serial port. If the 1-wire state machine is just looping over and over bat-debug won't provide much more info. It might however point out what part of the state machine is failing. That part of the code has a pretty large number of if() clauses all lumped into the same state. Procedure: 1) Remove the problem battery. 2) Boot machine and stop boot at OFW prompt. 3) run bat-debug (or bat-debug-log) 4) insert the battery 5) let it run for one or 2 screenfuls of info 6) hit a key to stop bat-debug send me the info. Note, that you don't run batman-start before you run bat-debug since you want the EC state machine to run and you don't need to 'fload batman.fth'. bat-debug should be in your firmware already. What is the difference between batman's bat-charge and watch-battery? Tell me if I'm wrong, but I think that bat-charge reads battery info directly from it, and watch-battery takes that info from the EC. So, the problem could be that the EC isn't synced with the battery. Am I right? Correct. Batman code takes over the 1-wire communication bus from the EC and talks directly to the battery. 'watch-battery' uses EC commands to read what the EC thinks. So if the EC state machine is bailing out for some reason then you will get odd things from watch-battery where batman only needs the 1-wire to work. So long I could recover 2 batteries out of 4. I'll try more batteries, the batteries that seem to be ok now are the same model (GP NTA2490), and the other two (the ones I couldn't recover even with bat-recover) are BYD LP183662AR-2S. I have no idea what this number is. The serial number I would need is the long string of digits under the barcode in the center of the battery. If you want me to do a particular test with any of these batteries, just ask and I'll share my results with you. Well. I'd like to make sure the firmware has the diagnostics that will allow you to figure out whats up with the battery. So depending on what see-bstate and bat-debug info is I'll perhaps need to make new firmware or new diags in batman.fth to try and figure out whats up. -- Richard Smith rich...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Battery recovery issues
Richard, I've just received a box with 60 faulty batteries inside, so I'll be playing with them for the next few years... I did a bat-recover on one of them for about 18 hours and I noticed this: When I run watch-battery, it still says No battery. I did a full-reset of the XO but nothing happened, it still says No battery. Then I loaded batman.fth and ran bat-charge and I got a nice output. All the values seemed to be OK when charging or discharging the battery. I tried batman-start; 6a bat-set-status; batman-stop and I could see tha 6a in the first block, but watch-battery still says No battery. What is the difference between batman's bat-charge and watch-battery? Tell me if I'm wrong, but I think that bat-charge reads battery info directly from it, and watch-battery takes that info from the EC. So, the problem could be that the EC isn't synced with the battery. Am I right? So long I could recover 2 batteries out of 4. I'll try more batteries, the batteries that seem to be ok now are the same model (GP NTA2490), and the other two (the ones I couldn't recover even with bat-recover) are BYD LP183662AR-2S. If you want me to do a particular test with any of these batteries, just ask and I'll share my results with you. On Wed, Apr 29, 2009 at 2:25 PM, Richard A. Smith rich...@laptop.orgwrote: Emiliano Pastorino wrote: Are you using the latest batman.fth? I pulled a lot of batman functionality into the firmware and had to modify batman.fth to avoid the errors above. I'm using 0.3.6. Sorry. I didn't have the latest up on the site. Grab a fresh copy. Is there any up-to-date document on how to proceed when recovering a faulty battery using recent firmware? No. But the difference is just running batman-start prior to bat-recover. If you want to stop bat-recover then remove the battery. It will error and drop to an ok prompt. Should I expect any output when running batman-start? I noticed that battery interface is suspended, but I don't see anything else going on. Nope. And while batman is enabled don't expect the charge LED to do anything normal. It will flash in odd patterns. Now I'm trying to recover a red led flashing battery. Suddenly, it went from flashing red to nothing and I'm also getting No battery from watch-battery and 0 1 2 0 1 2. from see-bstat. When the led was flashing red, I could get an error code of 2 from ec-abnormal@ .. Now I'm getting 0. I'd like to know what that 2 meant. Where can I get the explanation of those error codes? The error list on the wiki is a bit out of date. I'll work on updating a list on the battery diagnostics page. A 2 mean that the status register setting in the battery gas gauge was not what the EC expected it to be. This happens every so often and is usually transient. If it was actually written into the EEPROM and you get that every time then please do a bat-dump-banks and look at the value in the 2nd line of bank0, Col 1. It should be 0x6a if is not then you can use bat-set-status to fix it. ok batman-start ok 6a bat-set-status ok batman-stop I'll be testing more faulty batteries, so I'll be bothering here periodically :) No problem. Please help me keep the battery diagnostic page up to date with things that you find. On that note. I need to get with you sometime and get some charge logs. I'm want to know how the capacity of the batteries you have had out in the field are holding up. -- Richard Smith rich...@laptop.org One Laptop Per Child -- Ing. Emiliano Pastorino LATU - Plan Ceibal Av. Italia 6201 CP: 11500, Montevideo, Uruguay Tel: (598 2) 601 5773 int.: 210 ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Battery recovery issues
Emiliano Pastorino wrote: Hello everyone, I'm trying to recover a battery than seems to be broken. This is what I've done so far: - I've plugged the battery on an unsecured XO. - When I run watch-battery from the ok prompt, I get a No battery message. - I tried see-bstate and I get an infinite output of 0 1 2 0 1 2 0 1 2 0 1 2 - Battery led never flashes. - If I use a known good battery, I get all the expected results (led turns on, nice output from the commands above). Besides, I tried to use batman.fth, but when I run fload nand:\batman.fth I get The file 'nand:\olpc.fth' cannot be opened. I've downloaded batman.fth from http://dev.laptop.org/pub/firmware/scripts/batman.fth and placed it in / . Put batman.fth in /home/olpc and try fload nand:\home\olpc\batman.fth. nand:\ at the ok prompt is not / in linux, check with dir nand:\ at the ok prompt. Try to reset the battery with 1w-init bat-set-low and bat-recover, I have seen a battery with the see-bstate problem working afterwards. Good luck. I'm using firmware Q2E35. Is that battery unrecoverable? How can I tell the difference between a completely broken battery and a broken-but-recoverable one? Any tips? Emiliano ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Battery recovery issues
Emiliano Pastorino wrote: Put batman.fth in /home/olpc and try fload nand:\home\olpc\batman.fth. OK. That worked (I think), but now I'm getting this when I execute fload: sd.ddd isn't unique sd.dd isn't unique ec-rambase isn't unique ec-ram@ isn't unique logstr isn't unique sd isn't unique sdx isn't unique nand:\home\olpc\batman.fth:763: w16d32? nand:\home\olpc\batman.fth:769: w16d32? nand:\home\olpc\batman.fth:773: w16d32? Are you using the latest batman.fth? I pulled a lot of batman functionality into the firmware and had to modify batman.fth to avoid the errors above. Originally, I only pulled in some key diagnostics but then in later firmwares I needed the formatting functions too so its a bit of a mismash. Try to reset the battery with 1w-init bat-set-low and bat-recover, I have seen a battery with the see-bstate problem working afterwards. 1w-init should not be used anymore. Rather you do a 'batman-start' New firmware suspends only the battery interface and leaves the keyboard active. 'batman-stop' will resume normal operation. I get No response from battery with both commands. The battery is officially dead -- Richard Smith rich...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Battery recovery issues
Are you using the latest batman.fth? I pulled a lot of batman functionality into the firmware and had to modify batman.fth to avoid the errors above. I'm using 0.3.6. Originally, I only pulled in some key diagnostics but then in later firmwares I needed the formatting functions too so its a bit of a mismash. Is there any up-to-date document on how to proceed when recovering a faulty battery using recent firmware? New firmware suspends only the battery interface and leaves the keyboard active. 'batman-stop' will resume normal operation. Should I expect any output when running batman-start? I noticed that battery interface is suspended, but I don't see anything else going on. Now I'm trying to recover a red led flashing battery. Suddenly, it went from flashing red to nothing and I'm also getting No battery from watch-battery and 0 1 2 0 1 2. from see-bstat. When the led was flashing red, I could get an error code of 2 from ec-abnormal@ .. Now I'm getting 0. I'd like to know what that 2 meant. Where can I get the explanation of those error codes? I'll be testing more faulty batteries, so I'll be bothering here periodically :) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Battery recovery issues
Emiliano Pastorino wrote: Are you using the latest batman.fth? I pulled a lot of batman functionality into the firmware and had to modify batman.fth to avoid the errors above. I'm using 0.3.6. Sorry. I didn't have the latest up on the site. Grab a fresh copy. Is there any up-to-date document on how to proceed when recovering a faulty battery using recent firmware? No. But the difference is just running batman-start prior to bat-recover. If you want to stop bat-recover then remove the battery. It will error and drop to an ok prompt. Should I expect any output when running batman-start? I noticed that battery interface is suspended, but I don't see anything else going on. Nope. And while batman is enabled don't expect the charge LED to do anything normal. It will flash in odd patterns. Now I'm trying to recover a red led flashing battery. Suddenly, it went from flashing red to nothing and I'm also getting No battery from watch-battery and 0 1 2 0 1 2. from see-bstat. When the led was flashing red, I could get an error code of 2 from ec-abnormal@ .. Now I'm getting 0. I'd like to know what that 2 meant. Where can I get the explanation of those error codes? The error list on the wiki is a bit out of date. I'll work on updating a list on the battery diagnostics page. A 2 mean that the status register setting in the battery gas gauge was not what the EC expected it to be. This happens every so often and is usually transient. If it was actually written into the EEPROM and you get that every time then please do a bat-dump-banks and look at the value in the 2nd line of bank0, Col 1. It should be 0x6a if is not then you can use bat-set-status to fix it. ok batman-start ok 6a bat-set-status ok batman-stop I'll be testing more faulty batteries, so I'll be bothering here periodically :) No problem. Please help me keep the battery diagnostic page up to date with things that you find. On that note. I need to get with you sometime and get some charge logs. I'm want to know how the capacity of the batteries you have had out in the field are holding up. -- Richard Smith rich...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Battery recovery issues
Hello everyone, I'm trying to recover a battery than seems to be broken. This is what I've done so far: - I've plugged the battery on an unsecured XO. - When I run watch-battery from the ok prompt, I get a No battery message. - I tried see-bstate and I get an infinite output of 0 1 2 0 1 2 0 1 2 0 1 2 - Battery led never flashes. - If I use a known good battery, I get all the expected results (led turns on, nice output from the commands above). Besides, I tried to use batman.fth, but when I run fload nand:\batman.fth I get The file 'nand:\olpc.fth' cannot be opened. I've downloaded batman.fth from http://dev.laptop.org/pub/firmware/scripts/batman.fth and placed it in / . I'm using firmware Q2E35. Is that battery unrecoverable? How can I tell the difference between a completely broken battery and a broken-but-recoverable one? Any tips? Emiliano ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Battery recovery issues
Emiliano Pastorino wrote: - I tried see-bstate and I get an infinite output of 0 1 2 0 1 2 0 1 2 0 1 2 This means the battery is not responding to 1-wire reset. Nothing more you can do with out an o-scope. Probably not worth the time to go further unless you have a lot of them that are in this state. -- Richard Smith rich...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Battery recovery issues
Emiliano Pastorino wrote: How can I tell the difference between a completely http://wiki.laptop.org/go/XO_Troubleshooting_Battery#Diagnosing_Battery_Problems If see-bstate shows you more than just 0 1 2 then the battery is something you can work with. -- Richard Smith rich...@laptop.org One Laptop Per Child ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
