Android Eclair on OMAP3530

httpv://www.youtube.com/watch?v=blD-KYTESJ4

一個人開板子的心酸與寂寞, 有誰懂呢?
一個人開板子, 什麼奇怪的問題都會遇到, 每次都好刺激.

原本用usb轉rs232看console訊息, 後來插usb轉sd卡, 再插回usb轉rs232, 這樣sd卡中的image會有問題, 連我自己都不相信, 出現下列訊息:

[root@Android /]#find / -name "copy"
UBIFS error (pid 487): ubifs_read_node: bad node type (27 but expected 9)
UBIFS error (pid 487): ubifs_read_node: bad node at LEB 288:112968
UBIFS error (pid 487): ubifs_iget: failed to read inode 608, error -22
UBIFS error (pid 487): ubifs_lookup: dead directory entry 'usr', error -22
UBIFS warning (pid 487): ubifs_ro_mode: switched to read-only mode, error -22
find: /system/usr: Invalid argumUBIFS error (pid 487): ubifs_read_node: bad node type (226 but expected 9)
ent
UBIFS error (pid 487): ubifs_read_node: bad node at LEB 288:112008
UBIFS error (pid 487): ubifs_iget: failed to read inode 580, error -22
UBIFS error (pid 487): ubifs_lookup: dead directory entry 'xbin', error -22
find: /system/xbin: Invalid argument
UBIFS error (pid 487): ubifs_read_node: bad node type (254 but expected 9)
UBIFS error (pid 487): ubifs_read_node: bad node at LEB 288:110088
UBIFS error (pid 487): ubifs_iget: failed to read inode 577, error -22
UBIFS error (pid 487): ubifs_lookup: dead directory entry 'android.awt.jar', error -22
find: /system/framework/android.UBIFS error (pid 487): ubifs_read_node: bad node type (136 but expected 9)
awt.jar: Invalid argument
UBIFS error (pid 487): ubifs_read_node: bad node at LEB 288:109896
UBIFS error (pid 487): ubifs_iget: failed to read inode 573, error -22
UBIFS error (pid 487): ubifs_lookup: dead directory entry 'monkey.jar', error -22
find: /system/framework/monkey.jUBIFS error (pid 487): ubifs_read_node: bad node type (136 but expected 9)
ar: Invalid argument
UBIFS error (pid 487): ubifs_read_node: bad node at LEB 288:109896
UBIFS error (pid 487): ubifs_iget: failed to read inode 574, error -22
UBIFS error (pid 487): ubifs_lookup: dead directory entry 'ime.jar', error -22
find: /system/framework/ime.jar:UBIFS error (pid 487): ubifs_read_node: bad node type (226 but expected 9)
 Invalid argument
UBIFS error (pid 487): ubifs_read_node: bad node at LEB 288:112008
UBIFS error (pid 487): ubifs_iget: failed to read inode 579, error -22
UBIFS error (pid 487): ubifs_lookup: dead directory entry 'pm.jar', error -22
find: /system/framework/pm.jar: UBIFS error (pid 487): ubifs_read_node: bad node type (85 but expected 9)
Invalid argument
UBIFS error (pid 487): ubifs_read_node: bad node at LEB 288:110472
UBIFS error (pid 487): ubifs_iget: failed to read inode 578, error -22
UBIFS error (pid 487): ubifs_lookup: dead directory entry 'framework.jar', error -22
find: /system/framework/frameworUBIFS error (pid 487): ubifs_read_node: bad node type (136 but expected 9)
k.jar: Invalid argument
UBIFS error (pid 487): ubifs_read_node: bad node at LEB 288:109896
UBIFS error (pid 487): ubifs_iget: failed to read inode 576, error -22
UBIFS error (pid 487): ubifs_lookup: dead directory entry 'services.jar', error -22
find: /system/framework/servicesUBIFS error (pid 487): ubifs_read_node: bad node type (136 but expected 9)
.jar: Invalid argument
UBIFS error (pid 487): ubifs_read_node: bad node at LEB 288:109896
UBIFS error (pid 487): ubifs_iget: failed to read inode 572, error -22
UBIFS error (pid 487): ubifs_lookup: dead directory entry 'am.jar', error -22
find: /system/framework/am.jar: UBIFS error (pid 487): ubifs_read_node: bad node type (136 but expected 9)
Invalid argument
UBIFS error (pid 487): ubifs_read_node: bad node at LEB 288:109896
UBIFS error (pid 487): ubifs_iget: failed to read inode 575, error -22
UBIFS error (pid 487): ubifs_lookup: dead directory entry 'svc.jar', error -22
find: /system/framework/svc.jar: Invalid argument
[root@Android /]#UBIFS error (pid 214): make_reservation: cannot reserve 160 bytes in jhead 1, error -30
UBIFS error (pid 214): ubifs_write_inode: can't write inode 715, error -30
UBIFS error (pid 214): make_reservation: cannot reserve 160 bytes in jhead 1, error -30
UBIFS error (pid 214): ubifs_write_inode: can't write inode 718, error -30

一個人開板子, 常常要獨立思考問題發生的原因.

正常開機後, 出現下列訊息:

binder: release proc 792, transaction 510, not freed
binder: release proc 1106, transaction 2326, not freed
...
init: untracked pid 742 exited
init: untracked pid 785 exited
init: untracked pid 823 exited
init: untracked pid 862 exited
init: untracked pid 900 exited
init: untracked pid 940 exited
init: untracked pid 979 exited
init: untracked pid 1020 exited
init: untracked pid 1058 exited
init: untracked pid 1097 exited
init: untracked pid 1137 exited
init: untracked pid 1176 exited
init: untracked pid 1214 exited

debug的方法比照上課講的, 原因是電池的問題, 修正方式比照上課講的.

仿照emulator修改init.rc, 無效:

# fake some battery state
setprop status.battery.state Slow
setprop status.battery.level 5
setprop status.battery.level_raw  50
setprop status.battery.level_scale 9

有些問題以前都遇過, 但是現在年紀大了, 記憶力不好, 常常都忘記怎麼解決.

現階段在kernel的部分, 我還不打算做back port的動作.