^^ Well, that philosophy sound a little strange coming from you. We can't do much hardware hacking without root write access to the root filesystem "/". At least not, unless you know how to apply one of your unbreakable SW-JIG mods to gain temporary root somehow. All you really need is busybox,which contain the majority of commands and shells needed for normal system operations.
Accessing uart on Galaxy Nexus i9250
- Thread starter dpc.ucore.info
- Start date
Well.. im generating content for XDATV now... i have to move slower in order to make things reproducable... basically i log my work more thoroughly.
I want to start with taking a long hard look at the diagnostic port under the SIM card. I will be hooking up a logic analyzer to it and finding information on a stock device.
You mean this one? Are you sure its a diagnostic port? Seem just like extra solder pads for the SIM connectors. If so, I guess it could be useful to sniff SIM traffic, but I don't think you can actually use it for anything else without more serious SIM reading/writing equipment... If you really want to know whats going on in your SIM, you might wanna get a programmable SIM + sniffer card, where you can read and re-program both STK and new features. May I ask why you think this may be useful/important?
Attachments
Last edited:
No, I mean this one..
I modified my rear case to be able to get to this port.
Also I'm taking Linux+ and that's slowing me down too
alright... rooted and installed busybox in CASUAL format. I pushed the scripts to the SVN repository as well. http://code.google.com/p/android-casual/source/detail?r=117 I'll release that later.
Anyway... here we go. I'm not finding what you were looking for.
I'm not seeing the dialer service.
Anyway... here we go. I'm not finding what you were looking for.
Code:
shell@android:/ # find / -iname "*service*"
/system/app/DefaultContainerService.apk
/system/app/DefaultContainerService.odex
/system/app/GoogleLoginService.apk
/system/app/GoogleServicesFramework.apk
/system/bin/sensorservice
/system/bin/service
/system/bin/servicemanager
/system/framework/services.jar
/system/framework/services.odex
/system/lib/libcameraservice.so
/system/lib/libmediaplayerservice.so
/system/lib/libsensorservice.so
/system/vendor/lib/libPVRScopeServices.so
/data/data/com.google.android.gsf/databases/gservices.db
/data/data/com.google.android.gsf/databases/gservices.db-journal
/data/data/com.google.android.gsf/shared_prefs/CheckinService.xml
/data/data/com.google.android.gsf/shared_prefs/StatsUploadService.xml
/data/data/com.google.android.gsf/shared_prefs/EventLogService.xml
/data/data/com.android.nfc3/shared_prefs/NfcServicePrefs.xml
/data/data/com.rageconsulting.android.lightflowlite/shared_prefs/com.rageconsulting.android.lightflowlite.service.LightFlowService.PREFS.xml
/data/dalvik-cache/system@app@GoogleLoginService.apk@classes.dex
/data/dalvik-cache/system@app@GoogleServicesFramework.apk@classes.dex
/data/system/registered_services
/data/backup/com.google.android.backup.BackupTransportService
/dev/socket/property_service
Code:
shell@android:/ # shell@android:/ # hexdump -C /mnt/.lfs/param.blk
sh: shell@android:/: not found
127|shell@android:/ # hexdump: /mnt/.lfs/param.blk: No such file or directory
sh: hexdump:: not found
127|shell@android:/ # cd /mnt
shell@android:/mnt # la
asec
obb
sdcard
secure
shell@android:/mnt #
try *#*#[android_secret_code]#*#*
PhoneUtil menu: *#*#7284#*#*
ServiceMode menu : *#*#197328640#*#*
you should notice a servicemode.apk in system/app
if the dialer codes dont work, you can always go old school and install any cut free in play store, select activity > all activities.. for a list of all available actions.
you guys are great!
Tremendous work!
thanks.
PhoneUtil menu: *#*#7284#*#*
ServiceMode menu : *#*#197328640#*#*
you should notice a servicemode.apk in system/app
if the dialer codes dont work, you can always go old school and install any cut free in play store, select activity > all activities.. for a list of all available actions.
you guys are great!
Tremendous work!
thanks.
Last edited:
Ha! That look like a modified JTAG header!
Ouch, that is weird. Can you post (to pastebin) the output of:
Code:
[SIZE=2][B]HINT[/B]: type "ash" first so that you can use command completion, and thus avoid a lot of typing!
$ su
# busybox ash
# mount
# busybox ls -al /system/app/
# busybox ls -al /system/bin/
# busybox ls -al /system/xbin/
# busybox ls -al /mnt/[/SIZE]Seem that hexdump is not included in your busybox... try to find it. Perhaps in one of the "other" toolboxes from GalaxyS hackpack? Its not really needed, as you can just use a hexeditor on your PC, after having copied the file.
Last edited:
I got the output you wanted here: http://pastebin.com/G89SnRcg
Busybox has hexdump.. it can't find the param.blk.
Also, none of the service modes are working on this i9250.
Busybox has hexdump.. it can't find the param.blk.
Code:
shell@android:/ # hexdump -C /mnt/.lfs/param.blk
hexdump: /mnt/.lfs/param.blk: No such file or directory
ash: precmd: not found
shell@android:/ # which hexdump
/system/bin/hexdumpAlso, none of the service modes are working on this i9250.
Suddenly I got a really creepy feeling that the Samsung Dev's are closely following what we do here. (Not a real surprise, since they rarely seem to know what they do themselves, but their silence is.) I don't recognize much in that FS anymore, as I only run GB, I guess we need to get an ICS dev in here, who knows his way around this place. BTW. Is your device a CDMA version by any chance? (Does your interior match with that of Chipworks and iFixit's teardowns?)
Samsung is always watching
This is an unlocked GSM version. I think this is the 'official' device. Not the carrier device.
Very strange that you don't have .lfs directory... Perhaps it's hidden?
So to get you on your command line feet. (See "code" edit above.)
In order to avoid an awful lot of unnecessary re-writing, all commands you don't want to write "busybox" in front of, need to be soft-linked with:
(For some reason this doesn't work for me right now...) Then you need to set your file permission so that your xbin directory lists something as follows:
(Of course your path to the busybox binary must match with where you have it.) In fact, this should already have been setup by your root tool...
Can you also post the output (right after you have rebooted) of:
(You need to send it to a file first or you risk overflowing your terminal buffer.) For a "live" kernel message log, you can use:
Use CTRL-C to exit.
EDIT: See if you can get anywhere with this:
So to get you on your command line feet. (See "code" edit above.)
In order to avoid an awful lot of unnecessary re-writing, all commands you don't want to write "busybox" in front of, need to be soft-linked with:
Code:
# ln [-s] <target> <filename>
Code:
# busybox ls -al /system/xbin/
...
lrwxrwxrwx 1 0 0 20 Dec 15 14:55 ash -> /system/xbin/busybox
-rwsr-xr-x 1 0 2000 1075144 Dec 15 14:55 busybox
...Can you also post the output (right after you have rebooted) of:
Code:
# dmesg >/mnt/sdcard/dmesg.log
# cat /proc/cmdline
Code:
# cat /proc/kmsgEDIT: See if you can get anywhere with this:
Code:
[B]*#*#4636#*#*[/B]
Last edited:
dangit... that code worked. I don't know what's going on because now SMS stopped working. I can't send any text messages. Rebooted, same thing. I don't think I made any changes, but something definately happened when I went into that last code you posted.
Check to see if you didn't accidentally clobber your SMSC setting... I forget where that is on stock ICS though. I know having it go poof for no reason at all was common on Touchwizz Gingerbread.
That was it.. that fixed it. For some reason that field is destroyed when you enter that menu. It does not persist through entering and exiting the *#*#INFO#*#* menu. So here's the fix....
From dialer type: *#*#4636#*#*
Select "Phone Information"
In the SMSC field (for AT&T):07913121139418F0 then update, then refresh
I used CASUAL Keyboard Input script to make it easier to type... it sucks doing long hexadecimal from Android Keyboard...
You can download the CASUAL I used here: http://www.mediafire.com/?c1nd7yvoox61s39
Anyway... Back on track.
Last edited:
That's probably made to not be persistent, just so that things like you just mentioned doesn't happen. From my i9100:GB experience, you have to "back-out" in order to make changes persistent. Hit menu-button and then "back". If you just hit "exit", it doesn't save. Other changes may require reboot.
I have mad fast typing skills
This is in battery charging mode.
I was able to obtain that last one by typing in 'gedit'
then copy-paste
This is in battery charging mode.
Code:
<hit enter twice to activate fiq debugger>
debug>
debug>
debug>
debug>
debug>
debug>
debug>
debug>
debug>
debug> help
FIQ Debugger commands:
pc PC status
regs Register dump
allregs Extended Register dump
bt Stack trace
reboot Reboot
irqs Interupt status
kmsg Kernel log
version Kernel version
sleep Allow sleep while in FIQ
nosleep Disable sleep while in FIQ
console Switch terminal to console
cpu Current CPU
cpu <number> Switch to CPU<number>
debug> Kernel Debugger commands:
ps Process list
sysrq sysrq options
sysrq <param> Execute sysrq with <param>
debug>
Code:
debug> ps
pid ppid prio task pc
1 0 120 swapper R running
2 0 120 kthreadd S c0583e20
3 2 120 ksoftirqd/0 S c0583e20
4 2 120 kworker/0:0 S c0583e20
5 2 120 kworker/u:0 S c0583e20
6 2 0 migration/0 S c0583e20
7 2 0 migration/1 S c0583e20
8 2 120 kworker/1:0 S c0583e20
9 2 120 ksoftirqd/1 S c0583e20
10 2 100 khelper S c0583e20
11 2 100 suspend S c0583e20
12 2 49 irq/329-pogo_ S c0583e20
13 2 120 sync_supers S c0583e20
14 2 120 bdi-default S c0583e20
15 2 100 kblockd S c0583e20
16 2 100 omap2_mcspi S c0583e20
17 2 120 khubd S c0583e20
18 2 120 twl6030-irq S c0583e20
19 2 49 irq/374-TWL60 S c0583e20
20 2 120 kworker/0:1 S c0583e20
21 2 100 cfg80211 S c0583e20
22 2 100 musb-otg S c0583e20
23 2 0 kinteractiveu S c0583e20
24 2 120 kworker/0:2 S c0583e20
25 2 120 khungtaskd S c0583e20
26 2 120 kswapd0 S c0583e20
27 2 120 fsnotify_mark S c0583e20
28 2 100 crypto S c0583e20
41 2 100 hdmi_hotplug S c0583e20
42 2 100 hdcp S c0583e20
43 2 120 firmware/hdcp D c0583e20
44 2 100 dsscomp_apply S c0583e20
45 2 100 dsscomp_apply S c0583e20
46 2 100 dsscomp_apply S c0583e20
47 2 100 dsscomp_cb S c0583e20
48 2 49 irq/335-sii92 S c0583e20
49 2 120 firmware/duca D c0583e20
50 2 100 pvr_timer S c0583e20
51 2 100 bmp180_wq S c0583e20
52 2 100 sec_jack_wq S c0583e20
53 2 120 kworker/u:1 S c0583e20
54 2 49 irq/184-fsa94 S c0583e20
55 2 49 irq/164-fsa94 S c0583e20
56 2 49 irq/159-temp_ S c0583e20
57 2 49 irq/246-tshut S c0583e20
58 2 49 irq/151-twl60 S c0583e20
59 2 120 mtdblock0 S c0583e20
66 2 100 f_mtp S c0583e20
67 2 120 file-storage S c0583e20
68 2 120 kworker/1:1 S c0583e20
69 2 120 firmware/mms1 D c0583e20
70 2 100 gp2a_wq S c0583e20
71 2 49 irq/379-rtc0 S c0583e20
72 2 100 khotplug S c0583e20
73 2 100 binder S c0583e20
74 2 49 irq/131-ABE S c0583e20
75 2 120 kworker/u:2 S c0583e20
76 2 120 kworker/u:3 S c0583e20
77 2 100 twl6040-codec S c0583e20
78 2 100 twl6040-hf S c0583e20
79 2 100 twl6040-hs S c0583e20
80 2 100 twl6040-ep S c0583e20
81 2 120 mmcqd/0 S c0583e20
82 2 120 mmcqd/0boot0 S c0583e20
83 2 120 mmcqd/0boot1 S c0583e20
84 2 110 krfcommd S c0583e20
85 2 49 irq/142-omap_ S c0583e20
86 2 49 irq/143-omap_ S c0583e20
87 2 100 mipi_tx_wq S c0583e20
88 2 100 mipi_tx_raw_w S c0583e20
89 2 100 mipi_cmd_wq S c0583e20
90 53 120 kworker/u:1 S c0583e20
91 2 2 dhd_watchdog S c0583e20
92 2 1 dhd_dpc S c0583e20
93 2 120 dhd_sysioc S c0583e20
debug>
CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.5 | VT102 | Offline
Code:
debug> console
console mode
[ 3.190765] cannot apply mgr(lcd) on inactive device
[ 3.196411] omapfb omapfb: failed to apply dispc config
[ 3.201934] cannot apply mgr(tv) on inactive device
[ 3.207244] omapfb omapfb: failed to apply dispc config
[ 3.212799] cannot apply mgr(lcd2) on inactive device
[ 3.218048] omapfb omapfb: failed to apply dispc config
[ 3.225769] regulator_init_complete: VDAC: disabling
[ 3.231872] omaplfb OMAPLFBInitFBDev: Device 0: Requesting 4 TILER 2D framebuffers
[ 3.240051] ## wifi_probe
[ 3.243194] wifi_set_power = 1
[ 3.502685] wifi_set_carddetect = 1
[ 3.514373]
[ 3.514373] Dongle Host Driver, version 5.90.125.94
[ 3.514404] Compiled in drivers/net/wireless/bcmdhd on Nov 21 2011 at 19:05:54
[ 3.639862] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 3.692779] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 3.712341] mmc1: new high speed SDIO card at address 0001
[ 3.719848] F1 signature read @0x18000000=0x16844330
[ 3.734313] DHD: dongle ram size is set to 294912(orig 294912)
[ 3.741424] wl_create_event_handler thr:59 started
[ 3.746520] dhd_attach thr:5a started
[ 3.750335] dhd_attach thr:5b started
[ 3.754150] dhd_attach thr:5c started
[ 3.757995] wifi_get_mac_addr
[ 3.763336] Broadcom Dongle Host Driver: register interface [wlan0] MAC: 00:90:4c:11:22:33
[ 3.772216] wifi_set_power = 0
[ 4.031829] =========== WLAN placed in RESET ========
[ 4.037994] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'jig'
CTRL-A Z for help |115200 8N1 | NOR | Minicom 2.5 | VT102 | OfflineI was able to obtain that last one by typing in 'gedit'
Code:
console
Code:
debug> help
FIQ Debugger commands:
pc PC status
regs Register dump
allregs Extended Register dump
bt Stack trace
reboot Reboot
irqs Interupt status
kmsg Kernel log
version Kernel version
sleep Allow sleep while in FIQ
nosleep Disable sleep while in FIQ
console Switch terminal to console
cpu Current CPU
cpu <number> Switch to CPU<number>
debug> Kernel Debugger commands:
ps Process list
sysrq sysrq options
sysrq <param> Execute sysrq with <param>
debug> pc
pc c006b630 cpsr 90000013 mode SVC
debug> regs
r0 c073ff28 r1 3b9aca00 r2 2ce2a872 r3 00000000
r4 c111a100 r5 c073ff28 r6 09a138c5 r7 00000002
r8 09b8f872 r9 00000002 r10 00000000 r11 c073ff5c mode SVC
ip fffffff1 sp c073ff28 lr c007f004 pc c006b630 cpsr 20000013 spsr ffffffff
debug> allregs
r0 c073ff28 r1 3b9aca00 r2 41c04235 r3 00000000
r4 c111a100 r5 c073ff28 r6 5a306dc9 r7 00000002
r8 5a315c35 r9 00000002 r10 00000000 r11 c073ff5c mode SVC
ip fffffff1 sp c073ff28 lr c007f004 pc c006b630 cpsr 00000013 spsr ffffffff
svc: sp c073fd68 lr c006145c spsr 00000013
abt: sp c0794d2c lr c0053680 spsr 20000193
und: sp c0794d38 lr c00537c0 spsr 20000093
irq: sp c0794d20 lr c0053480 spsr 00000193
fiq: r8 00000000 r9 00406edc r10 00000000 r11 00000000 r12 00000000
fiq: sp 00000000 lr 00000000 spsr 00000000
debug> bt
pid: 0 comm: swapper
r0 c073ff28 r1 3b9aca00 r2 2f1fe314 r3 00000000
r4 c111a100 r5 c073ff28 r6 bec5a2a8 r7 00000002
r8 bec69114 r9 00000002 r10 00000000 r11 c073ff5c mode SVC
ip fffffff1 sp c073ff28 lr c007f004 pc c006b630 cpsr 80000013 spsr ffffffff
pc: c006b630 (omap4_enter_idle_wfi+0x40/0xdc), lr c007f004 (omap44xx_32k_read+0x18/0x30), sp c073ff28, fp c073ff5c
pc: c006b630 (omap4_enter_idle_wfi+0x40/0xdc), lr c007f004 (omap44xx_32k_read+0x18/0x30), sp c073ff28, fp c073ff5c
pc: c03ab6dc (cpuidle_idle_call+0x9c/0x130), lr c007f004 (omap44xx_32k_read+0x18/0x30), sp c073ff60, fp c073ff8c
pc: c0054fa0 (cpu_idle+0xc4/0x104), lr c007f004 (omap44xx_32k_read+0x18/0x30), sp c073ff90, fp c073ffac
pc: c05762f4 (rest_init+0xa0/0xa4), lr c007f004 (omap44xx_32k_read+0x18/0x30), sp c073ffb0, fp c073ffc4
pc: c00089d0 (start_kernel+0x2ac/0x300), lr c007f004 (omap44xx_32k_read+0x18/0x30), sp c073ffc8, fp c073fff4
pc: 80008040 (0x80008040), lr c007f004 (omap44xx_32k_read+0x18/0x30), sp c073fff8, fp (null)
debug> irqs
irqnr total since-last status name
39: 0 0 0 TWL6030-PIH
41: 0 0 0 l3-dbg-irq
42: 0 0 0 l3-app-irq
43: 2 2 0 prcm
44: 114 114 0 DMA
52: 0 0 0 gpmc
57: 13 13 0 OMAP DISPC
58: 1 1 0 mailbox-1
60: 0 0 0 omap-iommu.1
69: 1920 1920 0 gp timer
85: 35 35 0 omapdss_dsi1
88: 1091 1091 0 omap_i2c
89: 0 0 0 omap_i2c
91: 466 466 400 mmc1
93: 8 8 0 omap_i2c
94: 200 200 0 omap_i2c
99: 0 0 104 mpu_p1
103: 0 0 104 mpu_dma
106: 63 63 0 debug
112: 0 0 0 omap_wdt
115: 72 72 400 mmc0
124: 0 0 0 musb-hdrc
125: 0 0 0 musb-hdrc
131: 0 0 0 ABE
132: 0 0 0 omap-iommu.0
133: 0 0 0 OMAP HDMI
142: 0 0 0 omap_emif
143: 0 0 0 omap_emif
144: 0 0 0 McPDM
151: 1 1 0 twl6040
159: 1 1 1 temp_sensor
160: 0 0 403 sec_headset_detect
163: 0 0 403 gpio_keys
164: 1 1 508 fsa9480
168: 0 0 403 gpio_keys
177: 0 0 401 nfc_irq
181: 0 0 403 proximity_int
184: 1 1 504 fsa9480_external_id
190: 0 0 403 gpio_keys
205: 0 0 401 mpuirq
206: 0 0 508 mms_ts
223: 0 0 403 hpd
246: 0 0 401 tshut
280: 2 2 504 phone_active
281: 0 0 504 pogo_data
282: 0 0 401 accelirq
329: 0 0 403 pogo_det
335: 0 0 504 sii9234
336: 0 0 401 compassirq
337: 1 1 508 bt host_wake
374: 0 0 400 TWL6030-VLOW
379: 0 0 400 rtc0
389: 0 0 8400 twl6040_irq_plug
393: 1 1 8400 twl6040_irq_ready
LOC 0: 841 841
Last edited:
And this may be the most complete bootlog I've ever seen!
Code:
[Thermal] OK to boot
Initialize runtime thermal monitoring ...done!
-- OMAP 00004460 (version 04460e11) PPA release 1.6.1 Hash 30639809--
Device type: HS, DEBUG OFF
CPFROM HAL API support integrated
THERMAL support integrated: Run Time + Boot time
HDCP support integrated
-- PROD PPA RC3.2.3 --
Reset reason = 00037ba2
PRM_RSTST = 00000002
PPA freed 2992 bytes
Texas Instruments X-Loader 1.41 (Nov 16 2011 - 16:28:45)
Starting OS Bootloader from MMC/SD1 ...
EXCEPTION : CM_CLKMODE_DPLL_ABE = 0x7
EXCEPTION : CM_IDLEST_DPLL_ABE = 0x1
EXCEPTION : CM_CLKSEL_DPLL_ABE = 0x804018
EXCEPTION : CM_CLKMODE_DPLL_CORE = 0xf
EXCEPTION : CM_IDLEST_DPLL_CORE = 0x1
EXCEPTION : CM_CLKSEL_DPLL_CORE = 0x7d05
EXCEPTION : CM_CLKMODE_DPLL_PER = 0x107
EXCEPTION : CM_IDLEST_DPLL_PER = 0x1
EXCEPTION : CM_CLKSEL_DPLL_PER = 0x1400
EXCEPTION : CM_CLKMODE_DPLL_MPU = 0x117
EXCEPTION : CM_IDLEST_DPLL_MPU = 0x1
EXCEPTION : CM_CLKSEL_DPLL_MPU = 0x807d07
CFG_LOADADDR = 0xa0208000
1st instruct = 0xEA000007
[ __omap_twl6030_init_vbat_cfg :49] SA_PHOENIX_START_CONDITION = 0x4a
[ __omap_twl6030_init_vbat_cfg :54] SA_PH_CFG_VBATLOWV = 0x80
[ __omap_twl6030_init_vbat_cfg :63] SA_PH_CFG_VBATLOWV = 0x80
[ __omap_twl6030_init_vbat_cfg :86] SA_BBSPOR_CFG = 0x78
====== VCELL : 381375, SOC : 49, nType : 5 ======
[Charger] nScaledVCELL : 381375000, nDesriedSOC, : 62, nMaxSOC : 82, nMinSOC : 42
[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
[ __omap_usbacc_test_donwload_by_musb :280] nDeviceType : 0x5
[ omap_usbacc_get_reboot_reason :333] nJigStatus = 0x00000003
[ __sbl_board_hw_init_late :719] final reboot mode in cable = 0x40000
[ __sbl_board_hw_init_late :730] Wake up by TA / USB / JIG
* FB base addr = 0xbea70000!
* PANEL_S6E8AA0_ID_READ : 0x12, 0x8e, 0x9f.
[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
dev : 5
[sbl_board_charger_init_post] : Succeed set model data : 0x78!!!!!
====== VCELL : 381500, SOC : 50, nType : 5 ======
[Charger] nScaledVCELL : 381500000, nDesriedSOC, : 62, nMaxSOC : 82, nMinSOC : 42
[ omap_power_get_reset_source :47] PRM_RSTST : 0x1
[ __omap_usbacc_test_donwload_by_musb :280] nDeviceType : 0x5
[ omap_usbacc_get_reboot_reason :333] nJigStatus = 0x00000003
[ __sbl_board_hw_init_late :719] final reboot mode in cable = 0x40000
[ __sbl_board_hw_init_late :730] Wake up by TA / USB / JIG
* FB base addr = 0xbea70000!
* PANEL_S6E8AA0_ID_READ : 0x12, 0x8e, 0x9f.
[ omap_power_get_reset_source :47] PRM_RSTST : 0x1
message.command =
message.status =
message.recovery =
<hit enter twice to activate fiq debugger>
[Thermal] OK to boot
Initialize runtime thermal monitoring ...done!
-- OMAP 00004460 (version 04460e11) PPA release 1.6.1 Hash 30639809--
Device type: HS, DEBUG OFF
CPFROM HAL API support integrated
THERMAL support integrated: Run Time + Boot time
HDCP support integrated
-- PROD PPA RC3.2.3 --
Reset reason = 0003fba2
PRM_RSTST = 00000002
PPA freed 2992 bytes
Texas Instruments X-Loader 1.41 (Nov 16 2011 - 16:28:45)
Starting OS Bootloader from MMC/SD1 ...
EXCEPTION : CM_CLKMODE_DPLL_ABE = 0x7
EXCEPTION : CM_IDLEST_DPLL_ABE = 0x1
EXCEPTION : CM_CLKSEL_DPLL_ABE = 0x804018
EXCEPTION : CM_CLKMODE_DPLL_CORE = 0xf
EXCEPTION : CM_IDLEST_DPLL_CORE = 0x1
EXCEPTION : CM_CLKSEL_DPLL_CORE = 0x7d05
EXCEPTION : CM_CLKMODE_DPLL_PER = 0x107
EXCEPTION : CM_IDLEST_DPLL_PER = 0x1
EXCEPTION : CM_CLKSEL_DPLL_PER = 0x1400
EXCEPTION : CM_CLKMODE_DPLL_MPU = 0x117
EXCEPTION : CM_IDLEST_DPLL_MPU = 0x1
EXCEPTION : CM_CLKSEL_DPLL_MPU = 0x807d07
CFG_LOADADDR = 0xa0208000
1st instruct = 0xEA000007
[ __omap_twl6030_init_vbat_cfg :49] SA_PHOENIX_START_CONDITION = 0x8
[ __omap_twl6030_init_vbat_cfg :54] SA_PH_CFG_VBATLOWV = 0x80
[ __omap_twl6030_init_vbat_cfg :63] SA_PH_CFG_VBATLOWV = 0x80
[ __omap_twl6030_init_vbat_cfg :86] SA_BBSPOR_CFG = 0x78
====== VCELL : 381375, SOC : 50, nType : 5 ======
[Charger] nScaledVCELL : 381375000, nDesriedSOC, : 62, nMaxSOC : 82, nMinSOC : 42
[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
[ __omap_usbacc_test_donwload_by_musb :280] nDeviceType : 0x5
[ omap_usbacc_get_reboot_reason :333] nJigStatus = 0x00000003
[ __sbl_board_hw_init_late :719] final reboot mode in cable = 0x40000
[ __sbl_board_hw_init_late :730] Wake up by TA / USB / JIG
* FB base addr = 0xbea70000!
* PANEL_S6E8AA0_ID_READ : 0x12, 0x8e, 0x9f.
[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
<hit enter twice to activate fiq debugger>
Communications established====== VCELL : 381375, SOC : 50, nType : 5 ======
[Charger] nScaledVCELL : 381375000, nDesriedSOC, : 62, nMaxSOC : 82, nMinSOC : 42
* FB base addr = 0xbea70000!
* PANEL_S6E8AA0_ID_READ : 0x12, 0x8e, 0x9f.
[ omap_power_get_reset_source :47] PRM_RSTST : 0x2
<hit enter twice to activate fiq debugger>
debug> console
console mode
[ 3.320373] cannot apply mgr(lcd) on inactive device
[ 3.325805] omapfb omapfb: failed to apply dispc config
[ 3.331359] cannot apply mgr(tv) on inactive device
[ 3.336578] omapfb omapfb: failed to apply dispc config
[ 3.341949] cannot apply mgr(lcd2) on inactive device
[ 3.347167] omapfb omapfb: failed to apply dispc config
[ 3.354888] regulator_init_complete: VDAC: disabling
[ 3.361053] omaplfb OMAPLFBInitFBDev: Device 0: Requesting 4 TILER 2D framebuffers
[ 3.369232] ## wifi_probe
[ 3.371917] wifi_set_power = 1
[ 3.631866] wifi_set_carddetect = 1
[ 3.647338]
[ 3.647338] Dongle Host Driver, version 5.90.125.94
[ 3.647338] Compiled in drivers/net/wireless/bcmdhd on Nov 21 2011 at 19:05:54
[ 3.764984] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 3.817810] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 3.837463] mmc1: new high speed SDIO card at address 0001
[ 3.844818] F1 signature read @0x18000000=0x16844330
[ 3.859436] DHD: dongle ram size is set to 294912(orig 294912)
[ 3.866546] wl_create_event_handler thr:5b started
[ 3.871673] dhd_attach thr:5c started
[ 3.875488] dhd_attach thr:5d started
[ 3.879272] dhd_attach thr:5e started
[ 3.883148] wifi_get_mac_addr
[ 3.888519] Broadcom Dongle Host Driver: register interface [wlan0] MAC: 00:90:4c:11:22:33
[ 3.897430] wifi_set_power = 0
[ 4.157012] =========== WLAN placed in RESET ========
[ 4.163116] fsa9480 4-0025: cable detect change, from 'unknown/none' to 'uart'
[ 4.171203] twl_rtc twl_rtc: setting system clock to 2012-05-13 00:25:12 UTC (1336868712)
[ 4.180816] Freeing init memory: 276K
[ 4.187561] init (1): /proc/1/oom_adj is deprecated, please use /proc/1/oom_score_adj instead.
[ 4.214172] max17040 4-0036: online = 1 vcell = 3795000 soc = 48 status = 3 health = 1 temp = 330 charger status = 0
[ 4.288116] keychord: using input dev tuna-gpio-keypad for fevent
[ 4.354614] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: (null)
[ 4.446746] mms_ts 3-0048: fw version 0x62 already present
[ 4.454498] mms_ts 3-0048: Melfas MMS-series touch controller initialized
[ 4.757202] omap-rproc omap-rproc.1: Loaded BIOS image ducati-m3.bin, size 4489868
[ 4.765838] omap-rproc omap-rproc.1: BIOS image version is 2
[ 4.785888] omap-iommu omap-iommu.0: iommu_get: ducati qos_request
[ 4.806243] omap_hwmod: ipu: failed to hardreset
[ 4.811035] omap-iommu omap-iommu.0: ducati: version 2.1
[ 4.822448] omap-rproc omap-rproc.1: remote processor ipu is now up
[ 4.835571] omap_rpmsg_mbox_callback: received echo reply from ipu !
[ 4.842071] omap_rpmsg_mbox_callback: received echo reply from ipu !
[ 4.848541] omap_rpmsg_mbox_callback: received echo reply from ipu !
[ 4.855072] omap_rpmsg_mbox_callback: received echo reply from ipu !
[ 4.861816] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sample addr 0x32
[ 4.869812] virtio_rpmsg_bus virtio0: creating channel rpmsg-client-sample addr 0x33
[ 4.877899] virtio_rpmsg_bus virtio0: creating channel rpmsg-omx addr 0x3c
[ 4.885192] rpmsg_omx rpmsg-omx0: new OMX connection srv channel: 1024 -> 60!
[ 5.959960] EXT4-fs (mmcblk0p12): recovery complete
[ 5.974639] EXT4-fs (mmcblk0p12): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=panic
[ 6.021484] virtio_rpmsg_bus virtio1: creating channel rpmsg-omx addr 0x3c
[ 6.029602] rpmsg_omx rpmsg-omx1: new OMX connection srv channel: 1024 -> 60!
[ 6.170227] EXT4-fs (mmcblk0p11): recovery complete
[ 6.178833] EXT4-fs (mmcblk0p11): mounted filesystem with ordered data mode. Opts: nomblk_io_submit,errors=panic
[ 6.199371] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[ 6.269744] android_usb: already disabled
[ 6.274810] mtp_bind_config
[ 6.277740] adb_bind_config
[ 6.297790] HDCP: loaded keys
[ 6.481079] warning: `adbd' uses 32-bit capabilities (legacy support in use)
[ 6.488433] adb_open
[ 6.702026] init: sys_prop: permission denied uid:1001 name:net.rmnet1.dns1
[ 6.709808] init: sys_prop: permission denied uid:1001 name:net.rmnet1.dns2
[ 6.718780] init: sys_prop: permission denied uid:1001 name:net.rmnet1.gw
[ 6.726196] init: sys_prop: permission denied uid:1001 name:net.rmnet2.dns1
[ 6.733612] init: sys_prop: permission denied uid:1001 name:net.rmnet2.dns2
[ 6.741455] init: sys_prop: permission denied uid:1001 name:net.rmnet2.gw
[ 6.749481] PVR: Installing MISR with cookie c0800c2c
[ 6.757415] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie c7aa2700
[ 6.766174] PVR: OSUnMapPhysToLin: unmapping 65535 bytes from c8be0000
[ 6.773162] PVR: SysFinalise: Version string: SGX revision = 1.2.0
[ 6.797027] [MODEM_IF] misc_open : umts_boot0
[ 6.801666] omap_hsi omap_hsi.0: HSI clock is now 96000000
[ 6.824066] omap_hsi omap_hsi.0: Entering RX wakeup in 3 wires mode (no CAWAKE)
[ 6.831634] [MODEM_IF] xmm6260_off()
[ 6.835327] [MODEM_IF] PA EVENT : reset =0, pa=1
[ 6.840057] [MODEM_IF] umts_ipc0 state changed: OFFLINE
[ 6.845367] [MODEM_IF] xmm6260_on()
[ 6.866821] SMC: SecureCRC=0xBC7458DC
[ 6.959045] [MODEM_IF] PA EVENT : reset =1, pa=0
[ 7.042053] SMC PA: INFO 00000001 00:00:00.000 ------ ------ --------------- Booting... (t=00:25:15.356) SMCXG01.04p11.32196 /Widevine Integration
[ 7.058532] SMC PA: INFO 00000002 00:00:00.017 ------ ------ --------------- Booted
[ 7.238128] [MODEM_IF] misc_release : umts_boot0
[ 7.245147] omap_hsi omap_hsi.0: hsi_write_cancel ch 0
[ 7.251708] omap_hsi omap_hsi.0: __hsi_write_cancel : -125
[ 7.258941] omap_hsi omap_hsi.0: hsi_read_cancel ch 0
[ 7.265106] omap_hsi omap_hsi.0: __hsi_read_cancel : -125
[ 7.270629] omap_hsi omap_hsi.0: __hsi_write_cancel : -61
[ 7.276794] omap_hsi omap_hsi.0: __hsi_read_cancel : -61
[ 7.282470] [MODEM_IF] misc_open : umts_boot1
[ 7.287506] omap_hsi omap_hsi.0: Entering RX wakeup in 4 wires mode
[ 8.299774] misc dsscomp: [c7234000] ignoring set failure -22
[ 8.530609] s6e8aa: d/b 1, p 1, b-01390ffb
[ 8.530639] s6e8aa: c0, 1, b-001215fb, got v 3534794, factory wants 3529338
[ 8.530670] s6e8aa: c1, 1, b-00478927, got v 3764175, factory wants 3755229
[ 8.530700] s6e8aa: c2, 1, b-0012a421, got v 3486385, factory wants 3481495
[ 8.530731] s6e8aa: d/b 1, p 2, b-044d7cf9
[ 8.530761] s6e8aa: c0, 2, b-00bc6c9a, got v 3336878, factory wants 3330014
[ 8.530761] s6e8aa: c1, 2, b-01688d4e, got v 3556595, factory wants 3547367
[ 8.530792] s6e8aa: c2, 2, b-00a7db92, got v 3293516, factory wants 3285750
[ 8.530822] s6e8aa: d/b 1, p 3, b-0b323808
[ 8.530853] s6e8aa: c0, 3, b-026395cd, got v 3203365, factory wants 3194725
[ 8.530883] s6e8aa: c1, 3, b-0331a9fb, got v 3435905, factory wants 3424659
[ 8.530914] s6e8aa: c2, 3, b-021e3100, got v 3149091, factory wants 3139262
[ 8.530944] s6e8aa: d/b 1, p 4, b-186611f4
[ 8.530944] s6e8aa: c0, 4, b-062b8517, got v 3065435, factory wants 3053644
[ 8.531036] s6e8aa: c1, 4, b-0725b7f8, got v 3297279, factory wants 3284148
[ 8.531249] s6e8aa: c2, 4, b-053f8b4b, got v 3005194, factory wants 2992315
[ 8.531280] s6e8aa: d/b 1, p 5, b-6840e4ff
[ 8.531311] s6e8aa: c0, 5, b-221c3d41, got v 2688265, factory wants 2667329
[ 8.531341] s6e8aa: c1, 5, b-24fd4a51, got v 2906316, factory wants 2884895
[ 8.531372] s6e8aa: c2, 5, b-1d67176e, got v 2594260, factory wants 2571400
[ 8.531402] s6e8aa: d/b 1, p 6, b-ffffffff
[ 8.531433] s6e8aa: c0, 6, b-59b1b4d2, got v 2325286, factory wants 2292333
[ 8.531463] s6e8aa: c1, 6, b-60d28a3e, got v 2534439, factory wants 2499333
[ 8.531463] s6e8aa: c2, 6, b-4efd2a80, got v 2197307, factory wants 2162000
[ 11.727386] [MODEM_IF] misc_release : umts_boot1
[ 11.732147] omap_hsi omap_hsi.0: hsi_write_cancel ch 0
[ 11.756225] omap_hsi omap_hsi.0: __hsi_write_cancel : -61
[ 11.762268] omap_hsi omap_hsi.0: hsi_read_cancel ch 0
[ 11.767791] omap_hsi omap_hsi.0: __hsi_read_cancel : -125
[ 11.773620] omap_hsi omap_hsi.0: __hsi_write_cancel : -61
[ 11.779174] omap_hsi omap_hsi.0: __hsi_read_cancel : -61
[ 11.785552] [MODEM_IF] misc_open : umts_ipc0
[ 11.790954] omap_hsi omap_hsi.0: Entering RX wakeup in 4 wires mode
[ 11.798675] [MODEM_IF] misc_open : umts_rfs0
[ 11.829528] [MODEM_IF] PA EVENT : reset =1, pa=1
[ 11.834228] [MODEM_IF] umts_ipc0 state changed: ONLINE
[ 14.545074] drivers/misc/inv_mpu/mldl_cfg.c|inv_mpu_get_slave_config|1792 returning 4
[ 26.044372] request_suspend_state: wakeup (3->0) at 26030029299 (2012-05-13 00:25:34.359069826 UTC)
[ 26.622772] acc_open
[ 26.625122] acc_release
[ 26.670013]
[ 26.670043] Dongle Host Driver, version 5.90.125.94
[ 26.670043] Compiled in drivers/net/wireless/bcmdhd on Nov 21 2011 at 19:05:54
[ 26.684082] wl_android_wifi_on in
[ 26.687622] wifi_set_power = 1
[ 26.971282] =========== WLAN going back to live ========
[ 26.977600] sdio_reset_comm():
[ 27.066314] dhdsdio_write_vars: Download, Upload and compare of NVRAM succeeded.
[ 27.228179] wifi_get_mac_addr
[ 27.232513] Firmware up: op_mode=1, Broadcom Dongle Host Driver mac=a0:0b:ba:e6:73:ae
[ 27.344390] dhd_rx_frame: net device is NOT registered yet. drop packet
[ 27.351531] dhd_rx_frame: net device is NOT registered yet. drop packet
[ 27.360076] Firmware version = wl0: Oct 5 2011 14:41:12 version 5.90.125.94
[ 28.639709] wl_bss_connect_done succeeded status=(0x9)
[ 28.732391] wl_bss_connect_done succeeded status=(0x11)
[ 29.166564] nfc_power_apply ON
[ 29.201965] nfc_power_apply OFF
[ 29.272308] nfc_power_apply ON
[ 35.672241] rpmsg_omx rpmsg-omx1: local addr assigned: 0x401
[ 35.682067] omap-iommu omap-iommu.0: iommu_get: ducati qos_request
[ 35.703735] omap_hwmod: ipu: failed to hardreset
[ 35.713470] omap-iommu omap-iommu.0: ducati: version 2.1
[ 35.826934] rpmsg_omx rpmsg6: conn rsp: status 0 addr 101
[ 35.975158] rpmsg_omx rpmsg-omx1: Disconnecting from OMX service at 101
[ 39.279998] wlan0: no IPv6 routers present
[ 44.895355] init: untracked pid 1113 exited
[ 44.905731] init: untracked pid 1119 exited
[ 44.918914] init: untracked pid 1123 exited
[ 44.923248] init: untracked pid 1124 exited
[ 44.927612] init: untracked pid 1117 exited
[ 44.932067] init: untracked pid 1120 exited
[ 54.283905] max17040 4-0036: online = 1 vcell = 3788750 soc = 48 status = 3 health = 1 temp = 350 charger status = 0
[ 61.938812] request_suspend_state: sleep (0->3) at 61924468996 (2012-05-13 00:26:10.253540041 UTC)
[ 61.959869] dhd_set_suspend: force extra Suspend setting
[ 62.016418] dhd_get_dtim_skip bcn_li_dtim=3 DTIM=1 Listen=10
[ 62.038940] DSSCOMP: dsscomp_early_suspend
[ 62.054901] DSSCOMP: blanked screen
[ 62.143737] omap_hsi omap_hsi.0: Disabling clocks with HST FSM not IDLE !
[ 62.650421] PM: Syncing filesystems ... done.
[ 62.662689] PM: Preparing system for mem sleep
[ 62.667602] Freezing user space processes ... (elapsed 0.02 seconds) done.
[ 62.697692] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[ 62.729705] PM: Entering mem sleep
[ 62.746673] PVR: PVRSRVDriverSuspend(pDevice=c795ce00)
[ 62.753875] PVR: SysSystemPrePowerState: Entering state D3
[ 62.761535] PVR: Uninstalling device LISR on IRQ 53 with cookie c7aa2700
[ 62.770263] PVR: DisableSystemClocks: Disabling System Clocks
[ 62.786346] PM: suspend of devices complete after 49.102 msecs
[ 62.795654] PM: late suspend of devices complete after 1.434 msecs
[ 62.803955] Disabling non-boot CPUs ...
[ 62.845092] CPU1: shutdown
86.520507] Resume caused by IRQ 162, bcmsdh_sdmmc
[ 86.527343] Successfully put all powerdomains to target state
[ 86.535125] Suspended for 23.683 seconds
[ 86.541229] Enabling non-boot CPUs ...
[ 86.565612] CPU1: Booted secondary processor
[ 86.573120] Switched to NOHz mode on CPU #1
[ 86.580200] CPU1 is up
[ 86.586761] PM: early resume of devices complete after 2.227 msecs
[ 86.595001] wakeup wake lock: wlan_wake
[ 86.702270] PVR: PVRSRVDriverResume(pDevice=c795ce00)
[ 86.709381] PVR: SysSystemPostPowerState: Entering state D0
[ 86.717163] PVR: EnableSystemClocks: Enabling System Clocks
[ 86.724761] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie c7aa2700
[ 86.754638] PM: resume of devices complete after 159.881 msecs
[ 86.761535] PM: Finishing wakeup.
[ 86.765045] Restarting tasks ...
[ 86.768890] hub 1-0:1.0: activate --> -22
[ 86.782196] done.
[ 86.784973] suspend: exit suspend, ret = 0 (2012-05-13 00:26:35.099792469 UTC)
[ 88.201324] PM: Syncing filesystems ... done.
[ 88.213470] PM: Preparing system for mem sleep
[ 88.218505] Freezing user space processes ... (elapsed 0.02 seconds) done.
[ 88.248657] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[ 88.280487] PM: Entering mem sleep
[ 88.297576] PVR: PVRSRVDriverSuspend(pDevice=c795ce00)
[ 88.304901] PVR: SysSystemPrePowerState: Entering state D3
[ 88.312408] PVR: Uninstalling device LISR on IRQ 53 with cookie c7aa2700
[ 88.321289] PVR: DisableSystemClocks: Disabling System Clocks
[ 88.337280] PM: suspend of devices complete after 49.285 msecs
[ 88.346740] PM: late suspend of devices complete after 1.403 msecs
[ 88.354919] Disabling non-boot CPUs ...
[ 88.383422] CPU1: shutdown
[ 90.536529] Resume caused by IRQ 39, TWL6030-PIH
[ 90.543182] Successfully put all powerdomains to target state
[ 90.551116] Suspended for 2.162 seconds
[ 90.558746] Enabling non-boot CPUs ...
[ 90.582733] CPU1: Booted secondary processor
[ 90.591003] CPU1 is up
[ 90.594451] Switched to NOHz mode on CPU #1
[ 90.603668] PM: early resume of devices complete after 2.227 msecs
[ 90.720520] PVR: PVRSRVDriverResume(pDevice=c795ce00)
[ 90.727142] PVR: SysSystemPostPowerState: Entering state D0
[ 90.734405] PVR: EnableSystemClocks: Enabling System Clocks
[ 90.741577] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie c7aa2700
[ 90.750732] wakeup wake lock: musb_autosuspend_wake_lock
[ 90.777008] PM: resume of devices complete after 165.222 msecs
[ 90.783966] PM: Finishing wakeup.
[ 90.787475] Restarting tasks ...
[ 90.791320] hub 1-0:1.0: activate --> -22
[ 90.799774] done.
[ 90.802520] suspend: exit suspend, ret = 0 (2012-05-13 00:26:39.117340060 UTC)
[ 90.816131] PM: Syncing filesystems ... done.
[ 90.824768] PM: Preparing system for mem sleep
[ 90.829437] Freezing user space processes ...
[ 90.837615] active wake lock alarm_rtc, time left 124
[ 90.843048]
[ 90.844665] Freezing of user space aborted
[ 90.849395]
[ 90.850982] Restarting tasks ... done.
[ 90.859191] suspend: exit suspend, ret = -16 (2012-05-13 00:26:39.174041721 UTC)
[ 91.814605] PM: Syncing filesystems ... done.
[ 91.826843] PM: Preparing system for mem sleep
[ 91.831756] Freezing user space processes ... (elapsed 0.02 seconds) done.
[ 91.863708] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[ 91.895751] PM: Entering mem sleep
[ 91.908294] pm_op(): platform_pm_suspend+0x0/0x5c returns -16
[ 91.914337] PM: Device alarm failed to suspend: error -16
[ 91.920104] PM: Some devices failed to suspend
[ 91.925476] PM: resume of devices complete after 0.701 msecs
[ 91.932220] PM: Finishing wakeup.
[ 91.935729] Restarting tasks ... done.
[ 91.949096] suspend: exit suspend, ret = -16 (2012-05-13 00:26:40.263946506 UTC)
[ 92.208892] PM: Syncing filesystems ... done.
[ 92.221954] PM: Preparing system for mem sleep
[ 92.226898] Freezing user space processes ... (elapsed 0.02 seconds) done.
[ 92.262634] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[ 92.294006] PM: Entering mem sleep
[ 92.310577] PVR: PVRSRVDriverSuspend(pDevice=c795ce00)
[ 92.317871] PVR: SysSystemPrePowerState: Entering state D3
[ 92.325378] PVR: Uninstalling device LISR on IRQ 53 with cookie c7aa2700
[ 92.334259] PVR: DisableSystemClocks: Disabling System Clocks
[ 92.349121] PM: suspend of devices complete after 47.637 msecs
[ 92.357543] PM: late suspend of devices complete after 0.885 msecs
[ 92.365417] Disabling non-boot CPUs ...
[ 92.371520] CPU1: shutdown
[ 93.583618] Resume caused by IRQ 162, bcmsdh_sdmmc
[ 93.590118] Successfully put all powerdomains to target state
[ 93.597473] Suspended for 1.221 seconds
[ 93.602935] Enabling non-boot CPUs ...
[ 93.635894] gic_timer_retrigger: lost localtimer interrupt
[ 93.635894] CPU1: Booted secondary processor
[ 93.649993] CPU1 is up
[ 93.652343] Switched to NOHz mode on CPU #1
[ 93.660797] PM: early resume of devices complete after 1.037 msecs
[ 93.669067] wakeup wake lock: wlan_wake
[ 93.786315] PVR: PVRSRVDriverResume(pDevice=c795ce00)
[ 93.793426] PVR: SysSystemPostPowerState: Entering state D0
[ 93.801177] PVR: EnableSystemClocks: Enabling System Clocks
[ 93.808776] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie c7aa2700
[ 93.840850] PM: resume of devices complete after 171.936 msecs
[ 93.847869] PM: Finishing wakeup.
[ 93.851379] Restarting tasks ...
[ 93.855072] hub 1-0:1.0: activate --> -22
[ 93.866821] done.
[ 93.868988] suspend: exit suspend, ret = 0 (2012-05-13 00:26:42.183807332 UTC)
[ 93.876922] active wake lock wlan_rx_wake, time left 128
[ 95.176269] PM: Syncing filesystems ... done.
[ 95.188507] PM: Preparing system for mem sleep
[ 95.193542] Freezing user space processes ... (elapsed 0.02 seconds) done.
[ 95.225433] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[ 95.257324] PM: Entering mem sleep
[ 95.274169] PVR: PVRSRVDriverSuspend(pDevice=c795ce00)
[ 95.281494] PVR: SysSystemPrePowerState: Entering state D3
[ 95.289001] PVR: Uninstalling device LISR on IRQ 53 with cookie c7aa2700
[ 95.297882] PVR: DisableSystemClocks: Disabling System Clocks
[ 95.313903] PM: suspend of devices complete after 49.072 msecs
[ 95.323303] PM: late suspend of devices complete after 1.312 msecs
[ 95.331512] Disabling non-boot CPUs ...
[ 95.347778] CPU1: shutdown
[ 108.639556] Resume caused by IRQ 162, bcmsdh_sdmmc
[ 108.646392] Successfully put all powerdomains to target state
[ 108.654327] Suspended for 13.300 seconds
[ 108.660369] Enabling non-boot CPUs ...
[ 108.694885] CPU1: Booted secondary processor
[ 108.702423] Switched to NOHz mode on CPU #1
[ 108.709228] CPU1 is up
[ 108.715911] PM: early resume of devices complete after 2.227 msecs
[ 108.724151] wakeup wake lock: wlan_wake
[ 108.845031] PVR: PVRSRVDriverResume(pDevice=c795ce00)
[ 108.852142] PVR: SysSystemPostPowerState: Entering state D0
[ 108.859924] PVR: EnableSystemClocks: Enabling System Clocks
[ 108.867523] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie c7aa2700
[ 108.899505] PM: resume of devices complete after 175.537 msecs
[ 108.906402] PM: Finishing wakeup.
[ 108.910034] Restarting tasks ...
[ 108.913726] hub 1-0:1.0: activate --> -22
[ 108.925689] done.
[ 108.928070] suspend: exit suspend, ret = 0 (2012-05-13 00:26:57.242889345 UTC)
[ 108.935974] active wake lock max17040-battery
[ 108.940490] active wake lock wlan_rx_wake, time left 127
[ 108.980651] max17040 4-0036: online = 1 vcell = 3795000 soc = 48 status = 3 health = 1 temp = 330 charger status = 0
[ 110.227294] PM: Syncing filesystems ... done.
[ 110.239440] PM: Preparing system for mem sleep
[ 110.244506] Freezing user space processes ... (elapsed 0.02 seconds) done.
[ 110.276336] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[ 110.308258] PM: Entering mem sleep
[ 110.325103] PVR: PVRSRVDriverSuspend(pDevice=c795ce00)
[ 110.332427] PVR: SysSystemPrePowerState: Entering state D3
[ 110.339935] PVR: Uninstalling device LISR on IRQ 53 with cookie c7aa2700
[ 110.348815] PVR: DisableSystemClocks: Disabling System Clocks
[ 110.364807] PM: suspend of devices complete after 49.041 msecs
[ 110.374206] PM: late suspend of devices complete after 1.312 msecs
[ 110.382476] Disabling non-boot CPUs ...
[ 110.389648] CPU1: shutdown
[ 110.790832] Resume caused by IRQ 162, bcmsdh_sdmmc
[ 110.797637] Successfully put all powerdomains to target state
[ 110.805572] Suspended for 0.410 seconds
[ 110.811523] Enabling non-boot CPUs ...
[ 110.838012] CPU1: Booted secondary processor
[ 110.846282] CPU1 is up
[ 110.847106] Switched to NOHz mode on CPU #1
[ 110.858978] PM: early resume of devices complete after 2.227 msecs
[ 110.867248] wakeup wake lock: wlan_wake
[ 110.981903] PVR: PVRSRVDriverResume(pDevice=c795ce00)
[ 110.989013] PVR: SysSystemPostPowerState: Entering state D0
[ 110.996765] PVR: EnableSystemClocks: Enabling System Clocks
[ 111.004364] PVR: Installing device LISR SGX ISR on IRQ 53 with cookie c7aa2700
[ 111.037353] PM: resume of devices complete after 170.257 msecs
[ 111.044342] PM: Finishing wakeup.
[ 111.047851] Restarting tasks ...
[ 111.051544] hub 1-0:1.0: activate --> -22
[ 111.062164] done.
[ 111.064331] suspend: exit suspend, ret = 0 (2012-05-13 00:26:59.379150316 UTC)
[ 111.072174] active wake lock wlan_rx_wake, time left 128
[ 112.097290] PM: Syncing filesystems ... done.
[ 112.109497] PM: Preparing system for mem sleep
[ 112.114868] Freezing user space processes ... (elapsed 0.02 seconds) done.
[ 112.147583] Freezing remaining freezable tasks ... (elapsed 0.02 seconds) done.
[ 112.179473] PM: Entering mem sleep
[ 112.196014] PVR: PVRSRVDriverSuspend(pDevice=c795ce00)
[ 112.203338] PVR: SysSystemPrePowerState: Entering state D3
[ 112.210845] PVR: Uninstalling device LISR on IRQ 53 with cookie c7aa2700
[ 112.219726] PVR: DisableSystemClocks: Disabling System Clocks
[ 112.235717] PM: suspend of devices complete after 48.706 msecs
[ 112.245056] PM: late suspend of devices complete after 1.373 msecs
[ 112.253295] Disabling non-boot CPUs ...
[ 112.280487] CPU1: shutdown^^ This is great!
1) In your first "code" box in post #36, you got the output:
Which seem to imply you typed something to get the Kernel Dbg cmds??
2) What does it mean: "I was able to obtain that last one by typing in 'gedit' "?
a) Which "last one" and
b) where did you type this in?
3) Would the line (from what I suppose is from the iROM) that say: "Device type: HS, DEBUG OFF", imply that there is a way to turn Debug ON (for even more debug messages)?
1) In your first "code" box in post #36, you got the output:
Code:
debug> Kernel Debugger commands:2) What does it mean: "I was able to obtain that last one by typing in 'gedit' "?
a) Which "last one" and
b) where did you type this in?
3) Would the line (from what I suppose is from the iROM) that say: "Device type: HS, DEBUG OFF", imply that there is a way to turn Debug ON (for even more debug messages)?
I think thats the 'kernel' commands. It added the console prompt
For #2 i typed it in gedit and copied it, then pasted repeatedly to the terminal that way i was sending enter enter console.
Have you actually managed to figure out on what (serial?) device ( /dev/xxxx ) all this output is coming from?
I.e. Given that the Kernel is loading in the background, while you're in the FIQ debugger, you should be able to get a shell at the same time (by connecting through BT/WiFi or by local shell on telephone). Now assuming you have this, what device is your serial FIQ debugger located on? (You should then be able to intercept and/or inject [echo] FIQ commands on that device.)
I.e. Given that the Kernel is loading in the background, while you're in the FIQ debugger, you should be able to get a shell at the same time (by connecting through BT/WiFi or by local shell on telephone). Now assuming you have this, what device is your serial FIQ debugger located on? (You should then be able to intercept and/or inject [echo] FIQ commands on that device.)
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
5fiq debugger
First and foremost, many thanks to the participants of this thread. I'm doing kernel hacking on GNex and got valuable information here on retrieving UART output.
I did the trick of soldering a 619komh resistor in a micro usb cable + a uart-usb converter, and successfully got 'some' output :
- by default, I get the debug prompt (fiq debugger) for three seconds only
- by enabling in the kernel options : "Put the FIQ debugger into console mode by default", and I get the kernel logs until this message only
Anything after is not retrievable.Code:fsa9480 4-0025: cable detect change, from 'unknown/none' to 'jig'
This is as far as I could go with the info provided by the thread.
Below, I want to share things I came to understand but did not find any clues in this thread, and hopes it may help future developers that were puzzled by the same problems I encountered.
FIQ debugger:
The FIQ debugger is a valuable tool as it gives access to cpu registers and many commands to give to the OS. It takes the form of a kernel module. It has two modes, the "debug mode" which is a independant prompt with its own commands, and the "console mode" which is the regular shell on the device. The problem is we get access to this debugger for like 3 seconds only, making it indeed useless.
Some background first:
- by default, user interaction with the fiq debugger goes through the UART and the associated IRQ (and not the FIQ as its name should imply, although it is capable of using FIQ on other devices I think).
- At kernel boot, the fiq debugger requests the usage of UART2 and successfully register itself to the kernel, which will assign a irq number to the debugger (n'106). This means everything going through the UART2 port (micro sub -> fsa chip -> uart2) will trigger a irq106, and communicate with the debugger kernel module.
- 'Contact' is lost after 3 seconds (ie impossible to get logs or communicate with the debugger), as any requests from outside are not processed by the kernel. No processing, no control.
What is happenning? The event which breaks the uart link is the detection of a "jig" cable by the fsa driver. Detecting a jig will causes the kernel to change the functionality of the associated uart port from "simple uart input/output with the micro usb" to "uart redirected to another component" (according to kernel source, it is LTE, MODEM or AP, I have no idea what are those devices). Therefore, the detection of the jig cable breaks the uart link to the host.
If the fsa detects a 'uart' cable, though, the kernel will take no action: the default state of the uart port and the mux in between is a regular input/output.
The "trick" to keep the fiq debugger usable at all times would be to use a proper UART cable, or a cable detected as a 'uart' one (this would require to solder the correct resistor value). I have no idea if using a proper 'uart' cable (and not a 'jig' 619k-resistor cable) will result in no messages before the kernel boot. I also believe using a proper 'uart' cable should enable the use of fiq debugger even on a stock kernel.
Those who already have this 619k cable and don't want to meddle with it, can trick the kernel into thinking the 'jig' cable is a 'uart' cable. A simple edit will do.
In /drivers/misc/fsa9480.c, look for
and change it toCode:_detected(usbsw, FSA9480_DETECT_JIG);
This way, the fiq debugger keeps receiving requests coming from the micro usb and your host computer, as the kernel will not redirect the uart to other components.Code:_detected(usbsw, FSA9480_DETECT_UART);
Miscellaneous remarks:
- to enable the FIQ debugger, you are not required to tap enter twice at the very beginning. Just plugging the cable and pressing enter twice at any times will do. This makes things easier to debug.
- The /dev/ttyFIQ0 is a console registered by the FIQ debugger. Adding the kernel boot parameter "console=ttyFIQ0" will make you enable to use a full shell on the device, either if you enabled the "console mode" by default or if you typed "console" in the fiq debugger prompt. Not adding it will not prevent you from using the debug mode, but in console mode you will only get the console output.
- In debug mode, you will notice the debugger will sleep if not used ("suspending FIQ debugger"). To wake up, you should press twice <ENTER>. You can also prevent it to sleep by entering in debug mode 'nosleep'.3This device should have external UART.
Have you tried 619Kohms on the USB port yet? Most samsung device, including this one, have a FSA chip. This is the first way to tell if UART is properly connected.
If it is, than you can probe deeper to find the internal UART which will show more. The Internal UART connection will show UART before the FSA chip is initialized giving you even more to work with.
It's likely that because this is an OMAP chip, it should have the following characteristics:
192600 or 115200 bps
8 bits per word
1 stop bit
No parity
No flow control
1.8V high, Open drain
I'm not sure if the FSA chip will increase that level to 3V or not.3
Yep. I did read extensively the resources you have posted before, but could not resolve myself to try the 150k resistor. I went for the 619k resistor which had been confirmed to work. Now I am, however, pretty convinced that the 150k will work (although I won't do it, as I had quite some trouble setting up the cable already).
About early prints via USB, I am buying Rebellos explanation. Printing outputs to USB from the bootloader does not make much sense to me, as USB is so much more convoluted that the standard UART. I doubt bootloader developpers added such a functionality (print to USB) when they surely have the hardware to do with UART.
Of course, data transfer is another thing, and USB link is de facto necessary...
From what I have collected (OMAP TRM and www-riveywood-com/fiqvsirq.html):Rebellos said:
Each ARM core has one FIQ input pin (nFIQ), and one IRQ input pin (nIRQ). Only two pins. Interrupts can come from many sources, so having two input lines is obviously not enough. So interrupts are centralized by an interrupt controller, which exposes many interrupts lines to the multiples components of the device. The interrupt controller will manage incoming IRQs, check their priority, and dispatch them to the ARM core(s). Fact is this interrupt controller (at least in OMAP4460, the GNex chip) exposes only one FIQ line which bypass all the interrupt arbitration logic, and is directly linked to nFIQ. This line can also be used as a classic IRQ line.
The FIQ mode is rarely used though. Using it would mean that we have only one very high priority source linked directly to nFIQ, which has priority over every other IRQs (that would include radio, touch screen, button, etc...).
Is making the FIQ debugger "the single very high priority interrupt source" reliable/correct/reasonable ? FIQ debugger has been designed as such, but Google/Samsung may have not intended to use it with FIQ. After all, from their point of view, FIQ debugger could have been only a quick and dirty way to get some register info or a uart console, but it is very lacking in debugging power. If there was a case where a IRQ got stuck somewhere, they have means to use JTAG.
Also, and I have not put much though in it to confirm, is such a complex piece of code like a debugger compatible with the FIQ philosophy of "make it quick and get out" ?
Another explanation is that something else may be using the FIQ line already.3I've attached a circuit diagram. You will need to modify your cable. You will need a UART device like the FTDIFriend or Bus Pirate. I specified the communications settings above.
Here is the cable modifications and where to hook up on the MicroUSB port.
Power is disconnected
Data- and Data+ are your signal lines.
Pin X (aka Pin4) is connected to ground via 619Kohm resistor
Ground is used as a reference.
Just tear up a MicroUSB cable and modify it as above.2Hi,
I tried both values (619 KOhms and 150 Kohms). Contrary to Adam, there was no difference in the bootloaders's output. The only difference was that the kernel did not recognize the 619 Kohms value for the FIQ and stopped outputting anything - whereas with the 150 Kohms it worked fine (see pid below).
I used the following parts:
http://www.sparkfun.com/products/10031 USB MicroB Plug Breakout Board
http://www.dealextreme.com/p/usb-to-uart-5-pin-cp2102-module-serial-converter-81872?item=18 USB to UART 5-Pin CP2102 Module Serial Converter
You will also need a 150 Kohms resistor and a 5 pin row header which is easy to find. Note: VCC is not connected, which is normal.
