[N950] Infodump Thread - Page 5 - maemo.org

caco3 | # 41 | 2011-08-15, 07:23 | Report

Originally Posted by Bundyo View Post

Flashing will delete everything...

Is that on purpose?
DId somebody already test if also all the other MyDocs data (images, videos,...) get deleted?

The backups seem to stored in Mydocs/.backups/ as separate zip files:
applications.zip
bookmarks.zip
organizer.zip
settings.zip
contacts.zip
emails.zip
messaging.zip

Thats IMHO very nice.

The Following User Says Thank You to caco3 For This Useful Post:
Wikiwide

MohammadAG | # 42 | 2011-08-15, 10:55 | Report

OneClickFlasher flashes all parts of the image, flashing anually does not. Run OneClickFlasher w/o the device connected and you'll find the files in /tmp (flasher and the images)

The Following 4 Users Say Thank You to MohammadAG For This Useful Post:
jalyst, joerg_rw, qole, Wikiwide

pelago | # 43 | 2011-08-15, 11:13 | Report

Originally Posted by caco3 View Post

The backups seem to stored in Mydocs/.backups/ as separate zip files:
applications.zip
bookmarks.zip
organizer.zip
settings.zip
contacts.zip
emails.zip
messaging.zip

Thats IMHO very nice.

Same as Maemo 5 (and 4...) backup app isn't it?

The Following 2 Users Say Thank You to pelago For This Useful Post:
jalyst, Wikiwide

jalyst | # 44 | 2011-08-15, 14:35 | Report

Originally Posted by jalyst View Post

Kudos Hawaii

*RFMON
*Frame injection
*Mac80211
Is great functionality to eventually migrate to the N9.

But I'm not sure you're going to be able to implement FMTX.
I recall someone (actually from Nok IIRC) claiming the antenna or connection isn't there.
FMRX IIRC should be possible, but apparently not FMTX

Probably not an issue for the N950...
But that's not the point of you guys having the N950's.

Cheers.

@hawaii, you get this?
Do you have reason believe otherwise for N9?

Thank-you.

Last edited by jalyst; 2011-09-06 at 08:47.

The Following User Says Thank You to jalyst For This Useful Post:
Wikiwide

marmistrz | # 45 | 2011-09-05, 18:13 | Report

Why is N950 only for dev & for loan

The Following User Says Thank You to marmistrz For This Useful Post:
Wikiwide

jalyst | # 46 | 2011-09-06, 08:49 | Report

^
You need to read-up way more about the N9, it's still very good compared to the N950.
People srsly need to get over it, sheesh, & your post is totally off-topic anyway...

The Following User Says Thank You to jalyst For This Useful Post:
Wikiwide

Creamy Goodness | # 47 | 2011-09-07, 16:41 | Report

Originally Posted by pelago View Post

Same as Maemo 5 (and 4...) backup app isn't it?

same but worse because you can't choose which ones to restore...

The Following User Says Thank You to Creamy Goodness For This Useful Post:
Wikiwide

pycage | # 48 | 2011-09-07, 18:14 | Report

Originally Posted by marmistrz View Post

Why is N950 only for dev & for loan

Most likely because Nokia only produced a few preproduction batches of the device. So there's not much to sell. And the loaner thing, I was told once, is a legal thing, to not raise the suspicion of bribery.

The Following User Says Thank You to pycage For This Useful Post:
Wikiwide

joerg_rw | # 49 | 2011-09-23, 14:43 | Report

Code:

RM680-22-6_PR_RM680:~# i2cdetect -r 2
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- UU --
10: UU -- -- -- -- -- -- -- -- UU -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: UU -- UU -- -- -- -- UU UU -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- --
50: -- -- -- -- -- 55 -- -- -- -- -- -- -- -- -- --
60: UU -- -- -- -- -- -- -- -- -- -- 6b -- -- -- --
70: -- -- -- -- -- -- -- --
RM680-22-6_PR_RM680:~# echo "        · "UU". Probing was skipped, because this address is currently in use by a driver.  This  strongly  suggests  that
>          there is a chip at this address.
> "
        · UU. Probing was skipped, because this address is currently in use by a driver.  This  strongly  suggests  that
         there is a chip at this address.

RM680-22-6_PR_RM680:~#

