![]() |
Re: Only boots up in RD Mode
Quote:
Please revert to stock kernel (for now, until this got solved), never load this module (only available in powerkernel), best you delete it completely. This module is *known* to conflict with bme by exclusively allocating the I2C bus to bq27200, so whenever bme starts after the module got loaded, bme will blow chunks on trying to get info about battery /j |
Re: Only boots up in RD Mode
Quote:
Quote:
Quote:
I'll post a more comprehensive statement later /j |
Re: Only boots up in RD Mode
Quote:
Sorry - please scratch this whole post. It has too many false assumptions to comment on them one by one. Bottom line: it won't help /j |
Re: Only boots up in RD Mode
Quote:
I honestly suggest you try a new battery first, then if that gives same result we may have a look what else may cause this problem /j |
Re: Only boots up in RD Mode
ok, now that I'm at end of this thread, it seems you managed to spot the root cause. :-) Congrats. It's quite obvious this can only be a hw defect. Does anybody know what's a "good" value for BSI? (I probably could look up in source of getbootstate, but bear with me...)
jvollmann, please check carefully your 3 contact blades of battery contact in device - CLEAN them! BSI also gets probed by modem directly, so I wonder what modem says to this. Alas we can't ask the modem ;-) I only hope this isn't a silicon burnout, possibly caused by overclocking or harsh treatment of device like attaching alien power to battery contacts cheers jOERG |
Re: Only boots up in RD Mode
About Estel's getbootstate.c:
- I installed gcc in n900 but i can't compile the file. Too many errors while compiling. I will try with SDK later! - If it works, do you think this will let me charge the battery? About joerg_rw comments: - I reflashed the device to original PR1.3... - I tried to start the phone with 2 different batteries and nothing... - I will clean the battery contacts with a "contact cleaner" liquid... - I don't think it's a silicon burnout, never overclocked and never used another battery but the original one. |
Re: Only boots up in RD Mode
Quote:
Then, despite fact You've suggested to scratch totally one of my posts (and I'm sure You're right about that - just to avoid misunderstanding), I think You'll agree that further update by jvollmann about his typo in command, resulting in false "0" for "charge_full_design", thus leaving only: cat /sys/class/power_supply/bq27200-0/capacity 0 cat /sys/class/power_supply/bq27200-0/charge_full 0 cat /sys/class/power_supply/bq27200-0/charge_now 0 cat /sys/class/power_supply/bq27200-0/time_to_empty_avg 0 cat /sys/class/power_supply/bq27200-0/time_to_empty_now 0 cat /sys/class/power_supply/bq27200-0/time_to_full_now 0 ...as 0 may root from chip's inability to perform ANY calibration (as per 412b and shadowjk's posts, it's performed internally no matter if You use stock kernel or power-kernel), cause jvollmann isn't able to charge via USB cable (only charging battery externally). Mix it with many full reflash procedures - including cold reflash and EMMC reflash (yea, not quite relevant, but You know what i mean), and this may be why capacity, charge_full, charge_now, both "times to empty" and "time to full" are 0's. Then, charge_full_design shown as "2056320" , which is calculated by measuring resistance between ID pin and ground (thus being totally wrong, by the way), mean that ID pin IS probed correctly, right? --- As for Your question, correct values for BSI are: 32-85 - Service battery, result in "LOCAL" bootstate 87-176 - Test battery, result in "TEST" bootstate 280-568 - Normal battery, no bootstate change, continue checking. Everything else - "UNKNOWN" and shutdown, except R&D mode. While 28-568 result in our perfectly fine load, I have no idea how LOCAL or TEST bootstates affect booting. It seems that scripts in /sbin/preinit/ and /etc/ that call getbootstate decide what to do - they're open, so probably, we can check that ;) Quote:
2. IF it works, You'll definitely be able to charge battery - it return exact same state as NORMAL (280-568), so no reasons why Your battery should be threaten differently. Charging with "UNKNOWN" doesn't work in R&D, cause Nokians use "dummy" batteries (false battery attached to main DC power source) in their workdesk's, so they don't want N900 to put power back into main by any means ;) Everything above is correct only if (we assume that it will work at all, of course) there is no real serious hardware damage to charging chip. Which I think is most unlikely - keep in mind that joerg_rw seems to think otherwise, and he is MUCH (threat MUCH as multiplied by n times ;) ) more experienced than me. So only time will tell :) |
Re: Only boots up in RD Mode
Quote:
Quote:
Quote:
Quote:
Again, my suggestion is to clean the contacts and isolating material around the contacts, and maybe even open up the device and clean the inside so there are no "short circuits" caused by dust or residue from getting wet, which will cause the 100k value to get "detuned". Another rather weird idea tha comes to mind is the modem and its firmware are interfering with the OMAP BSI AD-conversion, in a way that switched modem's BSI sensing pin to an output or to internal pullup/down-resistor and so creates additional load to the circuit cheers jOERG |
Re: Only boots up in RD Mode
Huge thanks for clearing things up. As for Your advices...
Quote:
Quote:
|
Re: Only boots up in RD Mode
I opened up the phone, clean the battery contacts (both on phone and battery itself) but the problem persists. I don't have a multimeter here, I'm going to borrow one and try to test the resistance.
Should I still try to compile the getbootstate.c file?? |
| All times are GMT. The time now is 01:23. |
vBulletin® Version 3.8.8