| *** Martix has joined #maemo-ssu | 00:00 | |
| *** Martix has joined #maemo-ssu | 00:05 | |
| *** Martix has quit IRC | 00:07 | |
| *** Guest70244 has quit IRC | 00:12 | |
| ShadowJK | the power increase on plugging in happens with normal device too, with kernelpower it goes away after reading out the sysnode for charger detect | 00:21 |
|---|---|---|
| *** xes has quit IRC | 00:21 | |
| ShadowJK | wtih vanilla kernel it never goes away | 00:22 |
| ShadowJK | So when you force charging from powersource without shorted d+/d-, the increased power drain is always present | 00:22 |
| ShadowJK | about 80mA extra | 00:22 |
| *** Vlad_on_the_road has quit IRC | 00:31 | |
| *** MohammadAG has joined #maemo-ssu | 00:50 | |
| Estel_ | ShadowJK, when I force it using KP, it isn't present | 00:53 |
| Estel_ | no additional 80 mA | 00:53 |
| Estel_ | it's problem in range of 500 additional mA, untill I reset bq24150 via i2cget | 00:54 |
| ShadowJK | force it? | 00:54 |
| Estel_ | using bme replacement | 00:55 |
| Estel_ | forcing detection of dedicated charger | 00:56 |
| kerio | either it's detecting it or it's forced | 01:00 |
| kerio | you can't have both | 01:00 |
| Estel_ | forced, forced | 01:00 |
| *** LauRoman has quit IRC | 01:38 | |
| *** LauRoman has joined #maemo-ssu | 01:42 | |
| *** kolp has quit IRC | 01:45 | |
| *** luf has quit IRC | 02:10 | |
| *** arcean has quit IRC | 03:00 | |
| *** M4rtinK has quit IRC | 03:19 | |
| DocScrutinizer05 | musb core tries to talk to phy via ULPI. If phy is defect, the staemachine in musb core might go mad and spam phy with commands and gets IRQ as answer and resends commands | 04:06 |
| DocScrutinizer05 | almost a "hardware only" thing | 04:07 |
| DocScrutinizer05 | or just maybe KP has "newest leete patches" and now tries to enable boost chargepump in twl4030 ;-P | 04:10 |
| DocScrutinizer05 | just mere luck that this chargepump is missing a capacitor, or we'd burn the N900 by one chip in boostmode while other chip in chargemode | 04:11 |
| DocScrutinizer05 | on beaglebord somebody smoked up his hw this way | 04:12 |
| DocScrutinizer05 | OOOH HAHA | 04:14 |
| DocScrutinizer05 | OTG pin of bq24150 actually switches the chip into boost mode when in I2C mode | 04:15 |
| DocScrutinizer05 | and the OTG pin on bq24150 is connected to... PHY | 04:16 |
| DocScrutinizer05 | so if kernel sends "keep alive" aka watchdog tickling to bq24150 via I2C but forgets to properly initialize the chip (configure OTG pin so it will not force boost mode), you most likely will see nasty behaviour | 04:20 |
| DocScrutinizer05 | particularly with broken PHY chip that obviously doesn't obey to what musb core tells it to do | 04:21 |
| DocScrutinizer05 | when PHY isn't connected to battery anymore, it might even cause wild oscillation between boost (PHY now gets voltage from boostmode via USB, and thus starts to work correctly, disasserting CHARGER/OTG) and proper "normal mode" (PHY works properly from VBUS voltage by boost, and thus doesn't provide OTG pulldown anymore, so bq24150 stops boost) | 04:28 |
| DocScrutinizer05 | this wild oscillation would for sure cause arbitrary power burning, by charging up buffer capacitors on VBUS, then using same enery stored in those buffer capacitors to charge battery, then starting with boostmode again a millisecond later | 04:30 |
| DocScrutinizer05 | obviously attaching a charger will fix it since VBUS always present so PHY won't stop working and thus never asserts OTG erratically | 04:31 |
| DocScrutinizer05 | funny bug | 04:31 |
| DocScrutinizer05 | so funny I even like to check back in schematics now if it's a real possibility, or if I missed sth | 04:33 |
| DocScrutinizer05 | nope, i made a logical mistake, OTG pin needs HIGH voltage to force chip into boost mode, NOT GND level. And the line from PHY to bq24150 (CHRG_DET -> OTG) has even a pulldown R4281 | 04:40 |
| DocScrutinizer05 | anyway PHY depends on GAIA HFCLKOUT, and GAIA is the chip that gets reset by full-reset procedure | 04:46 |
| DocScrutinizer05 | HFCLKOUT is a (iirc) 32768Hz clock derived from RTC | 04:47 |
| DocScrutinizer05 | and it's configurable in sticky GAIA (aka TWL4030) config registers | 04:48 |
| *** unclouded has joined #maemo-ssu | 04:48 | |
| DocScrutinizer05 | without that clock, ULPI communication to musbcore for sure is flawed | 04:49 |
| DocScrutinizer05 | anywy, PHY is conected to quite a number of other subsystems, and it could provide enough material for a master thesis to try and analyze all possible failure modes whith this chip going south in various strange ways | 04:58 |
| DocScrutinizer05 | not even complete removal of that PHY 1707 chip will yield predictable results | 04:59 |
| *** amiconn has quit IRC | 05:04 | |
| *** amiconn_ has joined #maemo-ssu | 05:04 | |
| *** amiconn_ is now known as amiconn | 05:04 | |
| *** LauRoman has quit IRC | 05:59 | |
| *** DocScrutinizer05 has quit IRC | 06:03 | |
| *** DocScrutinizer05 has joined #maemo-ssu | 06:03 | |
| *** nox- has quit IRC | 07:10 | |
| *** M13 has joined #maemo-ssu | 07:18 | |
| *** sunny_s has joined #maemo-ssu | 07:42 | |
| *** M13 has quit IRC | 09:02 | |
| *** M13 has joined #maemo-ssu | 09:03 | |
| *** amiconn has quit IRC | 09:31 | |
| *** amiconn has joined #maemo-ssu | 09:31 | |
| *** M4rtinK has joined #maemo-ssu | 09:37 | |
| *** sunny_s has quit IRC | 09:58 | |
| *** LauRoman has joined #maemo-ssu | 09:59 | |
| *** M4rtinK has quit IRC | 10:03 | |
| *** dhbiker has joined #maemo-ssu | 10:07 | |
| *** sv has joined #maemo-ssu | 12:17 | |
| *** sv has joined #maemo-ssu | 12:17 | |
| *** kolp has joined #maemo-ssu | 12:20 | |
| *** discopig has quit IRC | 12:21 | |
| *** sunny_s has joined #maemo-ssu | 12:34 | |
| *** futpib has joined #maemo-ssu | 12:55 | |
| *** kolp has quit IRC | 13:07 | |
| *** M13 has quit IRC | 13:20 | |
| *** LauRoman has quit IRC | 13:25 | |
| *** sv is now known as discopig | 13:42 | |
| *** FReaper has quit IRC | 13:59 | |
| *** FReaper has joined #maemo-ssu | 14:03 | |
| *** unclouded has quit IRC | 14:23 | |
| *** sv has joined #maemo-ssu | 14:41 | |
| *** discopig has quit IRC | 14:43 | |
| *** sv is now known as discopig | 14:43 | |
| *** lizardo has joined #maemo-ssu | 15:21 | |
| *** kolp has joined #maemo-ssu | 16:00 | |
| *** jonwil has joined #maemo-ssu | 16:11 | |
| jonwil | hi | 16:11 |
| *** arcean has joined #maemo-ssu | 16:20 | |
| *** M13 has joined #maemo-ssu | 17:40 | |
| *** andre__ has quit IRC | 18:26 | |
| *** NIN101 has joined #maemo-ssu | 18:41 | |
| DocScrutinizer05 | hi jonwil | 18:43 |
| *** andre__ has joined #maemo-ssu | 18:49 | |
| *** andre__ has joined #maemo-ssu | 18:49 | |
| * jonwil wonders if all the issues relating to maemo infrastructure were ever solved | 18:49 | |
| jonwil | like the problems with the signature on the repositories | 18:49 |
| *** NIN101 has quit IRC | 18:53 | |
| *** NIN102 has joined #maemo-ssu | 18:53 | |
| DocScrutinizer05 | no, those signature problems are still pending, the nokia-ext guy seems has no pressure to do sth about it | 19:17 |
| DocScrutinizer05 | otoh siganture problem is not related to maemo infra | 19:17 |
| DocScrutinizer05 | right now we have another problem that's actually related to maemo.org: SSL certs, they are expiring by the day now | 19:18 |
| DocScrutinizer05 | and we still don't own the domain | 19:18 |
| *** DocScrutinizer51 has quit IRC | 19:21 | |
| *** DocScrutinizer51 has joined #maemo-ssu | 19:21 | |
| jonwil | So because the domain and stuff are still owned/controlled by Nokia only Nokia can legally obtain SSL certs for it? | 19:29 |
| *** jonwil has quit IRC | 19:34 | |
| kerio | DocScrutinizer05: startssl will allow you to get free certs if you control the matching webserver iirc | 19:42 |
| kerio | either that, or the DNS | 19:42 |
| DocScrutinizer05 | yes, but only lowest "level" of cert. We'd prefer a wildcard cert, and those are only available address-validated not domain-validated, and they cost a few bucks | 19:50 |
| DocScrutinizer05 | anyway warfare seems has opted for startssl for now | 19:52 |
| *** M4rtinK has joined #maemo-ssu | 20:03 | |
| kerio | of course he did | 20:15 |
| kerio | it's /free/ | 20:15 |
| kerio | and it requires barely more than no effort | 20:16 |
| *** arcean_ has joined #maemo-ssu | 20:36 | |
| *** arcean has quit IRC | 20:39 | |
| *** Vlad_on_the_road has joined #maemo-ssu | 20:49 | |
| *** luf has joined #maemo-ssu | 21:00 | |
| *** andre__ has quit IRC | 21:39 | |
| *** BCMM has joined #maemo-ssu | 21:42 | |
| *** andre__ has joined #maemo-ssu | 21:51 | |
| *** xes has joined #maemo-ssu | 21:53 | |
| Estel_ | DocScrutinizer05, when I reset chip, and then enable boost via i2cset like in booston from HEN, I got exact same power usage as just after boot, on that device with broken smth | 22:29 |
| Estel_ | I workarounded it by modifying /etc/event.d/bme to unload module touching bq24150, enabling boost via i2cset, reseting bq24150 via i2c set, loading module again, and forcing dedicated charging | 22:30 |
| Estel_ | strangely, skipping "enable boostmode" step, sticking to only reset command, doesnt work | 22:30 |
| Estel_ | despite that all other symptoms seems to idnicate device is in boostmode since boot | 22:31 |
| Estel_ | fortunatelly, trick with enabling boost and resetting chip in next command works, so no need to put charger in after every boot | 22:31 |
| Estel_ | for sure this device wasn't presenting that behavior from beginning, it seems that usage made this problem appear | 22:32 |
| Estel_ | so I wonder what will come next :P | 22:32 |
| *** NIN102 has quit IRC | 22:41 | |
| *** M13 has quit IRC | 22:50 | |
| *** dhbiker has quit IRC | 23:23 | |
| *** lizardo has quit IRC | 23:40 | |
| *** LauRoman has joined #maemo-ssu | 23:47 | |
Generated by irclog2html.py 2.15.1 by Marius Gedminas - find it at mg.pov.lt!