RM680-22-6_PR_RM680:~# i2cdump 2 0x6b
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2, address 0x6b, mode byte
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 40 30 0a 51 09 2c 40 ff ff ff ff ff ff ff ff ff    @0?Q?,@.........

[2011-09-23 17:29:10] <DocScrutinizer> candidate: bq24153A rev1.1
[2011-09-23 17:30:13] <DocScrutinizer> B4, B3:For I2C Address 6BH: 00--bq24151, 01–bq24150; 10–bq24153A; 11–NA.
[2011-09-23 17:32:19] <DocScrutinizer> 0x51=0101 0001= 010(vendor ID) | 10(bq24153A) | 001(001: Revision 1.1

[2011-09-23 17:33:45] <DocScrutinizer> Table 3. Status/Control Register (Read/Write)
[2011-09-23 17:33:45] <DocScrutinizer> Memory Location: 00, Reset State: x1xx 0xxx
[2011-09-23 17:34:01] <DocScrutinizer> Table 4. Control Register (Read/Write)
[2011-09-23 17:34:01] <DocScrutinizer> Memory Location: 01, Reset State: 0011 0000
[2011-09-23 17:34:14] <DocScrutinizer> Table 5. Control/Battery Voltage Register (Read/Write)
[2011-09-23 17:34:14] <DocScrutinizer> Memory Location: 02, Reset State: 0000 1010
[2011-09-23 17:34:28] <DocScrutinizer> Table 6. Vender/Part/Revision Register (Read only)
[2011-09-23 17:34:28] <DocScrutinizer> Memory Location: 03, Reset State: 0101 000x
[2011-09-23 17:34:43] <DocScrutinizer> Table 7. Battery Termination/Fast Charge Current Register (Read/Write)
[2011-09-23 17:34:43] <DocScrutinizer> Memory Location: 04, Reset State: 0000 0001
[2011-09-23 17:35:04] <DocScrutinizer> Table 8. Special Charger Voltage/Enable Pin Status Register
[2011-09-23 17:35:04] <DocScrutinizer> Memory location: 05, Reset state: 001X X100
[2011-09-23 17:36:03] <DocScrutinizer> reg0:is:40,doc:x1xx0xxx - match
[2011-09-23 17:36:36] <DocScrutinizer> reg1:is:30,doc:0011 0000 - match
[2011-09-23 17:37:12] <DocScrutinizer> reg2:is:0a,doc:0000 1010 - check
[2011-09-23 17:37:24] <DocScrutinizer> reg3: already checked
[2011-09-23 17:38:04] <DocScrutinizer> reg4:is:09,doc:0000 0001 - may match
[2011-09-23 17:38:46] <DocScrutinizer> reg5:is:2c,doc:001X X100 - seems to match
[2011-09-23 17:39:24] <DocScrutinizer> reg6:is:40,doc

oops
[2011-09-23 17:39:40] <DocScrutinizer> :-DD
[2011-09-23 17:39:43] <DocScrutinizer> Table 9. Safety Limit Register (READ/WRITE, Write only once after reset!)
[2011-09-23 17:39:43] <DocScrutinizer> Memory location: 06, Reset state: 01000000
[2011-09-23 17:39:46] <DocScrutinizer> check
[2011-09-23 17:40:08] <DocScrutinizer> WE HAVE A *WINNER*

charger chip in N950: i2cbus2, addr 0x6B, type BQ24153A http://www.ti.com/product/bq24153a
capable of powering VBUS with 5V@200mA (vboost mode)
according to reg6=40 we are locked down to 4200mV and 950mA max charge current

Code:

RM680-22-6_PR_RM680:~# i2cdump 2 0x55
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2, address 0x55, mode byte
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f    0123456789abcdef
00: 00 00 01 01 3f 31 e0 00 06 00 90 0b 0e 10 da ff    ..???1?.?.?????.
10: ce ff 6b 00 e7 9f ff 7f 00 00 0a 00 0a 00 46 0a    ?.k.??.?..?.?.F?
20: ca 0d 64 00 64 00 9c ff 0a 00 ff ff 18 fc 64 00    ??d.d.?.?...??d.
30: 00 00 50 fb 20 21 06 00 00 00 07 00 XX XX XX XX    ..P? !?...?.XXXX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX    XXXXXXXXXXXXXXXX
RM680-22-6_PR_RM680:~#

also doesn't exactly look like a bq27200 dump :-S
dpkg -L bme
*candidate: /usr/lib/hwi/ic/bq27521.so

closest hit: http://www.ti.com/product/bq27520-g2 - pinout matches with N9 schematics

Originally Posted by

RM680-22-6_PR_RM680:~# stop bme
Sep 24 13:52:51 (none) bme: terminating with exit status 0
RM680-22-6_PR_RM680:~# start bme
Sep 24 13:53:52 (none) bme: bme (May 19 2011 14:59:58) started, pid 5161
Sep 24 13:53:52 (none) bme: [bmeipc.c:bmeipc_open():356] unable to connect to server (sd=4): No such file or directory (2)
Sep 24 13:53:54 (none) bme: [tabby_get_battery_data_cmdline()] Fixed battery type: BL-4D
Sep 24 13:53:54 (none) bme: [tabby.c:tabby_get_battery_data_cmdline():775] Unknown battery type: 'BL-4D': Invalid argument (22)
Sep 24 13:53:54 (none) bme: Battery level OK for boot (4094 mv)
Sep 24 13:53:54 (none) bme: Stop and wait for upstart
Sep 24 13:53:54 (none) bme: Continue
RM680-22-6_PR_RM680:~/DL# ps|grep bme
606 root /usr/lib/hal/hald-addon-bme
5161 bme /usr/sbin/bme_RX-71 -u -l syslog -v 5 -c /usr/lib/hwi/hw/rx71.so
5164 root grep bme
RM680-22-6_PR_RM680:~/DL#

Achieved stable VBUS 5V at USB using:

Code:

RM680-22-6_PR_RM680:~# stop bme; sleep 3; i2cset -y -m 0x07 2 0x6b 0x01 0x05; while true; do sleep 5; i2cget -y 2 0x6b 0x00; i2cset -y -m 0x80 2 0x6b 0x00 0x80; done

funny syslog lines:
Sep 24 16:00:37 (none) kernel: [1135370.167449] twl5031_bcc twl5031_bcc: dcd failed
Sep 24 16:00:40 (none) kernel: [1135373.303527] g_file_storage gadget: File-backed Storage Gadget, version: 20 November 2008
Sep 24 16:00:40 (none) kernel: [1135373.303588] g_file_storage gadget: Number of LUNs=1 Number of buffers=16
(memstick attached, probably unrelated)

to be continued at http://forum.meego.com/showthread.php?p=32140#post32140

Last edited by joerg_rw; 2011-09-25 at 10:32.

The Following 14 Users Say Thank You to joerg_rw For This Useful Post:
divan, DJJonosound, dwaradzyn, eekkelund, GeneralAntilles, Iryus, jalyst, minimos, momcilo, OVK, qole, sicelo, tissot, Wikiwide

momcilo | # 50 | 2011-09-23, 15:04 | Report

Originally Posted by joerg_rw View Post

Code:

RM680-22-6_PR_RM680:~# i2cdetect -r 2
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-2 using read byte commands.
I will probe address range 0x03-0x77.
Continue? [Y/n]
     0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00:          -- -- -- -- -- -- -- -- -- -- -- UU --
10: UU -- -- -- -- -- -- -- -- UU -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: UU -- UU -- -- -- -- UU UU -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- UU -- -- -- --
50: -- -- -- -- -- 55 -- -- -- -- -- -- -- -- -- --
60: UU -- -- -- -- -- -- -- -- -- -- 6b -- -- -- --
70: -- -- -- -- -- -- -- --
RM680-22-6_PR_RM680:~# echo "        · "UU". Probing was skipped, because this address is currently in use by a driver.  This  strongly  suggests  that
>          there is a chip at this address.
> "
        · UU. Probing was skipped, because this address is currently in use by a driver.  This  strongly  suggests  that
         there is a chip at this address.

RM680-22-6_PR_RM680:~#

Is there any unexpected hardware there?
http://www.nxp.com/acrobat_download2...s/SELGUIDE.PDF

Last edited by momcilo; 2011-09-23 at 15:12.

The Following 2 Users Say Thank You to momcilo For This Useful Post:
mece, Wikiwide